From: Wan Zongshun <vincent.wan@amd.com>
To: Joerg Roedel <joro@8bytes.org>, <iommu@lists.linux-foundation.org>
Cc: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
Borislav Petkov <bp@suse.de>, Ray Huang <ray.huang@amd.com>,
<ken.xue@amd.com>, <vw@iommu.org>, <mcuos.com@gmail.com>,
<linux-kernel@vger.kernel.org>,
"Wan Zongshun" <Vincent.Wan@amd.com>
Subject: [PATCH V2 0/8] iommu/amd: enable ACPI hardware ID device support
Date: Tue, 26 Jan 2016 18:14:29 -0500 [thread overview]
Message-ID: <1453850077-2539-1-git-send-email-vincent.wan@amd.com> (raw)
From: Wan Zongshun <Vincent.Wan@amd.com>
There are some devices indentified using ACPI HID format in AMD chip.
This patch series enable iommu support for those ACPI HID device,
since the existing AMD iommu only supports PCI bus based device.
The latest public version of AMD IOMMU specification that describes
the support for IVHD type 40h and ACPI HID IVHD device type,
implemented by this patch series, is available here:
http://support.amd.com/TechDocs/48882_IOMMU.pdf
The V2 adds two new patches: patch 5 and patch 8 according to Joerg's
comments.
There is a little modification in patch 6 to distinguish pci and none pci.
Suravee Suthikulpanit (3):
iommu/amd: Modify ivhd_header structure to support type 11h and 40h
iommu/amd: Use the most comprehensive IVHD type that the driver can
support
iommu/amd: Introduces ivrs_acpihid kernel parameter
Wan Zongshun (5):
iommu/amd: Add new map for storing IVHD dev entry type HID
iommu/amd: Make call-sites of get_device_id aware of its return value
iommu/amd: Add iommu support for ACPI HID devices
iommu/amd: Manage iommu_group for ACPI HID devices
iommu/amd: Set AMD iommu callbacks for amba bus
Documentation/kernel-parameters.txt | 7 +
drivers/iommu/amd_iommu.c | 167 ++++++++++++++++---
drivers/iommu/amd_iommu_init.c | 309 +++++++++++++++++++++++++++++++-----
drivers/iommu/amd_iommu_types.h | 14 ++
4 files changed, 440 insertions(+), 57 deletions(-)
--
1.9.1
next reply other threads:[~2016-01-26 15:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 23:14 Wan Zongshun [this message]
2016-01-26 23:14 ` [PATCH V2 1/8] iommu/amd: Modify ivhd_header structure to support type 11h and 40h Wan Zongshun
2016-01-26 23:14 ` [PATCH V2 2/8] iommu/amd: Use the most comprehensive IVHD type that the driver can support Wan Zongshun
2016-01-26 23:14 ` [PATCH V2 3/8] iommu/amd: Add new map for storing IVHD dev entry type HID Wan Zongshun
2016-01-26 23:14 ` [PATCH V2 4/8] iommu/amd: Introduces ivrs_acpihid kernel parameter Wan Zongshun
2016-01-26 23:14 ` [PATCH V2 5/8] iommu/amd: Make call-sites of get_device_id aware of its return value Wan Zongshun
2016-01-26 23:14 ` [PATCH V2 6/8] iommu/amd: Add iommu support for ACPI HID devices Wan Zongshun
2016-01-26 23:14 ` [PATCH V2 7/8] iommu/amd: Manage iommu_group " Wan Zongshun
2016-01-26 23:14 ` [PATCH V2 8/8] iommu/amd: Set AMD iommu callbacks for amba bus Wan Zongshun
2016-02-26 14:44 ` [PATCH V2 0/8] iommu/amd: enable ACPI hardware ID device support Joerg Roedel
2016-03-04 1:52 ` Wan, Vincent
2016-03-04 8:46 ` Joerg Roedel
2016-03-04 8:49 ` Wan, Vincent
2016-03-05 9:00 ` Suravee Suthikulpanit
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=1453850077-2539-1-git-send-email-vincent.wan@amd.com \
--to=vincent.wan@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=bp@suse.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=ken.xue@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcuos.com@gmail.com \
--cc=ray.huang@amd.com \
--cc=vw@iommu.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®