[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH 08/34] x86: enclose hvm_op and dm_op in CONFIG_HVM in PV hypercall table
PV guest (Dom0) needs to able to use these two hypercalls in order to serve HVM guests. But if xen doesn't support HVM at all there is no point in exposing them to PV guests. Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> --- xen/arch/x86/pv/hypercall.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/xen/arch/x86/pv/hypercall.c b/xen/arch/x86/pv/hypercall.c index bbc3011..75e6cdb 100644 --- a/xen/arch/x86/pv/hypercall.c +++ b/xen/arch/x86/pv/hypercall.c @@ -68,7 +68,9 @@ const hypercall_table_t pv_hypercall_table[] = { #endif HYPERCALL(event_channel_op), COMPAT_CALL(physdev_op), +#ifdef CONFIG_HVM HYPERCALL(hvm_op), +#endif HYPERCALL(sysctl), HYPERCALL(domctl), #ifdef CONFIG_KEXEC @@ -78,7 +80,9 @@ const hypercall_table_t pv_hypercall_table[] = { HYPERCALL(tmem_op), #endif HYPERCALL(xenpmu_op), +#ifdef CONFIG_HVM COMPAT_CALL(dm_op), +#endif HYPERCALL(mca), HYPERCALL(arch_1), }; -- git-series 0.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 |