summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorNicolas Pitre <nicolas.pitre@linaro.org>2014-07-25 16:05:30 -0400
committerSteven Rostedt <rostedt@goodmis.org>2014-08-07 20:40:40 -0400
commitf6d9804d145b9c42dbbabefdda208a6a492b2236 (patch)
tree6a03d7b66cdbc5d9227a3e2c9d831b3ba99896d7 /virt/kvm
parent3c49b52b155d0f723792377e1a4480a0e7ca0ba2 (diff)
downloadlinux-f6d9804d145b9c42dbbabefdda208a6a492b2236.tar.gz
linux-f6d9804d145b9c42dbbabefdda208a6a492b2236.tar.bz2
linux-f6d9804d145b9c42dbbabefdda208a6a492b2236.zip
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/1406318733-26754-3-git-send-email-nicolas.pitre@linaro.org Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org> Signed-off-by: Nicolas Pitre <nico@linaro.org> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions