diff options
| author | Joerg Roedel <jroedel@suse.de> | 2014-09-22 16:30:22 +0200 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2014-10-02 12:12:35 +0200 |
| commit | 80f7b3d1b1f4ec6c80fa3b40c7c9a419e28b0897 (patch) | |
| tree | 609362f89702c8a2933a691df949378ca1c50974 /drivers/iommu/msm_iommu.c | |
| parent | 57384592c43375d2c9a14d82aebbdc95fdda9e9d (diff) | |
| download | op-kernel-dev-80f7b3d1b1f4ec6c80fa3b40c7c9a419e28b0897.zip op-kernel-dev-80f7b3d1b1f4ec6c80fa3b40c7c9a419e28b0897.tar.gz | |
iommu/vt-d: Work around broken RMRR firmware entries
The VT-d specification states that an RMRR entry in the DMAR
table needs to specify the full path to the device. This is
also how newer Linux kernels implement it.
Unfortunatly older drivers just match for the target device
and not the full path to the device, so that BIOS vendors
implement that behavior into their BIOSes to make them work
with older Linux kernels. But those RMRR entries break on
newer Linux kernels.
Work around this issue by adding a fall-back into the RMRR
matching code to match those old RMRR entries too.
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu/msm_iommu.c')
0 files changed, 0 insertions, 0 deletions
