mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-28 13:22:57 +00:00
bf210f7939
s390 doesn't use irq_domains, so it has no place to set IRQ_DOMAIN_FLAG_ISOLATED_MSI. Instead of continuing to abuse the iommu subsystem to convey this information add a simple define which s390 can make statically true. The define will cause msi_device_has_isolated() to return true. Remove IOMMU_CAP_INTR_REMAP from the s390 iommu driver. Link: https://lore.kernel.org/r/8-v3-3313bb5dd3a3+10f11-secure_msi_jgg@nvidia.com Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com> Tested-by: Matthew Rosato <mjrosato@linux.ibm.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
17 lines
527 B
C
17 lines
527 B
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
#ifndef _ASM_S390_MSI_H
|
|
#define _ASM_S390_MSI_H
|
|
#include <asm-generic/msi.h>
|
|
|
|
/*
|
|
* Work around S390 not using irq_domain at all so we can't set
|
|
* IRQ_DOMAIN_FLAG_ISOLATED_MSI. See for an explanation how it works:
|
|
*
|
|
* https://lore.kernel.org/r/31af8174-35e9-ebeb-b9ef-74c90d4bfd93@linux.ibm.com/
|
|
*
|
|
* Note this is less isolated than the ARM/x86 versions as userspace can trigger
|
|
* MSI belonging to kernel devices within the same gisa.
|
|
*/
|
|
#define arch_is_isolated_msi() true
|
|
|
|
#endif
|