summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/radixtree.py
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2025-09-03 16:04:46 +0200
committerThomas Gleixner <tglx@linutronix.de>2025-09-09 14:44:30 +0200
commitf09c1d63e895e1b45248a75656a41df2e8102874 (patch)
treeda72bddf8de7b398f028501710ab7679a6b235a0 /scripts/gdb/linux/radixtree.py
parentb2a0c13f8b4fc3f6c8b279fdc4395a5fa57dda5d (diff)
irqchip/msi-lib: Honor the MSI_FLAG_PCI_MSI_MASK_PARENT flag
For systems that implement interrupt masking at the interrupt controller level, the MSI library offers MSI_FLAG_PCI_MSI_MASK_PARENT. It indicates that it isn't enough to only unmask the interrupt at the PCI device level, but that the interrupt controller must also be involved. However, the way this is currently done is less than optimal, as the masking/unmasking is done on both sides, always. It would be far cheaper to unmask both at the start of times, and then only deal with the interrupt controller mask, which is cheaper than a round-trip to the PCI endpoint. Now that the PCI/MSI layer implements irq_startup() and irq_shutdown() callbacks, which [un]mask at the PCI level and honor the request to [un]mask the parent, this can be trivially done. Overwrite the irq_mask/unmask() callbacks of the device domain interrupt chip with irq_[un]mask_parent() when the parent domain asks for it. [ tglx: Adopted to the PCI/MSI changes ] Signed-off-by: Marc Zyngier <maz@kernel.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Tested-by: Marc Zyngier <maz@kernel.org> Acked-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/all/20250903135433.380783272@linutronix.de
Diffstat (limited to 'scripts/gdb/linux/radixtree.py')
0 files changed, 0 insertions, 0 deletions