diff options
| author |   Adrian Huang <adrianhuang0701@gmail.com> | 2019-11-14 14:14:47 +0800 |
|---|---|---|
| committer |   Joerg Roedel <jroedel@suse.de> | 2019-12-23 14:06:15 +0100 |
| commit | 387caf0b759ac437a65ad5d59665558025f350fc (patch) | |
| tree | 76ee0055b568b51eceb4033f5d913827c090d7ae /tools/include/trace/git:/ssh:/git@git.zx2c4.com | |
| parent | Linux 5.5-rc3 (diff) | |
| download | linux-dev-387caf0b759ac437a65ad5d59665558025f350fc.tar.xz linux-dev-387caf0b759ac437a65ad5d59665558025f350fc.zip | |
iommu/amd: Treat per-device exclusion ranges as r/w unity-mapped regions
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>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'tools/include/trace/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions