From: Auger Eric <eric.auger@redhat.com>
To: Simon Veith <sveith@amazon.de>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [PATCH v3 0/6] hw/arm/smmuv3: Correct stream ID and event address handling
Date: Tue, 17 Dec 2019 11:03:59 +0100 [thread overview]
Message-ID: <e0a55905-e76e-40d2-3d9b-06ea5b917001@redhat.com> (raw)
In-Reply-To: <1576509312-13083-1-git-send-email-sveith@amazon.de>
Hi,
On 12/16/19 4:15 PM, Simon Veith wrote:
> While working on the Linux SMMUv3 driver, I noticed a few cases where the QEMU
> SMMUv3 behavior relating to stream tables was inconsistent with our hardware.
>
> Also, when debugging those differences, I found that the errors reported through
> the QEMU SMMUv3 event queue contained the address fields in an incorrect
> position.
>
> These patches correct the QEMU SMMUv3 behavior to match the specification (and
> the behavior that I observed in our hardware). Linux guests normally will not
> notice these issues, but other SMMUv3 driver implementations might.
>
> Changes in v2:
>
> * New patch "hw/arm/smmuv3: Correct SMMU_BASE_ADDR_MASK value" added
> * Updated patch "hw/arm/smmuv3: Check stream IDs against actual table LOG2SIZE"
> * Updated patch "hw/arm/smmuv3: Align stream table base address to table size"
>
> Changes in v3:
>
> * No changes, but sending again to correct a patch submission mishap that
> confused Patchew
>
> Simon Veith (6):
> hw/arm/smmuv3: Apply address mask to linear strtab base address
> hw/arm/smmuv3: Correct SMMU_BASE_ADDR_MASK value
> hw/arm/smmuv3: Check stream IDs against actual table LOG2SIZE
> hw/arm/smmuv3: Align stream table base address to table size
> hw/arm/smmuv3: Use correct bit positions in EVT_SET_ADDR2 macro
> hw/arm/smmuv3: Report F_STE_FETCH fault address in correct word
> position
The series looks good to me. Also tested against non regression.
Tested-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
>
> hw/arm/smmuv3-internal.h | 6 +++---
> hw/arm/smmuv3.c | 28 +++++++++++++++++++++-------
> 2 files changed, 24 insertions(+), 10 deletions(-)
>
next prev parent reply other threads:[~2019-12-17 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 15:15 [PATCH v3 0/6] hw/arm/smmuv3: Correct stream ID and event address handling Simon Veith
2019-12-16 15:15 ` [PATCH v3 1/6] hw/arm/smmuv3: Apply address mask to linear strtab base address Simon Veith
2019-12-16 15:15 ` [PATCH v3 2/6] hw/arm/smmuv3: Correct SMMU_BASE_ADDR_MASK value Simon Veith
2019-12-17 8:55 ` Auger Eric
2019-12-16 15:15 ` [PATCH v3 3/6] hw/arm/smmuv3: Check stream IDs against actual table LOG2SIZE Simon Veith
2019-12-17 8:54 ` Auger Eric
2019-12-16 15:15 ` [PATCH v3 4/6] hw/arm/smmuv3: Align stream table base address to table size Simon Veith
2019-12-17 9:40 ` Auger Eric
2019-12-16 15:15 ` [PATCH v3 5/6] hw/arm/smmuv3: Use correct bit positions in EVT_SET_ADDR2 macro Simon Veith
2019-12-16 15:15 ` [PATCH v3 6/6] hw/arm/smmuv3: Report F_STE_FETCH fault address in correct word position Simon Veith
2019-12-17 10:03 ` Auger Eric [this message]
2019-12-17 15:25 ` [PATCH v3 0/6] hw/arm/smmuv3: Correct stream ID and event address handling 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=e0a55905-e76e-40d2-3d9b-06ea5b917001@redhat.com \
--to=eric.auger@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sveith@amazon.de \
/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).