On Tue, Jul 29, 2025 at 06:51:27PM -0700, Chris Li wrote: > They follow a pattern that the original kernel needs to write to the > device and change the device state. The liveupdate device needs to > maintain the previous state not changed, therefore needs to prevent > such write initialization in liveupdate case. No, I fundamentally reject this position and your testing methodology. The new kernel *should* be writing to config space and it *should* be doing things like clearing and gaining control over MSI. It is fully wrong to be blocking it like you are doing just to satify some incorrect qemu based test checking for no config access. Only some config accesse are bad. Each and every "bad" one needs to be clearly explained *why* it is bad and only then mitigated. Most mitigation are far harder than just if'ing around the config write. My ATS/PASID/etc example for instance. Jason
