From: Shuah Khan <shuahkhan@gmail.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] AMD IOMMU cleanups, fixes and IVRS bug workarounds
Date: Wed, 10 Apr 2013 10:06:02 -0600 [thread overview]
Message-ID: <CAKocOOP5tMsDLS8Wotu0kMNjSVJpN+pPhE9zj+n9ZKS9EcVR+A@mail.gmail.com> (raw)
In-Reply-To: <1365538384-12426-1-git-send-email-joro@8bytes.org>
On Tue, Apr 9, 2013 at 2:12 PM, Joerg Roedel <joro@8bytes.org> wrote:
> Hi,
>
> this patch-set contains some cleanups and patches for the
> AMD IOMM driver. The most important part is a workaround
> that can be used to get interrupt remapping working even the
> the IVRS table provided by the BIOS is broken.
>
>
> Joerg
>
> Joerg Roedel (9):
> iommu/amd: Remove map_sg_no_iommu()
> iommu/amd: Use AMD specific data structure for irq remapping
> iommu/amd: Properly initialize irq-table lock
> iommu/amd: Move add_special_device() to __init
> iommu/amd: Extend IVRS special device data structure
> iommu/amd: Add early maps for ioapic and hpet
> iommu/amd: Add ioapic and hpet ivrs override
> iommu/amd: Don't report firmware bugs with cmd-line ivrs overrides
> iommu/amd: Document ivrs_ioapic and ivrs_hpet parameters
>
> Documentation/kernel-parameters.txt | 14 ++++
> drivers/iommu/amd_iommu.c | 79 +++++++-----------
> drivers/iommu/amd_iommu_init.c | 151 +++++++++++++++++++++++++++++++----
> drivers/iommu/amd_iommu_types.h | 1 +
> 4 files changed, 182 insertions(+), 63 deletions(-)
>
Joerg,
Reviewed all the patches in this set. No longer have access to test machine. :(
Reviewed-by: Shuah Khan <shuahkhan@gmail.com>
-- Shuah
next prev parent reply other threads:[~2013-04-10 16:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 20:12 [PATCH 0/9] AMD IOMMU cleanups, fixes and IVRS bug workarounds Joerg Roedel
2013-04-09 20:12 ` [PATCH 1/9] iommu/amd: Remove map_sg_no_iommu() Joerg Roedel
2013-04-10 16:03 ` Shuah Khan
2013-04-09 20:12 ` [PATCH 2/9] iommu/amd: Use AMD specific data structure for irq remapping Joerg Roedel
2013-04-10 16:03 ` Shuah Khan
2013-04-09 20:12 ` [PATCH 3/9] iommu/amd: Properly initialize irq-table lock Joerg Roedel
2013-04-09 20:12 ` [PATCH 4/9] iommu/amd: Move add_special_device() to __init Joerg Roedel
2013-04-09 20:13 ` [PATCH 5/9] iommu/amd: Extend IVRS special device data structure Joerg Roedel
2013-04-09 20:13 ` [PATCH 6/9] iommu/amd: Add early maps for ioapic and hpet Joerg Roedel
2013-04-09 20:13 ` [PATCH 7/9] iommu/amd: Add ioapic and hpet ivrs override Joerg Roedel
2013-04-09 20:29 ` Joerg Roedel
2013-04-11 21:40 ` Suravee Suthikulanit
2013-04-12 8:04 ` Joerg Roedel
2013-04-09 20:13 ` [PATCH 8/9] iommu/amd: Don't report firmware bugs with cmd-line ivrs overrides Joerg Roedel
2013-04-10 15:59 ` Shuah Khan
2013-04-09 20:13 ` [PATCH 9/9] iommu/amd: Document ivrs_ioapic and ivrs_hpet parameters Joerg Roedel
2013-04-10 16:06 ` Shuah Khan [this message]
2013-04-12 8:06 ` [PATCH 0/9] AMD IOMMU cleanups, fixes and IVRS bug workarounds Joerg Roedel
2013-04-13 15:06 ` Andrew Cooks
2013-04-13 15:26 ` Joerg Roedel
2013-04-13 23:14 ` Shuah Khan
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=CAKocOOP5tMsDLS8Wotu0kMNjSVJpN+pPhE9zj+n9ZKS9EcVR+A@mail.gmail.com \
--to=shuahkhan@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).