linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Wan Zongshun <vincent.wan@amd.com>,
	Joerg Roedel <joro@8bytes.org>,
	<iommu@lists.linux-foundation.org>
Cc: Borislav Petkov <bp@suse.de>, Ray Huang <ray.huang@amd.com>,
	<ken.xue@amd.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] iommu/amd: enable ACPI hardware ID device support
Date: Tue, 5 Jan 2016 09:40:27 -0600	[thread overview]
Message-ID: <568BE3EB.3010205@amd.com> (raw)
In-Reply-To: <1451988444-4694-1-git-send-email-vincent.wan@amd.com>

Hi All,

Also, 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

Thanks,
Suravee


On 01/05/2016 04:07 AM, Wan Zongshun wrote:
> From: Wan Zongshun <Vincent.Wan@amd.com>
>
> This patch series enable ACPI hardware ID device support,
>
> 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.
>
> 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 (3):
>    iommu/amd: Add new map for storing IVHD dev entry type HID
>    iommu/amd: Add support for non-pci devices
>    iommu/amd: Manage iommu_group for non-pci devices
>
>   Documentation/kernel-parameters.txt |   7 +
>   drivers/iommu/amd_iommu.c           | 158 +++++++++++++++---
>   drivers/iommu/amd_iommu_init.c      | 309 +++++++++++++++++++++++++++++++-----
>   drivers/iommu/amd_iommu_types.h     |  14 ++
>   4 files changed, 433 insertions(+), 55 deletions(-)
>

      parent reply	other threads:[~2016-01-05 15:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 10:07 [PATCH 0/6] iommu/amd: enable ACPI hardware ID device support Wan Zongshun
2016-01-05 10:07 ` [PATCH 1/6] iommu/amd: Modify ivhd_header structure to support type 11h and 40h Wan Zongshun
2016-01-05 10:07 ` [PATCH 2/6] iommu/amd: Use the most comprehensive IVHD type that the driver can support Wan Zongshun
2016-01-05 10:07 ` [PATCH 3/6] iommu/amd: Add new map for storing IVHD dev entry type HID Wan Zongshun
2016-01-05 10:07 ` [PATCH 4/6] iommu/amd: Introduces ivrs_acpihid kernel parameter Wan Zongshun
2016-01-05 10:07 ` [PATCH 5/6] iommu/amd: Add support for non-pci devices Wan Zongshun
2016-01-07 12:04   ` Joerg Roedel
2016-01-08  3:15     ` Wan ZongShun
2016-01-08 12:18       ` Joerg Roedel
2016-01-08 14:52         ` Wan Zongshun
2016-01-08 17:01           ` Joerg Roedel
2016-01-09  9:47             ` Wan Zongshun
2016-01-20 12:00               ` Joerg Roedel
2016-01-05 10:07 ` [PATCH 6/6] iommu/amd: Manage iommu_group " Wan Zongshun
2016-01-07 12:06   ` Joerg Roedel
2016-01-08  1:44     ` Wan ZongShun
2016-01-05 15:40 ` Suravee Suthikulpanit [this message]

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=568BE3EB.3010205@amd.com \
    --to=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=ray.huang@amd.com \
    --cc=vincent.wan@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).