On Sun, Oct 12, 2025 at 05:04:57PM -0700, Nicolin Chen wrote: > Add a new test_dev domain op for drivers to run a compatibility test prior > to the actual attachment at the driver level. Any incompatible attachment > will be rejected early, allowing the iommu core to postpone any concurrent > attachment during a device reset state.
I had to go back and find the original email from kevin to understand this.. This is a preparatory series for new iommu_dev_reset APIs: https://lore.kernel.org/all/[email protected]/ That series parks the domain attachment at BLOCKED during a device reset. To keep the uAPI this also required that any change in domain during this reset sequence is just recorded and kept in the background until the reset is finished. This creates a weird hole where userspace could propose to attach to a domain that is incompatible with the device during FLR, have that attach queued and then ultimately have the domain attach fail when the FLR concludes. This can be mitigated by splitting out the compatability test from the attach and having the core code check the compatability before accepting a queued domain attach. It was felt that the subtle uAPI change warrants this rework. Jason
