From: Dave Hansen <dave.hansen@intel.com>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"joro@8bytes.org" <joro@8bytes.org>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
"will@kernel.org" <will@kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"Hegde, Vasant" <Vasant.Hegde@amd.com>
Subject: Re: [PATCH V3 1/2] Documentation: x86: Add documentation for AMD IOMMU
Date: Wed, 30 Mar 2022 07:20:47 -0700 [thread overview]
Message-ID: <79bde999-cf8d-796b-1ddf-3cf612d28375@intel.com> (raw)
In-Reply-To: <BL1PR12MB5144C7172FCB8ED2C1AB013AF71F9@BL1PR12MB5144.namprd12.prod.outlook.com>
On 3/30/22 07:01, Deucher, Alexander wrote:
>> Just scanning this, it looks *awfully* generic. Is anything in
>> here AMD- specific? Should this be in an AMD-specific file?
> There is some information about the ACPI tables used to enumerate the
> IOMMUs and a link to the AMD IOMMU programming documentation. Would
> you prefer I just create a combined x86 IOMMU document?
Yeah, I think that would make a lot of sense. Let's just have one
document with an AMD section and an Intel section. Maybe just rename
the existing one to intel-iommu => x86-iommu.rst.
next prev parent reply other threads:[~2022-03-30 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 17:28 [PATCH V3 0/2] x86 IOMMU Documentation updates Alex Deucher
2022-03-28 17:28 ` [PATCH V3 1/2] Documentation: x86: Add documentation for AMD IOMMU Alex Deucher
2022-03-29 15:24 ` Dave Hansen
2022-03-30 14:01 ` Deucher, Alexander
2022-03-30 14:20 ` Dave Hansen [this message]
2022-03-28 17:28 ` [PATCH V3 2/2] Documentation: x86: Clarify Intel IOMMU documentation Alex Deucher
2022-03-29 6:38 ` Bagas Sanjaya
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=79bde999-cf8d-796b-1ddf-3cf612d28375@intel.com \
--to=dave.hansen@intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Vasant.Hegde@amd.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=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
all inboxes | Powered by JetHome®