From: Joerg Roedel <joro@8bytes.org>
To: Adrian Huang <adrianhuang0701@gmail.com>
Cc: iommu@lists.linux-foundation.org, Adrian Huang <ahuang12@lenovo.com>
Subject: Re: [PATCH 1/1] iommu/amd: Treat per-device exclusion ranges as r/w unity-mapped regions
Date: Tue, 17 Dec 2019 10:30:44 +0100 [thread overview]
Message-ID: <20191217093043.GB8689@8bytes.org> (raw)
In-Reply-To: <20191114061447.14604-1-ahuang12@lenovo.com>
On Thu, Nov 14, 2019 at 02:14:47PM +0800, Adrian Huang wrote:
> Some buggy BIOSes might define multiple exclusion ranges of the
> IVMD entries which are associated with the same IOMMU hardware.
> This leads to the overwritten exclusion range (exclusion_start
> and exclusion_length members) in set_device_exclusion_range().
>
> Here is a real case:
> When attaching two Broadcom RAID controllers to a server, the first
> one reports the failure during booting (the disks connecting to the
> RAID controller cannot be detected).
>
> This patch prevents the issue by treating per-device exclusion
> ranges as r/w unity-mapped regions.
>
> Discussion:
> * https://lists.linuxfoundation.org/pipermail/iommu/2019-November/040140.html
>
> Suggested-by: Joerg Roedel <joro@8bytes.org>
> Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
> ---
> drivers/iommu/amd_iommu_init.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
Applied, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2019-12-17 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 6:14 [PATCH 1/1] iommu/amd: Treat per-device exclusion ranges as r/w unity-mapped regions Adrian Huang
2019-12-17 9:30 ` Joerg Roedel [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=20191217093043.GB8689@8bytes.org \
--to=joro@8bytes.org \
--cc=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=iommu@lists.linux-foundation.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).