15 Feb
2023
15 Feb
'23
12:51 p.m.
On Tue, Feb 14, 2023 at 11:15:09PM -0800, Nicolin Chen wrote:
But things will be out of control, if user space continues mapping something onto domain1's iopt for idev2, even after it is attached covertly to domain2's iopt by the replace routine. I wonder how kernel should handle this and keep the consistency between IOMMUFD objects and iommu_group.
I've been looking at this, the reason the locking is such a PITA is because we are still trying to use the device list short cut.
We need to have a iommu group object instead then everything will work smoothly.
Jason