On 27/10/25 14:12, Alex Bennée wrote:
Philippe Mathieu-Daudé <[email protected]> writes:
Do not log unassigned MMIO accesses as I/O ones:
expose unassigned_mem_ops then use it instead of
unassigned_io_ops.
But why? Is it because ioport.c is a x86 io thing?
Mainly. But also because log is confusing.
This is part of a bigger PCI host-bridge address-spaces
rework.
Philippe Mathieu-Daudé (6):
system/memory: Expose unassigned_mem_ops symbol
hw/display/vga: Log unassigned MMIO accesses with unassigned_mem_ops
hw/pci-host/gpex: Log unassigned MMIO accesses with unassigned_mem_ops
hw/pci-host/aspeed: Log unassigned MMIO accesses with
unassigned_mem_ops
hw/pci-host/astro: Log unassigned MMIO accesses with
unassigned_mem_ops
hw/sparc64/ebus: Log unassigned MMIO accesses with unassigned_mem_ops
include/system/memory.h | 2 ++
system/memory-internal.h | 2 --
hw/display/bochs-display.c | 2 +-
hw/display/vga-pci.c | 4 ++--
hw/pci-host/aspeed_pcie.c | 2 +-
hw/pci-host/astro.c | 2 +-
hw/pci-host/gpex.c | 2 +-
hw/sparc64/sun4u.c | 2 +-
8 files changed, 9 insertions(+), 9 deletions(-)
