On Fri, Nov 22, 2024 at 06:07:59PM +0100, Andrew Jones wrote: > > What you are trying to do is not supported by the software stack right > > now. You need to make much bigger, more intrusive changes, if you > > really want to make interrupt remapping dynamic. > > > > Let the fun begin. I'll look into this more. It also looks like I need to > collect some test cases to ensure I can support all use cases with > whatever I propose next. Pointers for those would be welcome. Sorry, I don't really have anything.. But iommufd allows changing the translation at will and we expect this to happen in normal VMM scenarios. So blocking, paging, nesting are all expected to be dynamically selectable and non-disruptive to interrupts. So, you can't decide if remapping is enabled or not for a device based only on the domain attachment. I think you'd need to create a way for VFIO to request dynamic interrupt remapping be enabled for the device very, very early in it's process and that would remain fixed while VFIO is using the device. The dynamic state of interrupt remapping would constrain what iommu attachment configurations are permitted. Jason
