From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Cc: qemu-devel@nongnu.org, sarunkod@amd.com, qemu@demindiro.com,
imammedo@redhat.com, peter.maydell@linaro.org,
philmd@oss.qualcomm.com
Subject: Re: [PATCH 0/5] amd_iommu fixes staged for 11.1
Date: Wed, 1 Jul 2026 02:36:17 -0400 [thread overview]
Message-ID: <20260701023508-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260630220806.1758748-1-alejandro.j.jimenez@oracle.com>
On Tue, Jun 30, 2026 at 10:08:01PM +0000, Alejandro Jimenez wrote:
> Hi Michael,
>
> I have staged these recently reviewed AMD vIOMMU fixes for 11.1:
>
> https://github.com/aljimenezb/qemu/commits/amdvi-next
> Base: 30e8a06b64aa ("Merge tag 'net-pull-request' of https://github.com/jasowang/qemu into staging")
> Tip: 018c1dfb3e8c ("amd_iommu: Fix endianness handling for command buffer entries")
>
> Patch 1 is an independent fix previously posted at:
> https://lore.kernel.org/qemu-devel/20260616174620.438468-1-alejandro.j.jimenez@oracle.com/
>
> Patches 2-5 address a Coverity finding and big-endian portability
> issues. They were reviewed in:
> https://lore.kernel.org/qemu-devel/20260624195925.1254462-1-alejandro.j.jimenez@oracle.com/
Great, I'm applying these. Thanks!
>
> I did basic smoke testing on an AMD Zen4 host using the AMD vIOMMU device.
> Completed several guest boot and reboot cycles with xtsup both enabled and
> disabled. No regressions were observed in guest startup or reboot behavior.
>
> There are two other outstanding series pending review, but I am unlikely to
> complete review/testing by myself for those before the upcoming soft-freeze
> deadline.
>
> Thank you,
> Alejandro
To be frank, these are bugfixes and such changes are okay after soft freeze. Thanks!
> Alejandro Jimenez (4):
> amd_iommu: Return int from page walk status helpers
> amd_iommu: Decode XT interrupt control register without bitfields
> amd_iommu: Decode IRTEs without bitfields
> amd_iommu: Fix endianness handling for command buffer entries
>
> David Hoppenbrouwers (1):
> amd_iommu: Fix opcode reported in invalid command handling
>
> hw/i386/amd_iommu.c | 168 +++++++++++++++++++++++++++++++-------------
> hw/i386/amd_iommu.h | 63 -----------------
> 2 files changed, 120 insertions(+), 111 deletions(-)
>
>
> base-commit: 30e8a06b64aa58a3990ba39cb5d09531e7d265e0
> --
> 2.47.3
prev parent reply other threads:[~2026-07-01 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 22:08 [PATCH 0/5] amd_iommu fixes staged for 11.1 Alejandro Jimenez
2026-06-30 22:08 ` [PATCH 1/5] amd_iommu: Fix opcode reported in invalid command handling Alejandro Jimenez
2026-06-30 22:08 ` [PATCH 2/5] amd_iommu: Return int from page walk status helpers Alejandro Jimenez
2026-06-30 22:23 ` Philippe Mathieu-Daudé
2026-06-30 22:08 ` [PATCH 3/5] amd_iommu: Decode XT interrupt control register without bitfields Alejandro Jimenez
2026-06-30 22:08 ` [PATCH 4/5] amd_iommu: Decode IRTEs " Alejandro Jimenez
2026-06-30 22:21 ` Philippe Mathieu-Daudé
2026-06-30 22:08 ` [PATCH 5/5] amd_iommu: Fix endianness handling for command buffer entries Alejandro Jimenez
2026-06-30 22:21 ` Philippe Mathieu-Daudé
2026-07-01 6:36 ` Michael S. Tsirkin [this message]
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=20260701023508-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu@demindiro.com \
--cc=sarunkod@amd.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