aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorBen Gardiner <[email protected]>2011-05-18 10:03:34 -0400
committerTakashi Iwai <[email protected]>2011-05-18 17:12:39 +0200
commitec08b14483de0702ca43e3a8506e149486975f9b (patch)
tree8519bc5afc22b259886aa775bef402dd51378601 /tools/perf/util/scripting-engines/trace-event-python.c
parent7cdd8d73139ec935a8e91806131a5b91e26c653e (diff)
ALSA: sound, core, pcm_lib: xrun_log: log also in_interrupt
When debugging pcm drivers I found the "period" or "hw" prefix printed by either XRUN_DEBUG_PERIODUPDATE or XRUN_DEBUG_PERIODUPDATE events, respectively to be very useful is observing the interplay between interrupt-context updates and syscall-context updates. Similarly, when debugging overruns with XRUN_DEBUG_LOG it is useful to see the context of the last 10 positions. Add an in_interrupt member to hwptr_log_entry which stores the value of the in_interrupt parameter of snd_pcm_update_hw_ptr0 when the log entry is created. Print a "[Q]" prefix when dumping the log entries if in_interrupt was true. Signed-off-by: Ben Gardiner <[email protected]> Signed-off-by: Takashi Iwai <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions