summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorYu Zhao <yuzhao@google.com>2018-12-06 14:39:15 -0700
committerJoerg Roedel <jroedel@suse.de>2018-12-07 14:07:24 +0100
commitc12b08ebbe16f0d3a96a116d86709b04c1ee8e74 (patch)
treef4e7e9316f80d2b7d15c554a997466b27cba50ed /README
parent6f5086a6e3383ae6a1b08a88836fcfda7d171ca4 (diff)
downloadlinux-c12b08ebbe16f0d3a96a116d86709b04c1ee8e74.tar.gz
linux-c12b08ebbe16f0d3a96a116d86709b04c1ee8e74.tar.bz2
linux-c12b08ebbe16f0d3a96a116d86709b04c1ee8e74.zip
iommu/amd: Fix amd_iommu=force_isolation
The parameter is still there but it's ignored. We need to check its value before deciding to go into passthrough mode for AMD IOMMU v2 capable device. We occasionally use this parameter to force v2 capable device into translation mode to debug memory corruption that we suspect is caused by DMA writes. To address the following comment from Joerg Roedel on the first version, v2 capability of device is completely ignored. > This breaks the iommu_v2 use-case, as it needs a direct mapping for the > devices that support it. And from Documentation/admin-guide/kernel-parameters.txt: This option does not override iommu=pt Fixes: aafd8ba0ca74 ("iommu/amd: Implement add_device and remove_device") Signed-off-by: Yu Zhao <yuzhao@google.com> Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions