> -----Original Message----- > From: Eric Auger <[email protected]> > Sent: 26 May 2026 13:09 > To: Shameer Kolothum Thodi <[email protected]>; qemu- > [email protected]; [email protected] > Cc: [email protected]; [email protected]; [email protected]; Nicolin > Chen <[email protected]>; Nathan Chen <[email protected]>; Matt > Ochs <[email protected]>; Jiandi An <[email protected]>; Jason Gunthorpe > <[email protected]>; [email protected]; Krishnakant Jaju > <[email protected]>; [email protected] > Subject: Re: [PATCH v5 31/32] hw/arm/smmuv3-accel: Enforce viommu > association when CMDQV is active > > External email: Use caution opening links or attachments > > > On 5/19/26 12:37 PM, Shameer Kolothum wrote: > > When CMDQV is active, the first cold-plugged VFIO device establishes > > the viommu to host SMMUv3 association. Block its hot-unplug to > > preserve this association and the guest's boot time CMDQV configuration. > > > > Also abort at machine_done if cmdqv=on is requested but no > > cold-plugged VFIO device was present to initialize it. > > To me this is still missing the "why", something along what you put in > https://lore.kernel.org/all/IA0PR12MB755515924AD70A273B7879A1AB3D > [email protected]/
Ok. I will summarise that and add into this commit msg. Thanks, Shameer
