You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
adding the iommu=pt kernel parameter puts the IOMMU into "enabled but only used for virtualization" mode, where the device's view of ram is mapped 1:1 with actual physical RAM.
This tends to be seen on sandy-bridge-era platforms due to some IOTLB errata (that I can't actually find) that drags system performance down to that of a pentium 2, but can also be used on platforms that cannot disable the iommu for whatever reason.
The text was updated successfully, but these errors were encountered:
on systems that can't disable IOMMU in BIOS, I'd imagine iommu=off would work just as well? Of course, then you don't get IOMMU available for virt as you do with pt, but I'm thinking just for systems that will only be used temporarily for flashing
as a followup, turns out the global iommu=off also partly disables SWIOMMU, which is kernel panic city. on modern x86 systems the correct options would be intel_iommu=off & amd_iommu=off. The customer kernel procline options for my LSI flashing live ISOs are the following now, which seems to have gotten the best compatibility across systems used by my guide users:
adding the
iommu=pt
kernel parameter puts the IOMMU into "enabled but only used for virtualization" mode, where the device's view of ram is mapped 1:1 with actual physical RAM.This tends to be seen on sandy-bridge-era platforms due to some IOTLB errata (that I can't actually find) that drags system performance down to that of a pentium 2, but can also be used on platforms that cannot disable the iommu for whatever reason.
The text was updated successfully, but these errors were encountered: