)]}'
{
  "commit": "df8290bf7ea6b3051e2f315579a6e829309ec1ed",
  "tree": "e142ed95335a9e1790deabc11448ee6e215bb855",
  "parents": [
    "76e1d9047e4edefb8ada20aa90d5762306082bd6"
  ],
  "author": {
    "name": "Frederic Weisbecker",
    "email": "fweisbec@gmail.com",
    "time": "Fri Apr 09 00:28:14 2010 +0200"
  },
  "committer": {
    "name": "Frederic Weisbecker",
    "email": "fweisbec@gmail.com",
    "time": "Wed Apr 14 18:20:33 2010 +0200"
  },
  "message": "perf: Make clock software events consistent with general exclusion rules\n\nThe cpu/task clock events implement their own version of exclusion\non top of exclude_user and exclude_kernel.\n\nThe result is that when the event triggered in the kernel but we\nhave exclude_kernel set, we try to rewind using task_pt_regs.\nThere are two side effects of this:\n\n- we call task_pt_regs even on kernel threads, which doesn\u0027t give\n  us the desired result.\n- if the event occured in the kernel, we shouldn\u0027t rewind to the\n  user context. We want to actually ignore the event.\n\nget_irq_regs() will always give us the right interrupted context, so\nuse its result and submit it to perf_exclude_context() that knows\nwhen an event must be ignored.\n\nSigned-off-by: Frederic Weisbecker \u003cfweisbec@gmail.com\u003e\nCc: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nCc: Arnaldo Carvalho de Melo \u003cacme@redhat.com\u003e\nCc: Paul Mackerras \u003cpaulus@samba.org\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9efdfe5b8d3b8b70d57e67d5104c07b1a62d5a29",
      "old_mode": 33188,
      "old_path": "kernel/perf_event.c",
      "new_id": "095101d685bc446b1382ec54753e520cf3cc1803",
      "new_mode": 33188,
      "new_path": "kernel/perf_event.c"
    }
  ]
}