From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Joel Stanley" <joel@jms.id.au>,
qemu-arm@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
"David Hildenbrand" <david@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Troy Lee" <leetroy@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Helge Deller" <deller@gmx.de>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Peter Xu" <peterx@redhat.com>,
"Artyom Tarasenko" <atar4qemu@gmail.com>,
"Jamin Lin" <jamin_lin@aspeedtech.com>
Subject: Re: [PATCH 0/6] hw: Log unassigned MMIO accesses with unassigned_mem_ops
Date: Mon, 27 Oct 2025 13:12:25 +0000 [thread overview]
Message-ID: <87pla8xzd2.fsf@draig.linaro.org> (raw)
In-Reply-To: <20251027123644.63487-1-philmd@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Mon, 27 Oct 2025 13:36:37 +0100")
Philippe Mathieu-Daudé <philmd@linaro.org> 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?
>
> 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(-)
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-10-27 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 12:36 [PATCH 0/6] hw: Log unassigned MMIO accesses with unassigned_mem_ops Philippe Mathieu-Daudé
2025-10-27 12:36 ` [PATCH 1/6] system/memory: Expose unassigned_mem_ops symbol Philippe Mathieu-Daudé
2025-10-27 12:36 ` [PATCH 2/6] hw/display/vga: Log unassigned MMIO accesses with unassigned_mem_ops Philippe Mathieu-Daudé
2025-10-27 12:36 ` [PATCH 3/6] hw/pci-host/gpex: " Philippe Mathieu-Daudé
2025-10-27 12:36 ` [PATCH 4/6] hw/pci-host/aspeed: " Philippe Mathieu-Daudé
2025-10-27 12:36 ` [PATCH 5/6] hw/pci-host/astro: " Philippe Mathieu-Daudé
2025-10-27 12:36 ` [PATCH 6/6] hw/sparc64/ebus: " Philippe Mathieu-Daudé
2025-10-27 13:12 ` Alex Bennée [this message]
2025-10-27 13:21 ` [PATCH 0/6] hw: " Philippe Mathieu-Daudé
2025-10-27 13:26 ` Peter Maydell
2025-10-27 13:33 ` Philippe Mathieu-Daudé
2025-10-27 13:47 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pla8xzd2.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=andrew@codeconstruct.com.au \
--cc=atar4qemu@gmail.com \
--cc=clg@kaod.org \
--cc=david@redhat.com \
--cc=deller@gmx.de \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=kraxel@redhat.com \
--cc=leetroy@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=steven_lee@aspeedtech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).