)]}'
{
  "commit": "736ec1677f1ae7e64f2f3436ca3775c48f79678c",
  "tree": "48db2dfcfc0a028a2a427b5b9c537c4a389aa705",
  "parents": [
    "05735a2a9cf37f5dc11ece998906431dda707258"
  ],
  "author": {
    "name": "Stefan Hajnoczi",
    "email": "stefanha@redhat.com",
    "time": "Wed Jan 15 11:10:30 2014 +0800"
  },
  "committer": {
    "name": "Stefan Hajnoczi",
    "email": "stefanha@redhat.com",
    "time": "Mon Jan 27 15:49:39 2014 +0100"
  },
  "message": "trace: fix simple trace \"disable\" keyword\n\nThe trace-events \"disable\" keyword turns an event into a nop at\ncompile-time.  This is important for high-frequency events that can\nimpact performance.\n\nThe \"disable\" keyword is currently broken in the simple trace backend.\nThis patch fixes the problem as follows:\n\nTrace events are identified by their TraceEventID number.  When events\nare disabled there are two options for assigning TraceEventID numbers:\n1. Skip disabled events and don\u0027t assign them a number.\n2. Assign numbers for all events regardless of the disabled keyword.\n\nThe simple trace backend and its binary file format uses approach #1.\n\nThe tracetool infrastructure has been using approach #2 for a while.\n\nThe result is that the numbers used in simple trace files do not\ncorrespond with TraceEventIDs.  In trace/simple.c we assumed that they\nare identical and therefore emitted bogus numbers.\n\nThis patch fixes the bug by using TraceEventID for trace_event_id()\nwhile sticking to approach #1 for simple trace file numbers.  This\npreserves simple trace file format compatibility.\n\nSigned-off-by: Stefan Hajnoczi \u003cstefanha@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "30faac93c8ff12b14b25bb0bed1c01c2e8ddeda0",
      "old_mode": 33188,
      "old_path": "scripts/tracetool/backend/simple.py",
      "new_id": "3dde372e466a1a14305b07ab5485be667f3ab668",
      "new_mode": 33188,
      "new_path": "scripts/tracetool/backend/simple.py"
    }
  ]
}