summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJoerg Roedel <joerg.roedel@amd.com>2008-11-17 17:09:20 +0300
committerJoerg Roedel <joerg.roedel@amd.com>2008-11-18 17:44:31 +0300
commit3ce1f93c6d53c3f91c3846cf66b018276c8ac2e7 (patch)
treeb6dd5e06c031f03aa7c81da818e90c52569707f9 /Documentation
parente5e1f606ecbf67e52ebe2df5d14f8b94ec6544d0 (diff)
downloadlinux-3ce1f93c6d53c3f91c3846cf66b018276c8ac2e7.tar.xz
AMD IOMMU: enable device isolation per default
Impact: makes device isolation the default for AMD IOMMU Some device drivers showed double-free bugs of DMA memory while testing them with AMD IOMMU. If all devices share the same protection domain this can lead to data corruption and data loss. Prevent this by putting each device into its own protection domain per default. Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/kernel-parameters.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index b56ee02d2514..f2e1e7fc0ffd 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -294,7 +294,7 @@ and is between 256 and 4096 characters. It is defined in the file
Possible values are:
isolate - enable device isolation (each device, as far
as possible, will get its own protection
- domain)
+ domain) [default]
share - put every device behind one IOMMU into the
same protection domain
fullflush - enable flushing of IO/TLB entries when