From: Donald Dutile <ddutile@redhat.com>
To: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>,
qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, mtosatti@redhat.com, mst@redhat.com,
marcel.apfelbaum@gmail.com, jon.grimm@amd.com,
santosh.shukla@amd.com, vasant.hegde@amd.com, Wei.Huang2@amd.com,
kraxel@redhat.com, bsd@redhat.com, berrange@redhat.com
Subject: Re: [PATCH] pci-ids.rst: Add Red Hat pci-id for AMD IOMMU device
Date: Wed, 5 Mar 2025 15:28:51 -0500 [thread overview]
Message-ID: <24e0aff1-f95d-4da5-abc9-a16e71d0a4ac@redhat.com> (raw)
In-Reply-To: <61205b17-3556-45d5-87b2-347a9b2c2b69@amd.com>
On 3/4/25 9:56 PM, Suthikulpanit, Suravee wrote:
>
>
> On 3/5/2025 6:02 AM, Donald Dutile wrote:
>> Hi Suravee!
>>
>> Not your issue, but wondering if others know:
>>
>> Why isn't this an issue for Intel-vtd-iommu & ARM-SMMUV3 ?
>> Are they instantiated as non-PCI-id (platform) devices, but AMD puts their IOMMU in PCI space?
>>
>> Adv. thanks for the info.
>
> Unlike AMD IOMMU, Intel VT-d IOMMU and ARM SMMUV3 are not enumerated as a PCI device in the system.
>
> Thanks,
> Suravee
>
ok. thanks for confirmation.
--dd
next prev parent reply other threads:[~2025-03-05 20:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 18:37 [PATCH] pci-ids.rst: Add Red Hat pci-id for AMD IOMMU device Suravee Suthikulpanit
2025-03-04 18:46 ` Daniel P. Berrangé
2025-03-04 23:02 ` Donald Dutile
2025-03-05 2:56 ` Suthikulpanit, Suravee
2025-03-05 20:28 ` Donald Dutile [this message]
2025-03-05 6:52 ` Michael S. Tsirkin
2025-03-06 7:11 ` Yan Vugenfirer
2025-03-06 8:58 ` Daniel P. Berrangé
2025-03-07 2:44 ` Suthikulpanit, Suravee
2025-03-07 2:53 ` Suthikulpanit, Suravee
2025-03-09 6:47 ` Yan Vugenfirer
2025-03-09 13:44 ` Michael S. Tsirkin
2025-03-11 1:55 ` Suthikulpanit, Suravee
2025-03-12 12:43 ` Yan Vugenfirer
2025-05-11 13:27 ` Michael S. Tsirkin
2025-05-11 15:20 ` Yan Vugenfirer
2025-05-11 15:35 ` Michael S. Tsirkin
2025-03-10 13:57 ` Jonathan Cameron via
2025-03-11 8:08 ` Gerd Hoffmann
2025-03-12 18:18 ` Jonathan Cameron via
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=24e0aff1-f95d-4da5-abc9-a16e71d0a4ac@redhat.com \
--to=ddutile@redhat.com \
--cc=Wei.Huang2@amd.com \
--cc=berrange@redhat.com \
--cc=bsd@redhat.com \
--cc=jon.grimm@amd.com \
--cc=kraxel@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=santosh.shukla@amd.com \
--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 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).