From: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
To: Sairaj Kodilkar <sarunkod@amd.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org, vasant.hegde@amd.com,
suravee.suthikulpanit@amd.com
Cc: mst@redhat.com, imammedo@redhat.com, anisinha@redhat.com,
marcel.apfelbaum@gmail.com, pbonzini@redhat.com,
richard.henderson@linaro.org, eduardo@habkost.net,
yi.l.liu@intel.com, eric.auger@redhat.com,
zhenzhong.duan@intel.com, cohuck@redhat.com, seanjc@google.com,
iommu@lists.linux.dev, kevin.tian@intel.com, joro@8bytes.org
Subject: Re: [RFC PATCH RESEND 2/5] vfio/iommufd: Add amd specific hardware info struct to vendor capability
Date: Tue, 27 Jan 2026 20:25:11 -0500 [thread overview]
Message-ID: <804a631e-1690-489e-b2fb-5ddded3efaeb@oracle.com> (raw)
In-Reply-To: <20251118101532.4315-3-sarunkod@amd.com>
nit: Capitalize AMD on commit subject line?
On 11/18/25 5:15 AM, Sairaj Kodilkar wrote:
> Update the vendor capability structure to have `struct iommu_hw_info_amd`.
> AMD vIOMMU can use this to determine hardware features supported by the
> host IOMMU.
>
> Signed-off-by: Sairaj Kodilkar <sarunkod@amd.com>
> ---
> include/system/host_iommu_device.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/system/host_iommu_device.h b/include/system/host_iommu_device.h
> index ab849a4a82d5..cb1745b97a09 100644
> --- a/include/system/host_iommu_device.h
> +++ b/include/system/host_iommu_device.h
> @@ -20,6 +20,7 @@
> typedef union VendorCaps {
> struct iommu_hw_info_vtd vtd;
> struct iommu_hw_info_arm_smmuv3 smmuv3;
> + struct iommu_hw_info_amd amd;
> } VendorCaps;
>
> /**
next prev parent reply other threads:[~2026-01-28 1:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 10:15 [RFC PATCH RESEND 0/5] amd_iommu: support up to 2048 MSI vectors per IRT Sairaj Kodilkar
2025-11-18 10:15 ` [RFC PATCH RESEND 1/5] [DO NOT MERGE] linux-headers: Introduce struct iommu_hw_info_amd Sairaj Kodilkar
2025-11-18 10:15 ` [RFC PATCH RESEND 2/5] vfio/iommufd: Add amd specific hardware info struct to vendor capability Sairaj Kodilkar
2026-01-28 1:25 ` Alejandro Jimenez [this message]
2025-11-18 10:15 ` [RFC PATCH RESEND 3/5] amd-iommu: Add support for set/unset IOMMU for VFIO PCI devices Sairaj Kodilkar
2026-01-28 1:40 ` Alejandro Jimenez
2026-01-28 11:19 ` Sairaj Kodilkar
2025-11-18 10:15 ` [RFC PATCH RESEND 4/5] amd_iommu: Add support for extended feature register 2 Sairaj Kodilkar
2025-11-18 10:15 ` [RFC PATCH RESEND 5/5] amd_iommu: Add support for upto 2048 interrupts per IRT Sairaj Kodilkar
2026-01-28 1:59 ` Alejandro Jimenez
2026-01-28 11:23 ` Sairaj Kodilkar
2026-01-07 6:09 ` [RFC PATCH RESEND 0/5] amd_iommu: support up to 2048 MSI vectors " Sairaj Kodilkar
2026-01-28 1:23 ` Alejandro Jimenez
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=804a631e-1690-489e-b2fb-5ddded3efaeb@oracle.com \
--to=alejandro.j.jimenez@oracle.com \
--cc=anisinha@redhat.com \
--cc=cohuck@redhat.com \
--cc=eduardo@habkost.net \
--cc=eric.auger@redhat.com \
--cc=imammedo@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sarunkod@amd.com \
--cc=seanjc@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@intel.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