5c83b2f5b4
The old logic didn't work as intended when an access spanned multiple fields (for example a 32-bit access to the location of the MSI Message Data field with the high 16 bits not being covered by any known field). Remove it and derive which fields not to write to from the accessed fields' emulation masks: When they're all ones, there's no point in doing any host write. This fixes a secondary issue at once: We obviously shouldn't make any host write attempt when already the host read failed. This is XSA-128. Signed-off-by: Jan Beulich <jbeulich@suse.com> Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> |
||
|---|---|---|
| .. | ||
| Makefile.objs | ||
| xen_backend.c | ||
| xen_devconfig.c | ||
| xen_pt_config_init.c | ||
| xen_pt_msi.c | ||
| xen_pt.c | ||
| xen_pt.h | ||
| xen-host-pci-device.c | ||
| xen-host-pci-device.h | ||