)]}'
{
  "log": [
    {
      "commit": "ada64e4c98eb5f04a9ca223c5ff9e7ac22ce6404",
      "tree": "48e284cf69157cf54302dcceb01ad7a07b889206",
      "parents": [
        "a0de055cf61338549b13079a5677ef2e1b6472ef"
      ],
      "author": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:24 2010 -0500"
      },
      "committer": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:24 2010 -0500"
      },
      "message": "kgdboc,keyboard: Keyboard driver for kdb with kgdb\n\nThis patch adds in the kdb PS/2 keyboard driver.  This was mostly a\ndirect port from the original kdb where I cleaned up the code against\ncheckpatch.pl and added the glue to stitch it into kgdb.\n\nThis patch also enables early kdb debug via kgdbwait and the keyboard.\n\nAll the access to configure kdb using either a serial console or the\nkeyboard is done via kgdboc.\n\nIf you want to use only the keyboard and want to break in early you\nwould add to your kernel command arguments:\n\n    kgdboc\u003dkbd kgdbwait\n\nIf you wanted serial and or the keyboard access you could use:\n\n    kgdboc\u003dkbd,ttyS0\n\nYou can also configure kgdboc as a kernel module or at run time with\nthe sysfs where you can activate and deactivate kgdb.\n\nTurn it on:\n    echo kbd,ttyS0 \u003e /sys/module/kgdboc/parameters/kgdboc\n\nTurn it off:\n    echo \"\" \u003e /sys/module/kgdboc/parameters/kgdboc\n\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\nReviewed-by: Dmitry Torokhov \u003cdmitry.torokhov@gmail.com\u003e\n"
    },
    {
      "commit": "a0de055cf61338549b13079a5677ef2e1b6472ef",
      "tree": "6191bbd6b3d567350b12ad973356995dbeffeeb3",
      "parents": [
        "6d45a1aed34b0cd7b298967eb9cb72b77afcb33b"
      ],
      "author": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:24 2010 -0500"
      },
      "committer": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:24 2010 -0500"
      },
      "message": "kgdb: gdb \"monitor\" -\u003e kdb passthrough\n\nOne of the driving forces behind integrating another front end (kdb)\nto the debug core is to allow front end commands to be accessible via\ngdb\u0027s monitor command.  It is true that you could write gdb macros to\nget certain data, but you may want to just use gdb to access the\ncommands that are available in the kdb front end.\n\nThis patch implements the Rcmd gdb stub packet.  In gdb you access\nthis with the \"monitor\" command.  For instance you could type \"monitor\nhelp\", \"monitor lsmod\" or \"monitor ps A\" etc...\n\nThere is no error checking or command restrictions on what you can and\ncannot access at this point.  Doing something like trying to set\nbreakpoints with the monitor command is going to cause nothing but\nproblems.  Perhaps in the future only the commands that are actually\nknown to work with the gdb monitor command will be available.\n\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\n"
    },
    {
      "commit": "f5316b4aea024da9266d740322a5481657f6ce59",
      "tree": "5888fd0afa54fc3bab2711e583147c4b563836bc",
      "parents": [
        "dcc7871128e99458ca86186b7bc8bf27ff0c47b5"
      ],
      "author": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:22 2010 -0500"
      },
      "committer": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:22 2010 -0500"
      },
      "message": "kgdb,8250,pl011: Return immediately from console poll\n\nThe design of the kdb shell requires that every device that can\nprovide input to kdb have a polling routine that exits immediately if\nthere is no character available.  This is required in order to get the\npage scrolling mechanism working.\n\nChanging the kernel debugger I/O API to require all polling character\nroutines to exit immediately if there is no data allows the kernel\ndebugger to process multiple input channels.\n\nNO_POLL_CHAR will be the return code to the polling routine when ever\nthere is no character available.\n\nCC: linux-serial@vger.kernel.org\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\n"
    },
    {
      "commit": "dcc7871128e99458ca86186b7bc8bf27ff0c47b5",
      "tree": "e10d252ccc4e990aac7dd09f44b94cfe045adc6b",
      "parents": [
        "67fc4e0cb931d6b4ccf21248e4199b154478ecea"
      ],
      "author": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:21 2010 -0500"
      },
      "committer": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:21 2010 -0500"
      },
      "message": "kgdb: core changes to support kdb\n\nThese are the minimum changes to the kgdb core in order to enable an\nAPI to connect a new front end (kdb) to the debug core.\n\nThis patch introduces the dbg_kdb_mode variable controls where the\nuser level I/O is routed.  It will be routed to the gdbstub (kgdb) or\nto the kdb front end which is a simple shell available over the kgdboc\nconnection.\n\nYou can switch back and forth between kdb or the gdb stub mode of\noperation dynamically.  From gdb stub mode you can blindly type\n\"$3#33\", or from the kdb mode you can enter \"kgdb\" to switch to the\ngdb stub.\n\nThe logic in the debug core depends on kdb to look for the typical gdb\nconnection sequences and return immediately with KGDB_PASS_EVENT if a\ngdb serial command sequence is detected.  That should allow a\nreasonably seamless transition between kdb -\u003e gdb without leaving the\nkernel exception state.  The two gdb serial queries that kdb is\nresponsible for detecting are the \"?\" and \"qSupported\" packets.\n\nCC: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\nAcked-by: Martin Hicks \u003cmort@sgi.com\u003e\n"
    },
    {
      "commit": "5d5314d6795f3c1c0f415348ff8c51f7de042b77",
      "tree": "2f433649d29be98ebc975f352b7d7046a2a2beec",
      "parents": [
        "e8861129d3c1a64e3c62f459aeb1cd54a55ab045"
      ],
      "author": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:20 2010 -0500"
      },
      "committer": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:20 2010 -0500"
      },
      "message": "kdb: core for kgdb back end (1 of 2)\n\nThis patch contains only the kdb core.  Because the change set was\nlarge, it was split.  The next patch in the series includes the\ninstrumentation into the core kernel which are mainly helper functions\nfor kdb.\n\nThis work is directly derived from kdb v4.4 found at:\n\nftp://oss.sgi.com/projects/kdb/download/v4.4/\n\nThe kdb internals have been re-organized to make them mostly platform\nindependent and to connect everything to the debug core which is used by\ngdbstub (which has long been known as kgdb).\n\nThe original version of kdb was 58,000 lines worth of changes to\nsupport x86.  From that implementation only the kdb shell, and basic\ncommands for memory access, runcontrol, lsmod, and dmesg where carried\nforward.\n\nThis is a generic implementation which aims to cover all the current\narchitectures using the kgdb core: ppc, arm, x86, mips, sparc, sh and\nblackfin.  More archictectures can be added by implementing the\narchitecture specific kgdb functions.\n\n[mort@sgi.com: Compile fix with hugepages enabled]\n[mort@sgi.com: Clean breakpoint code renaming kdba_ -\u003e kdb_]\n[mort@sgi.com: fix new line after printing registers]\n[mort@sgi.com: Remove the concept of global vs. local breakpoints]\n[mort@sgi.com: Rework kdb_si_swapinfo to use more generic name]\n[mort@sgi.com: fix the information dump macros, remove \u0027arch\u0027 from the names]\n[sfr@canb.auug.org.au: include fixup to include linux/slab.h]\n\nCC: linux-arch@vger.kernel.org\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\nSigned-off-by: Martin Hicks \u003cmort@sgi.com\u003e\n"
    },
    {
      "commit": "53197fc49549240f6c6a963b2713a4cd9517964b",
      "tree": "5a89c338ef8acd188e4aa1503370a4e928c33edd",
      "parents": [
        "c433820971ffa854feda6adc17f5f24201354f11"
      ],
      "author": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Fri Apr 02 11:48:03 2010 -0500"
      },
      "committer": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:19 2010 -0500"
      },
      "message": "Separate the gdbstub from the debug core\n\nSplit the former kernel/kgdb.c into debug_core.c which contains the\nkernel debugger exception logic and to the gdbstub.c which contains\nthe logic for allowing gdb to talk to the debug core.\n\nThis also created a private include file called debug_core.h which\ncontains all the definitions to glue the debug_core to any other\ndebugger connections.\n\nCC: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\n"
    },
    {
      "commit": "c433820971ffa854feda6adc17f5f24201354f11",
      "tree": "efb8028cc56e36eeade40d3a96bb461a242bab51",
      "parents": [
        "a0fe3cc5d36a5f5b4f60abfe1a4b1caf4a5cce5a"
      ],
      "author": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Tue May 19 07:49:32 2009 -0500"
      },
      "committer": {
        "name": "Jason Wessel",
        "email": "jason.wessel@windriver.com",
        "time": "Thu May 20 21:04:18 2010 -0500"
      },
      "message": "Move kernel/kgdb.c to kernel/debug/debug_core.c\n\nMove kgdb.c in preparation to separate the gdbstub from the debug\ncore and exception handling.\n\nCC: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Jason Wessel \u003cjason.wessel@windriver.com\u003e\n"
    }
  ]
}