diff options
author | Nicolas Pitre <[email protected]> | 2014-07-25 16:05:30 -0400 |
---|---|---|
committer | Steven Rostedt <[email protected]> | 2014-08-07 20:40:40 -0400 |
commit | f6d9804d145b9c42dbbabefdda208a6a492b2236 (patch) | |
tree | 6a03d7b66cdbc5d9227a3e2c9d831b3ba99896d7 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 3c49b52b155d0f723792377e1a4480a0e7ca0ba2 (diff) |
tracepoint: add generic tracepoint definitions for IPI tracing
The Inter Processor Interrupt is used to make another processor do a
specific action such as rescheduling tasks, signal a timer event or
execute something in another CPU's context. IRQs are already traceable
but IPIs were not. Tracing them is useful for monitoring IPI latency,
or to verify when they are the source of CPU wake-ups with power
management implications.
Three trace hooks are defined: ipi_raise, ipi_entry and ipi_exit. To make
them portable, a string is used to identify them and correlate related
events. Additionally, ipi_raise records a bitmask representing targeted
CPUs.
Link: http://lkml.kernel.org/p/[email protected]
Acked-by: Daniel Lezcano <[email protected]>
Signed-off-by: Nicolas Pitre <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions