From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH 5/6] hw/pci-host/sabre: Report IOMMU address range as unimplemented
Date: Mon, 19 Oct 2020 22:57:09 +0100 [thread overview]
Message-ID: <1bac5940-6e9d-fce8-6f42-bad484a94c34@ilande.co.uk> (raw)
In-Reply-To: <20201012170950.3491912-6-f4bug@amsat.org>
On 12/10/2020 18:09, Philippe Mathieu-Daudé wrote:
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> hw/pci-host/sabre.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/hw/pci-host/sabre.c b/hw/pci-host/sabre.c
> index 4412e23131c..67699ac9058 100644
> --- a/hw/pci-host/sabre.c
> +++ b/hw/pci-host/sabre.c
> @@ -122,6 +122,7 @@ static void sabre_config_write(void *opaque, hwaddr addr,
>
> switch (addr) {
> case 0x30 ... 0x4f: /* DMA error registers */
> + case 0x200 ... 0x21f: /* IOMMU registers */
> qemu_log_mask(LOG_UNIMP,
> "%s: Register 0x%02" HWADDR_PRIX " not implemented\n",
> __func__, addr);
> @@ -201,6 +202,7 @@ static uint64_t sabre_config_read(void *opaque,
>
> switch (addr) {
> case 0x30 ... 0x4f: /* DMA error registers */
> + case 0x200 ... 0x21f: /* IOMMU registers */
> qemu_log_mask(LOG_UNIMP,
> "%s: Register 0x%02" HWADDR_PRIX " not implemented\n",
> __func__, addr);
In theory this should never happen since a reference to the IOMMU should always be
set using an object property link (i.e. it is a developer error rather than an
unimplemented error) and its memory region overlaps this space within the PCI host
bridge.
Rather than add these logging statemants and/or failing if the property is not set, I
think now it may be possible to simply embed the IOMMU device within sabre itself
using the updated QOM APIs. I can take a look to see if this approach will work later
in the week.
ATB,
Mark.
next prev parent reply other threads:[~2020-10-19 21:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 17:09 [PATCH 0/6] hw/pci-host/sabre: Report UNIMP/GUEST_ERROR accesses Philippe Mathieu-Daudé
2020-10-12 17:09 ` [PATCH 1/6] hw/pci-host/sabre: Update documentation link Philippe Mathieu-Daudé
2020-10-19 19:01 ` Mark Cave-Ayland
2020-10-12 17:09 ` [PATCH 2/6] hw/pci-host/sabre: Remove superfluous address range check Philippe Mathieu-Daudé
2020-10-19 19:02 ` Mark Cave-Ayland
2020-10-12 17:09 ` [PATCH 3/6] hw/pci-host/sabre: Simplify code initializing variable once Philippe Mathieu-Daudé
2020-10-19 19:06 ` Mark Cave-Ayland
2020-10-12 17:09 ` [PATCH 4/6] hw/pci-host/sabre: Report unimplemented accesses via UNIMP log_mask Philippe Mathieu-Daudé
2020-10-19 21:52 ` Mark Cave-Ayland
2020-10-12 17:09 ` [PATCH 5/6] hw/pci-host/sabre: Report IOMMU address range as unimplemented Philippe Mathieu-Daudé
2020-10-19 21:57 ` Mark Cave-Ayland [this message]
2020-10-12 17:09 ` [PATCH 6/6] hw/pci-host/sabre: Log reserved address accesses as GUEST_ERROR Philippe Mathieu-Daudé
2020-10-19 21:58 ` Mark Cave-Ayland
2020-10-19 22:01 ` [PATCH 0/6] hw/pci-host/sabre: Report UNIMP/GUEST_ERROR accesses Mark Cave-Ayland
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=1bac5940-6e9d-fce8-6f42-bad484a94c34@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
/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).