aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/input/misc/dm355evm_keys.c
diff options
context:
space:
mode:
authorAndrea Bastoni <bastoni@sprg.uniroma2.it>2012-02-11 15:41:19 -0500
committerAndrea Bastoni <bastoni@sprg.uniroma2.it>2012-02-11 15:41:19 -0500
commitbcbc4c0486323cdc6d377253b4fc70ab9d030540 (patch)
tree0e3da47cd2dc8a83803cea836d46864e34fdcbfa /drivers/input/misc/dm355evm_keys.c
parent83b11ea1c6ad113519c488853cf06e626c95a64d (diff)
Add kernel-style events for sched_trace_XXX() functionswip-tracepoints
Enable kernel-style events (tracepoint) for Litmus. Litmus events trace the same functions as the sched_trace_XXX(), but can be enabled independently. So, why another tracing infrastructure then: - Litmus tracepoints can be recorded and analyzed together (single time reference) with all other kernel tracing events (e.g., sched:sched_switch, etc.). It's easier to correlate the effects of kernel events on litmus tasks. - It enables a quick way to visualize and process schedule traces using trace-cmd utility and kernelshark visualizer. Kernelshark lacks unit-trace's schedule-correctness checks, but it enables a fast view of schedule traces and it has several filtering options (for all kernel events, not only Litmus').
Diffstat (limited to 'drivers/input/misc/dm355evm_keys.c')
0 files changed, 0 insertions, 0 deletions