|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v3 10/24] vixen: do not permit access to physical IRQs if in Vixen mode
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Our intention is for the Vixen guest to be deprivileged so we need
to avoid permitting access to each IRQ even though it is technically
the hardware domain.
Signed-off-by: Anthony Liguori <aliguori@xxxxxxxxxx>
---
xen/arch/x86/irq.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/xen/arch/x86/irq.c b/xen/arch/x86/irq.c
index 87ef2e8..bd75108 100644
--- a/xen/arch/x86/irq.c
+++ b/xen/arch/x86/irq.c
@@ -25,6 +25,7 @@
#include <asm/flushtlb.h>
#include <asm/mach-generic/mach_apic.h>
#include <public/physdev.h>
+#include <asm/guest/vixen.h>
static int parse_irq_vector_map_param(const char *s);
@@ -190,7 +191,7 @@ int create_irq(nodeid_t node)
desc->arch.used = IRQ_UNUSED;
irq = ret;
}
- else if ( hardware_domain )
+ else if ( !is_vixen() && hardware_domain )
{
ret = irq_permit_access(hardware_domain, irq);
if ( ret )
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |