summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorAnup Patel <apatel@ventanamicro.com>2025-02-17 14:26:51 +0530
committerThomas Gleixner <tglx@linutronix.de>2025-02-20 15:19:26 +0100
commite54b1b5e89ae765e6d71d41883a8f551fde8d0ab (patch)
tree75ce7b0cf85c88103d6aa61fbfeb55f7b0c732b0 /tools/perf/scripts/python/export-to-postgresql.py
parent751dc837dabd275d0ab165fc737c10f80e2e863a (diff)
genirq: Introduce irq_can_move_in_process_context()
Interrupt controller drivers which enable CONFIG_GENERIC_PENDING_IRQ require to know whether an interrupt can be moved in process context or not to decide whether they need to invoke the work around for non-atomic MSI updates or not. This information can be retrieved via irq_can_move_pcntxt(). That helper requires access to the top-most interrupt domain data, but the driver which requires this is usually further down in the hierarchy. Introduce irq_can_move_in_process_context() which retrieves that information from the top-most interrupt domain data. [ tglx: Massaged change log ] Signed-off-by: Anup Patel <apatel@ventanamicro.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/all/20250217085657.789309-6-apatel@ventanamicro.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions