iommu/vt-d bad RMRR workarounds
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 3 repliesIn review
- v13 patches 8 repliesSuperseded
Changes in v2 from the cover letter
v1: https://lore.kernel.org/lkml/[email protected]/
- Added the TAINT_FIRMWARE_WORKAROUND
- Dropped the commit that treated missing e820 regions as "RMRR OK"
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | iommu/vt-d: skip RMRR entries that fail the sanity checkdrivers/ | +10 | 0 replies | |
| 2/2 | iommu/vt-d: skip invalid RMRR entriesdrivers/ | +13 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/2] iommu/vt-d bad RMRR workarounds
Commit f036c7fa0ab6 ("iommu/vt-d: Check VT-d RMRR region in BIOS is reported as reserved") caused a machine to fail to boot for me, but only after a kexec.
Buggy firmware provided an RMRR entry with base and end both == 0. That is an invalid RMRR format, and only happens to pass the RMRR sanity check. After a kexec, that entry fails the RMRR sanity check, due to a slight change in the first e820 mapping. See the v1 link for details.
v1->v2:
v1: https://lore.kernel.org/lkml/[email protected]/
- Added the TAINT_FIRMWARE_WORKAROUND
- Dropped the commit that treated missing e820 regions as "RMRR OK"
Barret Rhoden (2):
iommu/vt-d: skip RMRR entries that fail the sanity check iommu/vt-d: skip invalid RMRR entries
drivers/iommu/intel-iommu.c | 26 ++++++++++++++++++++++---- 1 file changed, 22 insertions(+), 4 deletions(-)
Signature · 1 line
2.24.1.735.g03f4e72817-goog