aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2012-02-15 12:04:44 +0100
committerJan Beulich <jbeulich@suse.com>2012-02-15 12:04:44 +0100
commit271ca5bea6ed14393b4c29c07be07409d48e04c8 (patch)
treed7fa2950e4fd18696d919d89dc0c8d48248acb23
parent1ad9275fc513aa130f88d5b803d4ea676e011d26 (diff)
downloadxen-271ca5bea6ed14393b4c29c07be07409d48e04c8.tar.gz
xen-271ca5bea6ed14393b4c29c07be07409d48e04c8.tar.bz2
xen-271ca5bea6ed14393b4c29c07be07409d48e04c8.zip
x86: don't allow Dom0 to map MSI-X table writably
With the traditional qemu tree fixed to not use PROT_WRITE anymore in the mmap() call for this region, and with the upstream qemu tree not being capable of handling passthrough, yet, there's no need to treat Dom specially here anymore. This continues to leave unaddressed the case where PV guests map the MSI-X table page(s) before setting up the first MSI-X interrupt (see the original c/s 22182:68cc3c514a0a description for options). Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org>
-rw-r--r--xen/arch/x86/mm.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/xen/arch/x86/mm.c b/xen/arch/x86/mm.c
index 120033beeb..ff2ccd95e9 100644
--- a/xen/arch/x86/mm.c
+++ b/xen/arch/x86/mm.c
@@ -869,7 +869,7 @@ get_page_from_l1e(
return -EINVAL;
}
- if ( !(l1f & _PAGE_RW) || IS_PRIV(pg_owner) ||
+ if ( !(l1f & _PAGE_RW) ||
!rangeset_contains_singleton(mmio_ro_ranges, mfn) )
return 0;
dprintk(XENLOG_G_WARNING,