diff options
| author | Jan Beulich <jbeulich@suse.com> | 2013-04-02 10:52:26 +0200 |
|---|---|---|
| committer | Jan Beulich <jbeulich@suse.com> | 2013-04-02 10:52:26 +0200 |
| commit | 77c1e88c14bb6705f6fca091e12d2aa4d8882207 (patch) | |
| tree | b7ad2a2c567dd88a14a48c52c0c6741478d94ad9 /tools/lib/sys_string.h | |
| parent | 144d1b5c4647d829080e32d7887c33795bf4c326 (diff) | |
| download | xen-77c1e88c14bb6705f6fca091e12d2aa4d8882207.tar.gz xen-77c1e88c14bb6705f6fca091e12d2aa4d8882207.tar.bz2 xen-77c1e88c14bb6705f6fca091e12d2aa4d8882207.zip | |
AMD IOMMU: allow disabling only interrupt remapping when certain IVRS consistency checks fail
After some more thought on the XSA-36 and specifically the comments we
got regarding disabling the IOMMU in this situation altogether making
things worse instead of better, I came to the conclusion that we can
actually restrict the action in affected cases to just disabling
interrupt remapping. That doesn't make the situation worse than prior
to the XSA-36 fixes (where interrupt remapping didn't really protect
domains from one another), but allows at least DMA isolation to still
be utilized.
To do so, disabling of interrupt remapping must be explicitly requested
on the command line - respective checks will then be skipped.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
master changeset: 92b8bc03bd4b582cb524db51494d0dba7607e7ac
master date: 2013-03-25 16:55:22 +0100
Diffstat (limited to 'tools/lib/sys_string.h')
0 files changed, 0 insertions, 0 deletions