From: Sairaj Kodilkar <sarunkod@amd.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
Ani Sinha <anisinha@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
Igor Mammedov <imammedo@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Sairaj Kodilkar <sarunkod@amd.com>, <qemu-devel@nongnu.org>
Cc: <vasant.hegde@amd.com>, <suravee.suthikulpanit@amd.com>
Subject: [PATCH 0/8] acpi_build: Refactor and cleanup AMD IVRS build
Date: Mon, 11 May 2026 18:09:29 +0530 [thread overview]
Message-ID: <20260511123937.32743-1-sarunkod@amd.com> (raw)
This series aims to improve redability and maintainibility of the the AMD IVRS
building by introducing macros and packed structs which represents IVRS, IVHDs
headers and IVHD device entries.
The goal is to land a maintainable baseline before adding AMD
hardware-accelerated vIOMMU support in QEMU, where we will require multiple
vIOMMUs attached to different pcie-pxb buses in order to serve set of
passthrough devices.
Please refer to AMD IOMMU spec [1] for more details about IVRS.
[1] https://docs.amd.com/api/khub/documents/GD6kOXjzWsek8QUbn_qMvg/content
Sairaj Kodilkar (8):
tests/acpi: x86: Allow IVRS acpi table changes
amd_iommu: update PA, GVA and VA size macros
amd_iommu: Return empty efr for stub call
acpi_build: Use IOMMU pci device to build IOMMU device ID
acpi_build: Introduce necessary macros and structs for AMD IOMMU IVRS
acpi_build: Build IVRS feature report using extended feature register
acpi_build: Cleanup AMD IOMMU IVRS building
tests/acpi: x86: update golden masters for IVRS
hw/i386/acpi-build.c | 191 +++++++++++++++++++--------------------
hw/i386/acpi-build.h | 93 ++++++++++++++++++-
hw/i386/amd_iommu-stub.c | 2 +-
hw/i386/amd_iommu.c | 2 +-
hw/i386/amd_iommu.h | 12 ++-
5 files changed, 195 insertions(+), 105 deletions(-)
--
2.34.1
next reply other threads:[~2026-05-11 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 12:39 Sairaj Kodilkar [this message]
2026-05-11 12:39 ` [PATCH 1/8] tests/acpi: x86: Allow IVRS acpi table changes Sairaj Kodilkar
2026-05-11 12:39 ` [PATCH 2/8] amd_iommu: update PA, GVA and VA size macros Sairaj Kodilkar
2026-05-19 8:39 ` Vasant Hegde
2026-05-11 12:39 ` [PATCH 3/8] amd_iommu: Return empty efr for stub call Sairaj Kodilkar
2026-05-11 12:39 ` [PATCH 4/8] acpi_build: Use IOMMU pci device to build IOMMU device ID Sairaj Kodilkar
2026-05-11 12:39 ` [PATCH 5/8] acpi_build: Introduce necessary macros and structs for AMD IOMMU IVRS Sairaj Kodilkar
2026-05-11 12:39 ` [PATCH 6/8] acpi_build: Build IVRS feature report using extended feature register Sairaj Kodilkar
2026-05-19 8:43 ` Vasant Hegde
2026-05-11 12:39 ` [PATCH 7/8] acpi_build: Cleanup AMD IOMMU IVRS building Sairaj Kodilkar
2026-05-11 12:39 ` [PATCH 8/8] tests/acpi: x86: update golden masters for IVRS Sairaj Kodilkar
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=20260511123937.32743-1-sarunkod@amd.com \
--to=sarunkod@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=anisinha@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.