summaryrefslogtreecommitdiff
path: root/drivers/firmware
diff options
context:
space:
mode:
authorMasami Hiramatsu <mhiramat@kernel.org>2016-09-08 19:05:45 +0300
committerSteven Rostedt <rostedt@goodmis.org>2016-09-23 16:47:59 +0300
commita0d0c6216afad4b2b1704a72bd76bea259e07655 (patch)
tree434154729ad4dd19f38e58ae71afc968be6ecde7 /drivers/firmware
parent951dbf500aa7df051d7cde15b9ac05608c0bb16f (diff)
downloadlinux-a0d0c6216afad4b2b1704a72bd76bea259e07655.tar.xz
tracing: Call traceoff trigger after event is recorded
Call traceoff trigger after the event is recorded. Since current traceoff trigger is called before recording the event, we can not know what event stopped tracing. Typical usecase of traceoff/traceon trigger is tracing function calls and trace events between a pair of events. For example, trace function calls between syscall entry/exit. In that case, it is useful if we can see the return code of the target syscall. Link: http://lkml.kernel.org/r/147335074530.12462.4526186083406015005.stgit@devbox Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'drivers/firmware')
0 files changed, 0 insertions, 0 deletions