Re: [PATCH v4 04/14] Documentation/x86: Secure Launch kernel documentation

From
Robin Murphy <robin.murphy@arm.com>
Date
2021-12-02 17:26:29
Also in
linux-integrity, linux-iommu, lkml
Reply to
Ross Philipson, 2021-08-27
On 2021-08-27 14:28, Ross Philipson wrote:
[...]
quoted hunk ↗ jump to hunk
+IOMMU Configuration
+-------------------
+
+When doing a Secure Launch, the IOMMU should always be enabled and the drivers
+loaded. However, IOMMU passthrough mode should never be used. This leaves the
+MLE completely exposed to DMA after the PMR's [2]_ are disabled. First, IOMMU
+passthrough should be disabled by default in the build configuration::
+
+  "Device Drivers" -->
+      "IOMMU Hardware Support" -->
+          "IOMMU passthrough by default [ ]"
+
+This unset the Kconfig value CONFIG_IOMMU_DEFAULT_PASSTHROUGH.
Note that the config structure has now changed, and if set, passthrough is deselected by choosing a different default domain type.
quoted hunk ↗ jump to hunk
+In addition, passthrough must be disabled on the kernel command line when doing
+a Secure Launch as follows::
+
+  iommu=nopt iommu.passthrough=0
This part is a bit silly - those options are literally aliases for the exact same thing, and furthermore if the config is already set as required then the sole effect either of them will have is to cause "(set by kernel command line)" to be printed. There is no value in explicitly overriding the default value with the default value - if anyone can append an additional "iommu.passthrough=1" (or "iommu=pt") to the end of the command line they'll still win.

Robin.
Thread (28 messages) 28 messages, 6 authors, last reply 2022-02-15
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help