Re: [RFC v4 15/16] vfio/type1: Check MSI remapping at irq domain level

Hi Geetha, On 23/12/2016 14:33, Geetha Akula wrote: > Hi Eric, > > Seeing same issue reported by Diana on ThunderX with you > v4.9-reserved-v4 branch. > Vfio passthough work fine when allow_unsafe_interrupts is set. Thank you for testing! I will fix the security assessment by better studying

Re: [RFC v4 15/16] vfio/type1: Check MSI remapping at irq domain level

Hi Eric, Seeing same issue reported by Diana on ThunderX with you v4.9-reserved-v4 branch. Vfio passthough work fine when allow_unsafe_interrupts is set. Thank you, Geetha. On Thu, Dec 22, 2016 at 6:32 PM, Auger Eric wrote: > Hi Diana, > > On 22/12/2016 13:41, Diana

Re: [RFC v4 15/16] vfio/type1: Check MSI remapping at irq domain level

Hi Diana, On 22/12/2016 13:41, Diana Madalina Craciun wrote: > Hi Eric, > > On 12/13/2016 10:32 PM, Eric Auger wrote: >> In case the IOMMU does not bypass MSI transactions (typical >> case on ARM), we check all MSI controllers are IRQ remapping >> capable. If not the IRQ assignment may be

Re: [RFC v4 15/16] vfio/type1: Check MSI remapping at irq domain level

Hi Eric, On 12/13/2016 10:32 PM, Eric Auger wrote: > In case the IOMMU does not bypass MSI transactions (typical > case on ARM), we check all MSI controllers are IRQ remapping > capable. If not the IRQ assignment may be unsafe. > > At this stage the arm-smmu-(v3) still advertise the >

[RFC v4 15/16] vfio/type1: Check MSI remapping at irq domain level

In case the IOMMU does not bypass MSI transactions (typical case on ARM), we check all MSI controllers are IRQ remapping capable. If not the IRQ assignment may be unsafe. At this stage the arm-smmu-(v3) still advertise the IOMMU_CAP_INTR_REMAP capability at IOMMU level. This will be removed in