aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/irq
diff options
context:
space:
mode:
authorJason Gunthorpe <jgg@nvidia.com>2022-11-28 20:12:43 -0400
committerJason Gunthorpe <jgg@nvidia.com>2023-01-11 16:27:23 -0400
commitdcb83f6ec1bf08a44b3f19719b56e8dc18058ff5 (patch)
tree673604461aa0b881324d6382b5f9da15e0f93aa6 /kernel/irq
parenta5e72a6bac14181249ffd04f35f6a7c9bf47fbb9 (diff)
downloadlinux-dcb83f6ec1bf08a44b3f19719b56e8dc18058ff5.tar.gz
genirq/msi: Rename IRQ_DOMAIN_MSI_REMAP to IRQ_DOMAIN_ISOLATED_MSI
What x86 calls "interrupt remapping" is one way to achieve isolated MSI, make it clear this is talking about isolated MSI, no matter how it is achieved. This matches the new driver facing API name of msi_device_has_isolated_msi() No functional change. Link: https://lore.kernel.org/r/6-v3-3313bb5dd3a3+10f11-secure_msi_jgg@nvidia.com Tested-by: Matthew Rosato <mjrosato@linux.ibm.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'kernel/irq')
-rw-r--r--kernel/irq/msi.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/irq/msi.c b/kernel/irq/msi.c
index dfb5d40abac9e..ac5e224a11b9a 100644
--- a/kernel/irq/msi.c
+++ b/kernel/irq/msi.c
@@ -1645,7 +1645,7 @@ bool msi_device_has_isolated_msi(struct device *dev)
struct irq_domain *domain = dev_get_msi_domain(dev);
for (; domain; domain = domain->parent)
- if (domain->flags & IRQ_DOMAIN_FLAG_MSI_REMAP)
+ if (domain->flags & IRQ_DOMAIN_FLAG_ISOLATED_MSI)
return true;
return false;
}