aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorIan Campbell <[email protected]>2011-10-03 15:37:00 +0100
committerThomas Gleixner <[email protected]>2011-10-17 11:42:49 +0200
commit9bab0b7fbaceec47d32db51cd9e59c82fb071f5a (patch)
tree19699e2c8463554c09fc44e3672c402687724d44 /tools/perf/util/scripting-engines/trace-event-python.c
parent32cffdde4a3ee6c2d9e0f0a94edecf1a9ce7586b (diff)
genirq: Add IRQF_RESUME_EARLY and resume such IRQs earlier
This adds a mechanism to resume selected IRQs during syscore_resume instead of dpm_resume_noirq. Under Xen we need to resume IRQs associated with IPIs early enough that the resched IPI is unmasked and we can therefore schedule ourselves out of the stop_machine where the suspend/resume takes place. This issue was introduced by 676dc3cf5bc3 "xen: Use IRQF_FORCE_RESUME". Signed-off-by: Ian Campbell <[email protected]> Cc: Rafael J. Wysocki <[email protected]> Cc: Jeremy Fitzhardinge <[email protected]> Cc: xen-devel <[email protected]> Cc: Konrad Rzeszutek Wilk <[email protected]> Link: http://lkml.kernel.org/r/[email protected] Cc: [email protected] (at least to 2.6.32.y) Signed-off-by: Thomas Gleixner <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions