)]}'
{
  "commit": "e4a3f541f0b67fdad98b326c851dfe7f4b6b6dad",
  "tree": "e93b858ab3313374d23c4ebadc5077816f1894f2",
  "parents": [
    "e08fbb78f03fe2c4f88824faf6f51ce6af185e11"
  ],
  "author": {
    "name": "Steven Rostedt",
    "email": "srostedt@redhat.com",
    "time": "Tue Jun 14 19:02:29 2011 -0400"
  },
  "committer": {
    "name": "Steven Rostedt",
    "email": "rostedt@goodmis.org",
    "time": "Thu Jul 07 22:26:27 2011 -0400"
  },
  "message": "tracing: Still trace filtered irq functions when irq trace is disabled\n\nIf a function is set to be traced by the set_graph_function, but the\noption funcgraph-irqs is zero, and the traced function happens to be\ncalled from a interrupt, it will not be traced.\n\nThe point of funcgraph-irqs is to not trace interrupts when we are\npreempted by an irq, not to not trace functions we want to trace that\nhappen to be *in* a irq.\n\nLuckily the current-\u003etrace_recursion element is perfect to add a flag\nto help us be able to trace functions within an interrupt even when\nwe are not tracing interrupts that preempt the trace.\n\nReported-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nTested-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a3e2db708072f23b062a86f4b7a85cffaa763bba",
      "old_mode": 33188,
      "old_path": "kernel/trace/trace.h",
      "new_id": "651f35be372a40efd6ec4f63872b85ba35ee1570",
      "new_mode": 33188,
      "new_path": "kernel/trace/trace.h"
    },
    {
      "type": "modify",
      "old_id": "e8d6bb55d719f75ea829f613d91191b82f70807f",
      "old_mode": 33188,
      "old_path": "kernel/trace/trace_functions_graph.c",
      "new_id": "a7d2a4c653d8d893f51652c8cd599bf780359f45",
      "new_mode": 33188,
      "new_path": "kernel/trace/trace_functions_graph.c"
    }
  ]
}