From: Dave Hansen <dave.hansen@intel.com>
To: Alex Deucher <alexander.deucher@amd.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, hpa@zytor.com, x86@kernel.org,
dave.hansen@linux.intel.com, bp@alien8.de, mingo@redhat.com,
tglx@linutronix.de, joro@8bytes.org,
suravee.suthikulpanit@amd.com, will@kernel.org,
iommu@lists.linux-foundation.org, robin.murphy@arm.com, "Raj,
Ashok" <ashok.raj@intel.com>
Subject: Re: [PATCH 2/2] Documentation: x86: Clarify Intel IOMMU documenation
Date: Wed, 9 Mar 2022 10:36:54 -0800 [thread overview]
Message-ID: <42641969-c958-847c-4d6e-baa14d847545@intel.com> (raw)
In-Reply-To: <20220309175805.1298503-2-alexander.deucher@amd.com>
> -ACPI enumerates and lists the different DMA engines in the platform, and
> -device scope relationships between PCI devices and which DMA engine controls
> +ACPI enumerates and lists the different IOMMUs in the platform, and
> +device scope relationships between PCI devices and which IOMMU controls
> them.
Isn't this just a really long-winded way of saying:
ACPI enumerates both the IOMMUs in the platform and which IOMMU
controls a specific PCI device.
?
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-03-09 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 17:58 [PATCH v2 1/2] Documentation: x86: Add documenation for AMD IOMMU Alex Deucher via iommu
2022-03-09 17:58 ` [PATCH 2/2] Documentation: x86: Clarify Intel IOMMU documenation Alex Deucher via iommu
2022-03-09 18:36 ` Dave Hansen [this message]
2022-03-10 4:17 ` [PATCH v2 1/2] Documentation: x86: Add documenation for AMD IOMMU Vasant Hegde via iommu
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=42641969-c958-847c-4d6e-baa14d847545@intel.com \
--to=dave.hansen@intel.com \
--cc=alexander.deucher@amd.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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