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 <[email protected]> > Signed-off-by: Adrian Huang <[email protected]> > --- > drivers/iommu/amd_iommu_init.c | 20 ++++++++++---------- > 1 file changed, 10 insertions(+), 10 deletions(-)
Applied, thanks. _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
