Revision 8aafaaf2212192012f5bae305bb31cdf7681d777 authored by Joerg Roedel on 28 March 2019, 10:44:59 UTC, committed by Joerg Roedel on 29 March 2019, 16:12:57 UTC
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't happened until now and can cause
data corruption on data transfered with these devices.

Treat exclusion ranges as reserved regions in the iommu-core
to fix the problem.

Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory mapping requirements for devices')
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: Gary R Hook <gary.hook@amd.com>
1 parent 8bc32a2
History
File Mode Size
Kconfig -rw-r--r-- 65.1 KB
Makefile -rw-r--r-- 1.2 KB
calibrate.c -rw-r--r-- 8.6 KB
do_mounts.c -rw-r--r-- 15.1 KB
do_mounts.h -rw-r--r-- 1.1 KB
do_mounts_initrd.c -rw-r--r-- 3.5 KB
do_mounts_md.c -rw-r--r-- 7.9 KB
do_mounts_rd.c -rw-r--r-- 8.1 KB
init_task.c -rw-r--r-- 5.2 KB
initramfs.c -rw-r--r-- 13.7 KB
main.c -rw-r--r-- 28.9 KB
noinitramfs.c -rw-r--r-- 1.5 KB
version.c -rw-r--r-- 1.2 KB

back to top