xen: drop hypercall function tables
v3 cover xen: drop hypercall function tables
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressed
Changes in V3:
- patches 1 and 4 removed as already applied
- comments addressed
Juergen Gross (13):
xen: move do_vcpu_op() to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't include asm/hypercall.h from C sources
xen: include compat/platform.h from hypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: drop calls_to_multicall performance counter tools/xenperf: update hypercall names
.gitignore | 1 + tools/misc/xenperf.c | 5 + xen/arch/arm/domain.c | 15 +- xen/arch/arm/hvm.c | 3 +- xen/arch/arm/physdev.c | 2 +- xen/arch/arm/platform_hypercall.c | 1 + xen/arch/arm/traps.c | 124 ++------- xen/arch/x86/compat.c | 14 +- xen/arch/x86/cpu/vpmu.c | 1 + xen/arch/x86/domain.c | 11 +- xen/arch/x86/domctl.c | 4 +- xen/arch/x86/hvm/hypercall.c | 178 ++----------- xen/arch/x86/hypercall.c | 59 ----- xen/arch/x86/mm.c | 1 - xen/arch/x86/mm/paging.c | 3 +- xen/arch/x86/platform_hypercall.c | 1 + xen/arch/x86/pv/callback.c | 20 +- xen/arch/x86/pv/emul-priv-op.c | 2 +- xen/arch/x86/pv/hypercall.c | 182 ++----------- xen/arch/x86/pv/iret.c | 5 +- xen/arch/x86/pv/misc-hypercalls.c | 14 +- xen/arch/x86/pv/shim.c | 54 ++-- xen/arch/x86/traps.c | 2 +- xen/arch/x86/x86_64/compat.c | 1 - xen/arch/x86/x86_64/compat/mm.c | 1 + xen/arch/x86/x86_64/domain.c | 16 +- xen/arch/x86/x86_64/mm.c | 2 - xen/arch/x86/x86_64/platform_hypercall.c | 3 +- xen/common/argo.c | 12 +- xen/common/compat/domain.c | 14 +- xen/common/compat/grant_table.c | 1 + xen/common/compat/multicall.c | 2 +- xen/common/domain.c | 11 +- xen/common/event_channel.c | 10 + xen/common/grant_table.c | 10 + xen/common/kexec.c | 6 +- xen/common/multicall.c | 2 +- xen/include/Makefile | 13 + xen/include/asm-arm/hypercall.h | 7 +- xen/include/asm-x86/hypercall.h | 205 ++++----------- xen/include/asm-x86/paging.h | 3 - xen/include/asm-x86/pv/shim.h | 3 + xen/include/hypercall-defs.c | 280 ++++++++++++++++++++ xen/include/xen/hypercall.h | 184 +------------ xen/include/xen/perfc_defn.h | 1 - xen/scripts/gen_hypercall.awk | 314 +++++++++++++++++++++++ 46 files changed, 874 insertions(+), 929 deletions(-) create mode 100644 xen/include/hypercall-defs.c create mode 100644 xen/scripts/gen_hypercall.awk
Signature · 1 line
2.26.2
PATCH v3 1/13 xen: move do_vcpu_op() to arch specific code
Today Arm is using another entry point for the vcpu_op hypercall as x86, as some of the common sub-ops are not supported on Arm. The Arm specific handler filetrs out the not supported sub-ops and then calls the common handler. This leads to the weird call hierarchy:
do_arm_vcpu_op()
do_vcpu_op()
arch_do_vcpu_op()Clean this up by renaming do_vcpu_op() to common_vcpu_op() and arch_do_vcpu_op() in each architecture to do_vcpu_op(). This way one of above calls can be avoided without restricting any potential future use of common sub-ops for Arm.
Additionally the single user of HYPERCALL_ARM() can be modified and HYPERCALL_ARM() can be removed.
--- xen/arch/arm/domain.c | 15 ++++++++------- xen/arch/arm/traps.c | 7 +------ xen/arch/x86/domain.c | 11 +++++++---- xen/arch/x86/x86_64/domain.c | 16 ++++++++++++---- xen/common/compat/domain.c | 14 ++++++-------- xen/common/domain.c | 11 ++++------- xen/include/asm-arm/hypercall.h | 2 -- xen/include/asm-x86/hypercall.h | 2 +- xen/include/xen/hypercall.h | 2 +- 9 files changed, 40 insertions(+), 40 deletions(-)
xen/arch/arm/domain.c +8 -7
@@ -1074,23 +1074,24 @@ void arch_dump_domain_info(struct domain *d) } -long do_arm_vcpu_op (int cmd,unsigned int vcpuid,XEN_GUEST_HANDLE_PARAM (void ) arg) +long do_vcpu_op (int cmd,unsigned int vcpuid,XEN_GUEST_HANDLE_PARAM (void ) arg) { +struct domain *d = current->domain; +struct vcpu *v; + +if ( (v =domain_vcpu (d, vcpuid)) ==NULL ) +return -ENOENT ; +switch ( cmd ) {case VCPUOP_register_vcpu_info:case VCPUOP_register_runstate_memory_area: -return do_vcpu_op (cmd, vcpuid, arg); +return common_vcpu_op (cmd, v, arg);default :return -EINVAL ; } } -long arch_do_vcpu_op (int cmd,struct vcpu *v,XEN_GUEST_HANDLE_PARAM (void ) arg) -{ -return -ENOSYS ; -} -void arch_dump_vcpu_info (struct vcpu *v) {gic_dump_info (v);
xen/arch/arm/traps.c +1 -6
@@ -1351,11 +1351,6 @@ typedef struct { .nr_args = _nr_args, \ } -#define HYPERCALL_ARM (_name, _nr_args) \ - [ __HYPERVISOR_ ## _name ] = { \ - .fn = (arm_hypercall_fn_t) &do_arm_ ## _name, \ - .nr_args = _nr_args, \ - }/* * Only use this for hypercalls which were deprecated (i.e. replaced * by something else) before Xen on ARM was created, i.e. *not* for
@@ -1386,7 +1381,7 @@ static arm_hypercall_t arm_hypercall_table[] = {#endif HYPERCALL (multicall,2 ),HYPERCALL (platform_op,1 ), -HYPERCALL_ARM (vcpu_op,3 ), +HYPERCALL (vcpu_op,3 ),HYPERCALL (vm_assist,2 ), #ifdef CONFIG_ARGO HYPERCALL(argo_op, 5),
xen/arch/x86/domain.c +7 -4
@@ -1488,11 +1488,14 @@ int arch_vcpu_reset(struct vcpu *v)return 0 ; } -long -arch_do_vcpu_op ( -int cmd,struct vcpu *v,XEN_GUEST_HANDLE_PARAM (void ) arg) +long do_vcpu_op (int cmd,unsigned int vcpuid,XEN_GUEST_HANDLE_PARAM (void ) arg) {long rc =0 ; +struct domain *d = current->domain; +struct vcpu *v; + +if ( (v =domain_vcpu (d, vcpuid)) ==NULL ) +return -ENOENT ;switch ( cmd ) {
@@ -1544,7 +1547,7 @@ arch_do_vcpu_op( }default : - rc = -ENOSYS ; + rc =common_vcpu_op (cmd, v, arg);break ; }
xen/arch/x86/x86_64/domain.c +12 -4
@@ -13,10 +13,14 @@ CHECK_vcpu_get_physid;#undef xen_vcpu_get_physidint -arch_compat_vcpu_op ( -int cmd,struct vcpu *v,XEN_GUEST_HANDLE_PARAM (void ) arg) +compat_vcpu_op (int cmd,unsigned int vcpuid,XEN_GUEST_HANDLE_PARAM (void ) arg) { -int rc = -ENOSYS ; +int rc; +struct domain *d = current->domain; +struct vcpu *v; + +if ( (v =domain_vcpu (d, vcpuid)) ==NULL ) +return -ENOENT ;switch ( cmd ) {
@@ -55,7 +59,11 @@ arch_compat_vcpu_op( }case VCPUOP_get_physid: - rc =arch_do_vcpu_op (cmd, v, arg); + rc =do_vcpu_op (cmd, vcpuid, arg); +break ; + +default : + rc =compat_common_vcpu_op (cmd, v, arg);break ; }
xen/common/compat/domain.c +6 -8
@@ -38,14 +38,12 @@ CHECK_vcpu_hvm_context;#endif -int compat_vcpu_op (int cmd,unsigned int vcpuid,XEN_GUEST_HANDLE_PARAM (void ) arg) +int compat_common_vcpu_op (int cmd,struct vcpu *v, +XEN_GUEST_HANDLE_PARAM (void ) arg) { -struct domain *d = current->domain; -struct vcpu *v;int rc =0 ; - -if ( (v =domain_vcpu (d, vcpuid)) ==NULL ) -return -ENOENT ; +struct domain *d = current->domain; +unsigned int vcpuid = v->vcpu_id;switch ( cmd ) {
@@ -102,7 +100,7 @@ int compat_vcpu_op(int cmd, unsigned int vcpuid, XEN_GUEST_HANDLE_PARAM(void) arcase VCPUOP_stop_singleshot_timer:case VCPUOP_register_vcpu_info:case VCPUOP_send_nmi: - rc =do_vcpu_op (cmd, vcpuid, arg); + rc =common_vcpu_op (cmd, v, arg);break ;case VCPUOP_get_runstate_info:
@@ -133,7 +131,7 @@ int compat_vcpu_op(int cmd, unsigned int vcpuid, XEN_GUEST_HANDLE_PARAM(void) ar }default : - rc =arch_compat_vcpu_op (cmd, v, arg); + rc = -ENOSYS ;break ; }
xen/common/domain.c +4 -7
@@ -1558,14 +1558,11 @@ int default_initialise_vcpu(struct vcpu *v, XEN_GUEST_HANDLE_PARAM(void) arg)return rc; } -long do_vcpu_op (int cmd,unsigned int vcpuid,XEN_GUEST_HANDLE_PARAM (void ) arg) +long common_vcpu_op (int cmd,struct vcpu *v,XEN_GUEST_HANDLE_PARAM (void ) arg) { -struct domain *d = current->domain; -struct vcpu *v;long rc =0 ; - -if ( (v =domain_vcpu (d, vcpuid)) ==NULL ) -return -ENOENT ; +struct domain *d = current->domain; +unsigned int vcpuid = v->vcpu_id;switch ( cmd ) {
@@ -1737,7 +1734,7 @@ long do_vcpu_op(int cmd, unsigned int vcpuid, XEN_GUEST_HANDLE_PARAM(void) arg) }default : - rc =arch_do_vcpu_op (cmd, v, arg); + rc = -ENOSYS ;break ; }
xen/include/asm-arm/hypercall.h +0 -2
@@ -4,8 +4,6 @@#include <public/domctl.h> /* for arch_do_domctl */ int do_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg); -long do_arm_vcpu_op (int cmd,unsigned int vcpuid,XEN_GUEST_HANDLE_PARAM (void ) arg); -long subarch_do_domctl (struct xen_domctl *domctl,struct domain *d,XEN_GUEST_HANDLE_PARAM (xen_domctl_t) u_domctl);
xen/include/asm-x86/hypercall.h +1 -1
@@ -152,7 +152,7 @@ compat_physdev_op( XEN_GUEST_HANDLE_PARAM(void) arg);extern int -arch_compat_vcpu_op ( +compat_common_vcpu_op (int cmd,struct vcpu *v,XEN_GUEST_HANDLE_PARAM (void ) arg); extern int compat_mmuext_op(
xen/include/xen/hypercall.h +1 -1
@@ -110,7 +110,7 @@ do_vcpu_op(struct vcpu ;extern long -arch_do_vcpu_op (int cmd, +common_vcpu_op (int cmd,struct vcpu *v,XEN_GUEST_HANDLE_PARAM (void ) arg);
Signature · 1 line
2.26.2
Re: [PATCH v3 01/13] xen: move do_vcpu_op() to arch specific code
Hi Juergen,
Quoted 1 line · Juergen Gross
Today Arm is using another entry point for the
vcpu_ophypercall as
NIT: The 'as' doesn't sound right here. Did you mean 'compare to'?
Quoted 2 lines
x86, as some of the common sub-ops are not supported on Arm. The Arm specific handler filetrs out the not supported sub-ops and then calls
Typo: s/filetrs/filters/
Quoted 11 lines
the common handler. This leads to the weird call hierarchy:
do_arm_vcpu_op() do_vcpu_op() arch_do_vcpu_op()Clean this up by renaming
do_vcpu_op()tocommon_vcpu_op()andarch_do_vcpu_op()in each architecture todo_vcpu_op(). This way one of above calls can be avoided without restricting any potential future use of common sub-ops for Arm.
Quoted 4 lines
Additionally the single user of
HYPERCALL_ARM()can be modified andHYPERCALL_ARM()can be removed.Signed-off-by Juergen Gross <[email protected]>
Cheers,
Signature · 1 line
Julien Grall
Re: [PATCH v3 01/13] xen: move do_vcpu_op() to arch specific code
Quoted 6 lines · Julien Grall
Hi Juergen,
Quoted 1 line · Juergen Gross
Today Arm is using another entry point for the
vcpu_ophypercall asNIT: The 'as' doesn't sound right here. Did you mean 'compare to'?
Hmm, it should even be "different" instead of "another". And then it should be:
The entry point used for the vcpu_op hypercall on Arm is different from the one on x86 today.
Quoted 5 lines
Quoted 3 lines
x86, as some of the common sub-ops are not supported on Arm. The Arm specific handler filetrs out the not supported sub-ops and then calls
Typo: s/filetrs/filters/
Yes.
Quoted 12 lines
Quoted 12 lines
the common handler. This leads to the weird call hierarchy:
do_arm_vcpu_op()
do_vcpu_op()
arch_do_vcpu_op()Clean this up by renaming
do_vcpu_op()tocommon_vcpu_op()andarch_do_vcpu_op()in each architecture todo_vcpu_op(). This way one of above calls can be avoided without restricting any potential future use of common sub-ops for Arm.
Quoted 6 lines
Quoted 4 lines
Additionally the single user of
HYPERCALL_ARM()can be modified andHYPERCALL_ARM()can be removed.Signed-off-by Juergen Gross <[email protected]>Reviewed-by Julien Grall <[email protected]>
Thanks,
Juergen
Re: [PATCH v3 01/13] xen: move do_vcpu_op() to arch specific code
Hi Juergen,
Quoted 6 lines · Juergen Gross
Quoted 5 lines · Julien Grall
Hi Juergen,
Quoted 1 line · Juergen Gross
Today Arm is using another entry point for the
vcpu_ophypercall as
Quoted 7 lines
Quoted 1 line
NIT: The 'as' doesn't sound right here. Did you mean 'compare to'?
Hmm, it should even be "different" instead of "another". And then it should be:
The entry point used for the
vcpu_ophypercall on Arm is different from the one on x86 today.
LGTM.
Cheers,
Signature · 1 line
Julien Grall
PATCH v3 2/13 xen: harmonize return types of hypercall handlers
In reply to Juergen GrossToday most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Get rid of the exceptions by letting compat handlers always return int and others always return long.
For the compat hvm case use eax instead of rax for the stored result as it should have been from the beginning.
Additionally move some prototypes to include/asm-x86/hypercall.h as they are x86 specific. Move the do_physdev_op() prototype from both architecture dependant headers to the common one. Move the compat_platform_op() prototype to the common header.
Switch some non style compliant types (u32, s32, s64) to style compliant ones.
Rename paging_domctl_continuation() to do_paging_domctl_cont() and add a matching define for the associated hypercall.
Make do_callback_op() and compat_callback_op() more similar by adding the const attribute to compat_callback_op()'s 2nd parameter.
Change the type of the cmd parameter for [do|compat]_kexec_op() to unsigned int, as this is more appropriate for the compat case.
---
V2:
- rework platform_op compat handling (Jan Beulich) V3:
- remove include of types.h (Jan Beulich)
--- xen/arch/arm/physdev.c | 2 +- xen/arch/x86/domctl.c | 4 +-- xen/arch/x86/hvm/hypercall.c | 8 ++--- xen/arch/x86/hypercall.c | 2 +- xen/arch/x86/mm/paging.c | 3 +- xen/arch/x86/pv/callback.c | 20 +++++------ xen/arch/x86/pv/emul-priv-op.c | 2 +- xen/arch/x86/pv/hypercall.c | 5 +-- xen/arch/x86/pv/iret.c | 4 +-- xen/arch/x86/pv/misc-hypercalls.c | 14 +++++--- xen/arch/x86/x86_64/platform_hypercall.c | 2 +- xen/common/argo.c | 12 +++---- xen/common/kexec.c | 6 ++-- xen/include/asm-arm/hypercall.h | 1 - xen/include/asm-x86/hypercall.h | 43 +++++++++++------------- xen/include/asm-x86/paging.h | 3 -- xen/include/xen/hypercall.h | 26 +++++++------- 17 files changed, 74 insertions(+), 83 deletions(-)
xen/arch/arm/physdev.c +1 -1
@@ -11,7 +11,7 @@#include <xen/hypercall.h> -int do_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg) +long do_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg) {#ifdef CONFIG_HAS_PCI return pci_physdev_op (cmd, arg);
xen/arch/x86/domctl.c +2 -2
@@ -221,8 +221,8 @@ long arch_do_domctl(case XEN_DOMCTL_shadow_op: ret =paging_domctl (d, &domctl->u.shadow_op, u_domctl,0 );if ( ret == -ERESTART ) -return hypercall_create_continuation (__HYPERVISOR_arch_1, -"h" , u_domctl); +return hypercall_create_continuation ( + __HYPERVISOR_paging_domctl_cont,"h" , u_domctl); copyback = true;break ;
xen/arch/x86/hvm/hypercall.c +2 -6
@@ -120,8 +120,6 @@ static long hvm_physdev_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg) [ __HYPERVISOR_ ## x ] = { (hypercall_fn_t *) do_ ## x, \ (hypercall_fn_t *) compat_ ## x } -#define do_arch_1 paging_domctl_continuation -static const struct {hypercall_fn_t *native, *compat; } hvm_hypercall_table[] = {
@@ -154,11 +152,9 @@ static const struct {#ifdef CONFIG_HYPFS HYPERCALL (hypfs_op), #endif -HYPERCALL (arch_1) +HYPERCALL (paging_domctl_cont) }; -#undef do_arch_1 -#undef HYPERCALL#undef HVM_CALL#undef COMPAT_CALL
@@ -296,7 +292,7 @@ int hvm_hypercall(struct cpu_user_regs *regs)#endif curr->hcall_compat = true; - regs->rax = hvm_hypercall_table[eax].compat (ebx, ecx, edx, esi, edi); + regs->eax = hvm_hypercall_table[eax].compat (ebx, ecx, edx, esi, edi); curr->hcall_compat = false;#ifndef NDEBUG
xen/arch/x86/hypercall.c +1 -1
@@ -75,7 +75,7 @@ const hypercall_args_t hypercall_args_table[NR_hypercalls] =ARGS (dm_op,3 ),ARGS (hypfs_op,5 ),ARGS (mca,1 ), - ARGS(arch_1, 1), + ARGS(paging_domctl_cont, 1), };#undef COMP
xen/arch/x86/mm/paging.c +2 -1
@@ -21,6 +21,7 @@#include <xen/init.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <asm/paging.h> #include <asm/shadow.h> #include <asm/p2m.h>
@@ -756,7 +757,7 @@ int paging_domctl(struct domain *d, struct xen_domctl_shadow_op *sc,return shadow_domctl (d, sc, u_domctl); } -long paging_domctl_continuation (XEN_GUEST_HANDLE_PARAM (xen_domctl_t) u_domctl) +long do_paging_domctl_cont (XEN_GUEST_HANDLE_PARAM (xen_domctl_t) u_domctl) {struct xen_domctl op;struct domain *d;
xen/arch/x86/pv/callback.c +10 -10
@@ -207,9 +207,9 @@ long do_set_callbacks(unsigned long event_address,#include <compat/callback.h> #include <compat/nmi.h> -static long compat_register_guest_callback (struct compat_callback_register *reg) +static int compat_register_guest_callback (struct compat_callback_register *reg) { -long ret =0 ; +int ret =0 ;struct vcpu *curr = current;fixup_guest_code_selector (curr->domain, reg->address.cs);
@@ -256,10 +256,10 @@ static long compat_register_guest_callback(struct compat_callback_register *reg)return ret; } -static long compat_unregister_guest_callback ( +static int compat_unregister_guest_callback (struct compat_callback_unregister *unreg) { -long ret; +int ret;switch ( unreg->type ) {
@@ -283,9 +283,9 @@ static long compat_unregister_guest_callback(return ret; } -long compat_callback_op (int cmd,XEN_GUEST_HANDLE (void ) arg) +int compat_callback_op (int cmd,XEN_GUEST_HANDLE (const_void) arg) { -long ret; +int ret;switch ( cmd ) {
@@ -321,10 +321,10 @@ long compat_callback_op(int cmd, XEN_GUEST_HANDLE(void) arg)return ret; } -long compat_set_callbacks (unsigned long event_selector, -unsigned long event_address, -unsigned long failsafe_selector, -unsigned long failsafe_address) +int compat_set_callbacks (unsigned long event_selector, +unsigned long event_address, +unsigned long failsafe_selector, +unsigned long failsafe_address) {struct compat_callback_register event = { .type = CALLBACKTYPE_event,
xen/arch/x86/pv/emul-priv-op.c +1 -1
@@ -22,12 +22,12 @@#include <xen/domain_page.h> #include <xen/event.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/iocap.h> #include <asm/amd.h> #include <asm/debugreg.h> #include <asm/hpet.h> -#include <asm/hypercall.h> #include <asm/mc146818rtc.h> #include <asm/pv/domain.h> #include <asm/pv/trace.h>
xen/arch/x86/pv/hypercall.c +1 -4
@@ -40,8 +40,6 @@#define COMPAT_CALL (x) HYPERCALL(x)#endif -#define do_arch_1 paging_domctl_continuation -const pv_hypercall_table_t pv_hypercall_table[] = {COMPAT_CALL (set_trap_table),HYPERCALL (mmu_update),
@@ -102,11 +100,10 @@ const pv_hypercall_table_t pv_hypercall_table[] = {#endif HYPERCALL(mca), #ifndef CONFIG_PV_SHIM_EXCLUSIVE - HYPERCALL(arch_1), + HYPERCALL(paging_domctl_cont), #endif }; -#undef do_arch_1#undef COMPAT_CALL#undef HYPERCALL
xen/arch/x86/pv/iret.c +2 -2
@@ -48,7 +48,7 @@ static void async_exception_cleanup(struct vcpu *curr) curr->arch.async_exception_state (trap).old_mask; } -unsigned long do_iret (void ) +long do_iret (void ) {struct cpu_user_regs *regs =guest_cpu_user_regs ();struct iret_context iret_saved;
@@ -105,7 +105,7 @@ unsigned long do_iret(void) }#ifdef CONFIG_PV32 -unsigned int compat_iret (void ) +int compat_iret (void ) {struct cpu_user_regs *regs =guest_cpu_user_regs ();struct vcpu *v = current;
xen/arch/x86/pv/misc-hypercalls.c +9 -5
@@ -28,12 +28,16 @@ long do_set_debugreg(int reg, unsigned long value)return set_debugreg (current, reg, value); } -unsigned long do_get_debugreg (int reg) +long do_get_debugreg (int reg) { -unsigned long val; -int res =x86emul_read_dr (reg, &val,NULL ); - -return res ==X86EMUL_OKAY ? val : -ENODEV ; +/* Avoid implementation defined behavior casting unsigned long to long. */ +union { +unsigned long val; +long ret; + } u; +int res =x86emul_read_dr (reg, &u.val,NULL ); + +return res ==X86EMUL_OKAY ? u.ret : -ENODEV ; }long do_fpu_taskswitch (int set)
xen/arch/x86/x86_64/platform_hypercall.c +1 -1
@@ -4,10 +4,10 @@EMIT_FILE ; +#include <xen/hypercall.h> #include <xen/lib.h> #include <compat/platform.h> -DEFINE_XEN_GUEST_HANDLE (compat_platform_op_t);#define xen_platform_op compat_platform_op#define xen_platform_op_t compat_platform_op_t#define do_platform_op (x) compat_platform_op(_##x)
xen/common/argo.c +6 -6
@@ -2207,13 +2207,13 @@ do_argo_op(unsigned int cmd, XEN_GUEST_HANDLE_PARAM(void) arg1, }#ifdef CONFIG_COMPAT -long -compat_argo_op (unsigned int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg1, -XEN_GUEST_HANDLE_PARAM (void ) arg2,unsigned long arg3, -unsigned long arg4) +int compat_argo_op (unsigned int cmd, +XEN_GUEST_HANDLE_PARAM (void ) arg1, +XEN_GUEST_HANDLE_PARAM (void ) arg2, +unsigned long arg3,unsigned long arg4) {struct domain *currd = current->domain; -long rc; +int rc;xen_argo_send_addr_t send_addr;xen_argo_iov_t iovs[XEN_ARGO_MAXIOV ];compat_argo_iov_t compat_iovs[XEN_ARGO_MAXIOV ];
@@ -2267,7 +2267,7 @@ compat_argo_op(unsigned int cmd, XEN_GUEST_HANDLE_PARAM(void) arg1, rc =sendv (currd, &send_addr.src, &send_addr.dst, iovs, niov, arg4); out: -argo_dprintk ("<-compat_argo_op(%u)=%ld\n" , cmd, rc); +argo_dprintk ("<-compat_argo_op(%u)=%d\n" , cmd, rc);return rc; }
xen/common/kexec.c +3 -3
@@ -1213,7 +1213,7 @@ static int kexec_status(XEN_GUEST_HANDLE_PARAM(void) uarg)return !!test_bit (bit, &kexec_flags); } -static int do_kexec_op_internal (unsigned long op, +static int do_kexec_op_internal (unsigned int op,XEN_GUEST_HANDLE_PARAM (void ) uarg,bool_t compat) {
@@ -1265,13 +1265,13 @@ static int do_kexec_op_internal(unsigned long op,return ret; } -long do_kexec_op (unsigned long op,XEN_GUEST_HANDLE_PARAM (void ) uarg) +long do_kexec_op (unsigned int op,XEN_GUEST_HANDLE_PARAM (void ) uarg) {return do_kexec_op_internal (op, uarg,0 ); }#ifdef CONFIG_COMPAT -int compat_kexec_op (unsigned long op,XEN_GUEST_HANDLE_PARAM (void ) uarg) +int compat_kexec_op (unsigned int op,XEN_GUEST_HANDLE_PARAM (void ) uarg) {return do_kexec_op_internal (op, uarg,1 ); }
xen/include/asm-arm/hypercall.h +0 -1
@@ -2,7 +2,6 @@#define __ASM_ARM_HYPERCALL_H__#include <public/domctl.h> /* for arch_do_domctl */ -int do_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg);long subarch_do_domctl (struct xen_domctl *domctl,struct domain *d,XEN_GUEST_HANDLE_PARAM (xen_domctl_t) u_domctl);
xen/include/asm-x86/hypercall.h +20 -23
103 lines not on this page · raw message
xen/include/asm-x86/paging.h +0 -3
@@ -234,9 +234,6 @@ int paging_domctl(struct domain *d, struct xen_domctl_shadow_op *sc,XEN_GUEST_HANDLE_PARAM (xen_domctl_t) u_domctl, bool_t resuming); -/* Helper hypercall for dealing with continuations. */ -long paging_domctl_continuation (XEN_GUEST_HANDLE_PARAM (xen_domctl_t )); -/* Call when destroying a vcpu/domain */ void paging_vcpu_teardown (struct vcpu *v);int paging_teardown (struct domain *d);
xen/include/xen/hypercall.h +13 -13
@@ -114,11 +114,6 @@ common_vcpu_op(int cmd, struct vcpu *v, XEN_GUEST_HANDLE_PARAM(void) arg); -extern long -do_nmi_op ( -unsigned int cmd, -XEN_GUEST_HANDLE_PARAM (void ) arg); - extern long do_hvm_op( unsigned long op,
@@ -126,13 +121,15 @@ do_hvm_op(extern long do_kexec_op ( -unsigned long op, +unsigned int op,XEN_GUEST_HANDLE_PARAM (void ) uarg);extern long do_xsm_op (XEN_GUEST_HANDLE_PARAM (void ) u_xsm_op); +long do_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg); +#ifdef CONFIG_ARGO extern long do_argo_op( unsigned int cmd,
@@ -145,9 +142,6 @@ extern long do_argo_op(extern long do_xenoprof_op (int op,XEN_GUEST_HANDLE_PARAM (void ) arg); -extern long -do_xenpmu_op (unsigned int op,XEN_GUEST_HANDLE_PARAM (xen_pmu_params_t) arg); - extern long do_dm_op( domid_t domid,
@@ -198,21 +192,27 @@ compat_sched_op(extern int compat_set_timer_op ( -u32 lo, -s32 hi); +uint32_t lo, +int32_t hi);extern int compat_xsm_op (XEN_GUEST_HANDLE_PARAM (void ) op); -extern int compat_kexec_op (unsigned long op,XEN_GUEST_HANDLE_PARAM (void ) uarg); +extern int compat_kexec_op (unsigned int op,XEN_GUEST_HANDLE_PARAM (void ) uarg);DEFINE_XEN_GUEST_HANDLE (multicall_entry_compat_t);extern int compat_multicall (XEN_GUEST_HANDLE_PARAM (multicall_entry_compat_t) call_list,uint32_t nr_calls); +int compat_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg); + +typedef struct compat_platform_op compat_platform_op_t ; +DEFINE_XEN_GUEST_HANDLE (compat_platform_op_t); +int compat_platform_op (XEN_GUEST_HANDLE_PARAM (compat_platform_op_t) u_xenpf_op); +#ifdef CONFIG_ARGO -extern long compat_argo_op( +extern int compat_argo_op( unsigned int cmd, XEN_GUEST_HANDLE_PARAM(void) arg1, XEN_GUEST_HANDLE_PARAM(void) arg2,
Signature · 1 line
2.26.2
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value on Arm.
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Quoted 7 lines
Get rid of the exceptions by letting compat handlers always return int and others always return long.
For the compat hvm case use eax instead of rax for the stored result as it should have been from the beginning.
Quoted 7 lines
Additionally move some prototypes to
include/asm-x86/hypercall.has they are x86 specific. Move thedo_physdev_op()prototype from both architecture dependant headers to the common one. Move thecompat_platform_op()prototype to the common header.Switch some non style compliant types (u32, s32, s64) to style compliant ones.
TBH, I think this should have been split because the modifications are done on lines that are untouched.
The extra patch would have made the review easier (even if this patch is still quite small).
Quoted 4 lines
Rename
paging_domctl_continuation()todo_paging_domctl_cont()and add a matching define for the associated hypercall.
Quoted 8 lines
Make
do_callback_op()andcompat_callback_op()more similar by adding the const attribute to compat_callback_op()'s 2nd parameter.Change the type of the cmd parameter for [do|compat]_kexec_op() to unsigned int, as this is more appropriate for the compat case.
Signed-off-by Juergen Gross <[email protected]>Reviewed-by Jan Beulich <[email protected]>
Cheers,
[1] [1] https://lore.kernel.org/xen-devel/[email protected]/
Signature · 1 line
Julien Grall
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 11 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value on Arm.
This would break hypercalls like XENMEM_maximum_ram_page which are able to return larger values, right?
Quoted 1 line
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in do_trap_hypercall() instead?
The question is what to return if this is not the case. -EDOM?
Quoted 13 lines
Quoted 13 lines
Get rid of the exceptions by letting compat handlers always return int and others always return long.
For the compat hvm case use eax instead of rax for the stored result as it should have been from the beginning.
Additionally move some prototypes to
include/asm-x86/hypercall.has they are x86 specific. Move thedo_physdev_op()prototype from both architecture dependant headers to the common one. Move thecompat_platform_op()prototype to the common header.
Quoted 6 lines
Quoted 2 lines
Switch some non style compliant types (u32, s32, s64) to style compliant ones.
TBH, I think this should have been split because the modifications are done on lines that are untouched.
The extra patch would have made the review easier (even if this patch is still quite small).
I can split the patch if you want.
Juergen
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 18 lines · Juergen Gross
Quoted 7 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Quoted 6 lines
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value on Arm.
This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?
Quoted 7 lines
Quoted 2 lines
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?
I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both aarch32 and aarch64. It would make things simple.
The case of XENMEM_maximum_ram_page is interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.
So XENMEM_maximum_ram_page could be the exception and return "long" which is 4 bytes on aarch32 and 8 bytes on aarch64, and it is exactly what we need.
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 33 lines · Stefano Stabellini
Quoted 18 lines · Juergen Gross
Quoted 7 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Quoted 6 lines
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value on Arm.
This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?Quoted 7 lines
Quoted 2 lines
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both aarch32 and aarch64. It would make things simple.
Quoted 4 lines
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.
You are aware that this isn't the guest's max page, but the host's?
And all of this is about a 32-bit guest on a 64-bit host.
Juergen
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 35 lines · Juergen Gross
Quoted 34 lines · Stefano Stabellini
Quoted 19 lines · Juergen Gross
Quoted 7 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Quoted 7 lines
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value
on Arm.This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?Quoted 7 lines
Quoted 2 lines
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both aarch32 and aarch64. It would make things simple.
Quoted 8 lines
Quoted 4 lines
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
And all of this is about a 32-bit guest on a 64-bit host.
Yes, I am following, and it is always difficult to get the right information out of the ARM Reference Manual, but from my search ARMv8/aarch32 (which is 32-bit mode on 64-bit capable hardware) supports max 40 bits.
From G5.1.3 (ARM DDI 0487G.a):
---
For execution in AArch32 state, the Armv8 architecture supports:
- A VA space of up to 32 bits. The actual width is IMPLEMENTATION DEFINED .
- An IPA space of up to 40 bits. The translation tables and associated System registers define the width of the implemented address space.
---
Julien, Bertrand, am I reading this right?
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 36 lines · Stefano Stabellini
Quoted 35 lines · Juergen Gross
Quoted 34 lines · Stefano Stabellini
Quoted 19 lines · Juergen Gross
Quoted 7 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Quoted 7 lines
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value
on Arm.This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?Quoted 7 lines
Quoted 2 lines
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both aarch32 and aarch64. It would make things simple.
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM, XENMEM_maximum_ram_page is supposed to return the max memory page, which could go above the addressibility limit of the VM.
So XENMEM_maximum_ram_page should potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.
I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like XENMEM_maximum_ram_page needs to be able to return a value > 32-bit when called by a 32-bit guest.
The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1 today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.
In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of memory_op is "technically" the correct thing to do because it matches the C declaration in xen/include/xen/hypercall.h:
extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void) arg);
So... I guess the conclusion is that on ARM do_memory_op should return "long" although it is not actually enough for a correct implementation of XENMEM_maximum_ram_page for aarch32 guests ?
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 70 lines · Stefano Stabellini
Quoted 36 lines · Stefano Stabellini
Quoted 35 lines · Juergen Gross
Quoted 34 lines · Stefano Stabellini
Quoted 19 lines · Juergen Gross
Quoted 7 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Quoted 7 lines
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value
on Arm.This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?Quoted 7 lines
Quoted 2 lines
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both aarch32 and aarch64. It would make things simple.
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1 today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.
In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis "technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:
Quoted 9 lines
extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);So... I guess the conclusion is that on ARM
do_memory_opshould return "long" although it is not actually enough for a correct implementation ofXENMEM_maximum_ram_pagefor aarch32 guests ?
Hence my suggestion to check the return value of _all_ hypercalls to be proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.
Juergen
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 42 lines · Juergen Gross
Quoted 41 lines · Stefano Stabellini
Quoted 8 lines · Stefano Stabellini
Quoted 7 lines · Juergen Gross
Quoted 4 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1 today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.
In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis "technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);
Quoted 8 lines
Quoted 4 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return "long" although it is not actually enough for a correct implementation ofXENMEM_maximum_ram_pagefor aarch32 guests ?Hence my suggestion to check the return value of _all_ hypercalls to be proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while compat_memory_op() does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)
Jan
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 52 lines · Jan Beulich
Quoted 42 lines · Juergen Gross
Quoted 41 lines · Stefano Stabellini
Quoted 8 lines · Stefano Stabellini
Quoted 7 lines · Juergen Gross
Quoted 4 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1 today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.
In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis "technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 8 lines
Quoted 4 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return "long" although it is not actually enough for a correct implementation ofXENMEM_maximum_ram_pagefor aarch32 guests ?Hence my suggestion to check the return value of _all_ hypercalls to be proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.
Quoted 8 lines
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while
compat_memory_op()does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)
In fact libxenctrl tries do deal with this fact by wrapping a memory_op for a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, as xen_ulong_t is a uint64 there.
So do_memory_op should return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.
So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits. The only really clean alternative would be to have separate hypercall function classes for Arm 32- and 64-bit guests (which still could share most of the functions by letting those return "int"). This would allow to use the 64-bit variant even for 32-bit guests in multicall (fine as the return field is 64-bit wide), and a probably saturating compat version for the 32-bit guest direct hypercall.
The needed adaptions in my series would be rather limited (an additional column in the hypercall table, a split which macro to use in do_trap_hypercall() on Arm depending on the bitness of the guest, the addition of the Arm compat variant of do_memory_op()).
Thoughts?
Juergen
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Hi Juergen,
Quoted 66 lines · Juergen Gross
Quoted 52 lines · Jan Beulich
Quoted 42 lines · Juergen Gross
Quoted 41 lines · Stefano Stabellini
Quoted 8 lines · Stefano Stabellini
Quoted 7 lines · Juergen Gross
Quoted 4 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1 today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.
In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis "technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 8 lines
Quoted 4 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return "long" although it is not actually enough for a correct implementation ofXENMEM_maximum_ram_pagefor aarch32 guests ?Hence my suggestion to check the return value of _all_ hypercalls to be proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.
Quoted 8 lines
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while
compat_memory_op()does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)In fact libxenctrl tries do deal with this fact by wrapping a
memory_opfor a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, asxen_ulong_tis a uint64 there.
Quoted 6 lines
So
do_memory_opshould return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits.
It would make sense. But what would you return if the value doesn't fit?
Quoted 7 lines
The only really clean alternative
would be to have separate hypercall function classes for Arm 32- and 64-bit guests (which still could share most of the functions by letting those return "int"). This would allow to use the 64-bit variant even for 32-bit guests in multicall (fine as the return field is 64-bit wide), and a probably saturating compat version for the 32-bit guest direct hypercall.
I am not entirely sure to understand this proposal. Can you clarify it?
Quoted 5 lines
The needed adaptions in my series would be rather limited (an additional column in the hypercall table, a split which macro to use in
do_trap_hypercall()on Arm depending on the bitness of the guest, the addition of the Arm compat variant ofdo_memory_op()).
Cheers,
Signature · 1 line
Julien Grall
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 69 lines · Julien Grall
Hi Juergen,
Quoted 66 lines · Juergen Gross
Quoted 52 lines · Jan Beulich
Quoted 42 lines · Juergen Gross
Quoted 41 lines · Stefano Stabellini
Quoted 8 lines · Stefano Stabellini
Quoted 7 lines · Juergen Gross
Quoted 4 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1 today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.
In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis "technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 8 lines
Quoted 4 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return "long" although it is not actually enough for a correct implementation ofXENMEM_maximum_ram_pagefor aarch32 guests ?Hence my suggestion to check the return value of _all_ hypercalls to be proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.
Quoted 8 lines
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while
compat_memory_op()does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)In fact libxenctrl tries do deal with this fact by wrapping a
memory_opfor a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, asxen_ulong_tis a uint64 there.
Quoted 8 lines
Quoted 6 lines
So
do_memory_opshould return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits.
It would make sense. But what would you return if the value doesn't fit?
I guess some errno value would be appropriate, like -EDOM, -ERANGE or -E2BIG.
Quoted 10 lines
Quoted 8 lines
The only really clean alternative
would be to have separate hypercall function classes for Arm 32- and 64-bit guests (which still could share most of the functions by letting those return "int"). This would allow to use the 64-bit variant even for 32-bit guests in multicall (fine as the return field is 64-bit wide), and a probably saturating compat version for the 32-bit guest direct hypercall.I am not entirely sure to understand this proposal. Can you clarify it?
1. In patch 5 modify the hypercall table by adding another column, so instead of:
+table: pv32 pv64 hvm32 hvm64 arm
use:
+table: pv32 pv64 hvm32 hvm64 arm32 arm64
2. Let most of the hypercalls just return int instead of long:
+rettype: do int
3. Have an explicit 64-bit variant of memory_op (the 32-bit one is the compat variant existing already):
+rettype: do64 long
+prefix: do64 PREFIX_hvm
+memory_op(unsigned long cmd, void *arg)
4. Use the appropriate calls in each column:
+memory_op compat do64 hvm hvm compat do64
5. In the Arm hypercall trap handler do:
if ( is_32bit_domain(current->domain) )
call_handlers_arm32(...);
else
call_handlers_arm64(...);6. In the multicall handler always do:
call_handlers_arm64(...);
Juergen
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 86 lines · Juergen Gross
Quoted 85 lines · Julien Grall
Hi Juergen,
Quoted 82 lines · Juergen Gross
Quoted 64 lines · Jan Beulich
Quoted 58 lines · Juergen Gross
Quoted 50 lines · Stefano Stabellini
Quoted 10 lines · Stefano Stabellini
Quoted 9 lines · Juergen Gross
Quoted 7 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a
problem in reality because the max physical address size is only 40-bit
for aarch32 guests, so 32-bit are always enough to return the highest
page in memory for 32-bit guests.Quoted 2 lines
Quoted 2 lines
You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis
supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44)
even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a
value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1
today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis
"technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 6 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return
"long" although it is not actually enough for a correct implementation
ofXENMEM_maximum_ram_pagefor aarch32 guests ?Quoted 4 lines
Hence my suggestion to check the return value of _all_ hypercalls to be
proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.Quoted 8 lines
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while
compat_memory_op()does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)In fact libxenctrl tries do deal with this fact by wrapping a
memory_opfor a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, asxen_ulong_tis a uint64 there.So
do_memory_opshould return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits.
It would make sense. But what would you return if the value doesn't fit?
I guess some errno value would be appropriate, like
-EDOM,-ERANGEor-E2BIG.
This seems to be better than the alternative below as it is a lot simpler.
Quoted 36 lines
Quoted 9 lines
Quoted 7 lines
The only really clean alternative
would be to have separate hypercall function classes for Arm 32- and 64-bit guests (which still could share most of the functions by letting those return "int"). This would allow to use the 64-bit variant even for 32-bit guests in multicall (fine as the return field is 64-bit wide), and a probably saturating compat version for the 32-bit guest direct hypercall.I am not entirely sure to understand this proposal. Can you clarify it?
1. In patch 5 modify the hypercall table by adding another column, so instead of:
+table: pv32 pv64 hvm32 hvm64 arm
use:
+table: pv32 pv64 hvm32 hvm64 arm32 arm642. Let most of the hypercalls just return int instead of long:
+rettype: do int3. Have an explicit 64-bit variant of
memory_op(the 32-bit one is the compat variant existing already):
+rettype: do64 long
+prefix: do64PREFIX_hvm
+memory_op(unsigned long cmd, void *arg)4. Use the appropriate calls in each column:
+memory_op compat do64 hvm hvm compat do645. In the Arm hypercall trap handler do:
if ( is_32bit_domain(current->domain) ) call_handlers_arm32(...); else call_handlers_arm64(...);6. In the multicall handler always do:
call_handlers_arm64(...);
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Hi,
Quoted 90 lines · Stefano Stabellini
Quoted 89 lines · Juergen Gross
Quoted 88 lines · Julien Grall
Hi Juergen,
Quoted 84 lines · Juergen Gross
Quoted 64 lines · Jan Beulich
Quoted 58 lines · Juergen Gross
Quoted 50 lines · Stefano Stabellini
Quoted 10 lines · Stefano Stabellini
Quoted 9 lines · Juergen Gross
Quoted 7 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a
problem in reality because the max physical address size is only 40-bit
for aarch32 guests, so 32-bit are always enough to return the highest
page in memory for 32-bit guests.Quoted 2 lines
Quoted 2 lines
You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis
supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44)
even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a
value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1
today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis
"technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 6 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return
"long" although it is not actually enough for a correct implementation
ofXENMEM_maximum_ram_pagefor aarch32 guests ?Quoted 4 lines
Hence my suggestion to check the return value of _all_ hypercalls to be
proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.Quoted 8 lines
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while
compat_memory_op()does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)In fact libxenctrl tries do deal with this fact by wrapping a
memory_opfor a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, asxen_ulong_tis a uint64 there.So
do_memory_opshould return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It would make sense. But what would you return if the value doesn't fit?
I guess some errno value would be appropriate, like
-EDOM,-ERANGEor-E2BIG.This seems to be better than the alternative below as it is a lot simpler.
We would still need to special case XENMEM_maximum_reservation (or rework the implementation of the sub-op) because the value returned is an unsigned long. So technically, the unsigned value for -EDOM & co could be interpreted as the maximum host frame number.
I also would like to see the hypercall returning 'int' when they are only meant to return 32-bit value. This will make easier to spot someone that decide to return a 64-bit value.
Quoted 30 lines
Quoted 30 lines
Quoted 11 lines
Quoted 9 lines
The only really clean alternative
would be to have separate hypercall function classes for Arm 32- and 64-bit guests (which still could share most of the functions by letting those return "int"). This would allow to use the 64-bit variant even for 32-bit guests in multicall (fine as the return field is 64-bit wide), and a probably saturating compat version for the 32-bit guest direct hypercall.I am not entirely sure to understand this proposal. Can you clarify it?
1. In patch 5 modify the hypercall table by adding another column, so instead of:
+table: pv32 pv64 hvm32 hvm64 arm
use:
+table: pv32 pv64 hvm32 hvm64 arm32 arm642. Let most of the hypercalls just return int instead of long:
+rettype: do int3. Have an explicit 64-bit variant of
memory_op(the 32-bit one is the compat variant existing already):
+rettype: do64 long
+prefix: do64PREFIX_hvm
+memory_op(unsigned long cmd, void *arg)4. Use the appropriate calls in each column:
+memory_op compat do64 hvm hvm compat do64
Quoted 8 lines
Quoted 8 lines
5. In the Arm hypercall trap handler do:
if ( is_32bit_domain(current->domain) ) call_handlers_arm32(...); else call_handlers_arm64(...);6. In the multicall handler always do:
call_handlers_arm64(...);
I am probably missing something. But why do we need to have separate call handlers for arm32/arm64?
Cheers,
Signature · 1 line
Julien Grall
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 117 lines · Julien Grall
Quoted 108 lines · Stefano Stabellini
Quoted 107 lines · Juergen Gross
Quoted 106 lines · Julien Grall
Hi Juergen,
Quoted 102 lines · Juergen Gross
Quoted 78 lines · Jan Beulich
Quoted 70 lines · Juergen Gross
Quoted 62 lines · Stefano Stabellini
Quoted 13 lines · Stefano Stabellini
Quoted 12 lines · Juergen Gross
Quoted 10 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is
not a
problem in reality because the max physical address size is
only 40-bit
for aarch32 guests, so 32-bit are always enough to return the
highest
page in memory for 32-bit guests.Quoted 2 lines
Quoted 2 lines
You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max
pseudo-physical address supported by the VM,XENMEM_maximum_ram_page
is
supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44)
even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are
64-bit on a 64-bit hypervisor (which I think it would be a very rare
configuration on ARM.)Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a
value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit
value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets
r1
today. Only r0 is set, so effectively we only support 32-bit return
values on aarch32 and for aarch32 guests.In other words, today all hypercalls on ARM return 64-bit to 64-bit
guests and 32-bit to 32-bit guests. Which in the case ofmemory_op
is
"technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 6 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return
"long" although it is not actually enough for a correct implementation
ofXENMEM_maximum_ram_pagefor aarch32 guests ?Quoted 6 lines
Hence my suggestion to check the return value of _all_ hypercalls to
be
proper sign extended int values for 32-bit guests. This would fix all
potential issues without silently returning truncated values.Quoted 11 lines
Are we absolutely certain we have no other paths left where a possibly
large unsigned values might be returned? In fact whilecompat_memory_op()does the necessary saturation, I've never been fully
convinced of this being the best way of dealing with things. The range
of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)In fact libxenctrl tries do deal with this fact by wrapping a
memory_op
for a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, asxen_ulong_tis a uint64 there.So
do_memory_opshould return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
It would make sense. But what would you return if the value doesn't fit?
I guess some errno value would be appropriate, like
-EDOM,-ERANGEor-E2BIG.This seems to be better than the alternative below as it is a lot simpler.
Quoted 8 lines
We would still need to special case
XENMEM_maximum_reservation(or rework the implementation of the sub-op) because the value returned is an unsigned long. So technically, the unsigned value for-EDOM& co could be interpreted as the maximum host frame number.I also would like to see the hypercall returning 'int' when they are only meant to return 32-bit value. This will make easier to spot someone that decide to return a 64-bit value.
I am completely aligned with you on both points.
XENMEM_maximum_reservation is a bit of a distraction given that is unused (even unsupported?) on ARM. In general, to switch to "int" as return type we would have to (manually) check that all the sub-ops of a given hypercall return 32-bit values, right? Otherwise, how can we be sure that we don't start to silently truncate the top 32-bit on a sub-op on arm64?
In theory we could use -Wconversion to automatically spot any truncations but unfortunately -Wconversion breaks the build at the moment.
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
In reply to Julien GrallQuoted 95 lines · Julien Grall
Hi,
Quoted 92 lines · Stefano Stabellini
Quoted 91 lines · Juergen Gross
Quoted 89 lines · Julien Grall
Hi Juergen,
Quoted 78 lines · Juergen Gross
Quoted 64 lines · Jan Beulich
Quoted 58 lines · Juergen Gross
Quoted 50 lines · Stefano Stabellini
Quoted 10 lines · Stefano Stabellini
Quoted 9 lines · Juergen Gross
Quoted 7 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a
problem in reality because the max physical address size is only 40-bit
for aarch32 guests, so 32-bit are always enough to return the highest
page in memory for 32-bit guests.Quoted 2 lines
Quoted 2 lines
You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis
supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44)
even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a
value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1
today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis
"technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 6 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return
"long" although it is not actually enough for a correct implementation
ofXENMEM_maximum_ram_pagefor aarch32 guests ?Quoted 4 lines
Hence my suggestion to check the return value of _all_ hypercalls to be
proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.Quoted 8 lines
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while
compat_memory_op()does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)In fact libxenctrl tries do deal with this fact by wrapping a
memory_opfor a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, asxen_ulong_tis a uint64 there.Quoted 6 lines
So
do_memory_opshould return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits.
It would make sense. But what would you return if the value doesn't fit?
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
I guess some errno value would be appropriate, like
-EDOM,-ERANGEor-E2BIG.This seems to be better than the alternative below as it is a lot simpler.
We would still need to special case
XENMEM_maximum_reservation(or rework the implementation of the sub-op) because the value returned is an unsigned long. So technically, the unsigned value for-EDOM& co could be interpreted as the maximum host frame number.
I guess you meant XENMEM_maximum_ram_page.
What about setting -EDOM only if the high 32 bits are not all the same? This would mean to clamp the highest RAM page to -EDOM in case the caller is interpreting it as an unsigned value. This would still be better than silently dropping the high bits, which could lead to a rather low page number instead.
Quoted 1 line
I also would like to see the hypercall returning 'int' when they are only meant to return 32-bit value. This will make easier to spot someone that decide to return a 64-bit value.
I guess this would need to include all hypercalls handled in common code?
Quoted 34 lines
Quoted 34 lines
Quoted 34 lines
Quoted 9 lines
Quoted 7 lines
The only really clean alternative
would be to have separate hypercall function classes for Arm 32- and 64-bit guests (which still could share most of the functions by letting those return "int"). This would allow to use the 64-bit variant even for 32-bit guests in multicall (fine as the return field is 64-bit wide), and a probably saturating compat version for the 32-bit guest direct hypercall.I am not entirely sure to understand this proposal. Can you clarify it?
1. In patch 5 modify the hypercall table by adding another column, so instead of:
+table: pv32 pv64 hvm32 hvm64 arm use:
+table: pv32 pv64 hvm32 hvm64 arm32 arm642. Let most of the hypercalls just return int instead of long:
+rettype: do int3. Have an explicit 64-bit variant of
memory_op(the 32-bit one is the compat variant existing already):
+rettype: do64 long
+prefix: do64PREFIX_hvm
+memory_op(unsigned long cmd, void *arg)4. Use the appropriate calls in each column:
+memory_op compat do64 hvm hvm compat do645. In the Arm hypercall trap handler do:
if (is_32bit_domain(current->domain))
call_handlers_arm32(...);
else
call_handlers_arm64(...);
Quoted 3 lines
Quoted 2 lines
Quoted 2 lines
6. In the multicall handler always do:
call_handlers_arm64(...);I am probably missing something. But why do we need to have separate call handlers for arm32/arm64?
How else could you have different functions called for 32- and 64-bit guests (other than doing the distinction in the called functions)?
Juergen
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Hi Juergen,
Quoted 99 lines · Juergen Gross
Quoted 98 lines · Julien Grall
Hi,
Quoted 95 lines · Stefano Stabellini
Quoted 93 lines · Juergen Gross
Quoted 81 lines · Julien Grall
Hi Juergen,
Quoted 78 lines · Juergen Gross
Quoted 64 lines · Jan Beulich
Quoted 58 lines · Juergen Gross
Quoted 50 lines · Stefano Stabellini
Quoted 10 lines · Stefano Stabellini
Quoted 9 lines · Juergen Gross
Quoted 7 lines · Stefano Stabellini
The case of
XENMEM_maximum_ram_pageis interesting but it is not a
problem in reality because the max physical address size is only 40-bit
for aarch32 guests, so 32-bit are always enough to return the highest
page in memory for 32-bit guests.Quoted 2 lines
Quoted 2 lines
You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis
supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44)
even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a
value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1
today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis
"technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);Quoted 6 lines
So... I guess the conclusion is that on ARM
do_memory_opshould return
"long" although it is not actually enough for a correct implementation
ofXENMEM_maximum_ram_pagefor aarch32 guests ?Quoted 4 lines
Hence my suggestion to check the return value of _all_ hypercalls to be
proper sign extended int values for 32-bit guests. This would fix all potential issues without silently returning truncated values.Quoted 8 lines
Are we absolutely certain we have no other paths left where a possibly large unsigned values might be returned? In fact while
compat_memory_op()does the necessary saturation, I've never been fully convinced of this being the best way of dealing with things. The range of error indicators is much smaller than [-INT_MIN,-1], so almost double the range of effectively unsigned values could be passed back fine. (Obviously we can't change existing interfaces, so this mem-op will need to remain as is.)In fact libxenctrl tries do deal with this fact by wrapping a
memory_opfor a 32-bit environment into a multicall. This will work fine for a 32-bit Arm guest, asxen_ulong_tis a uint64 there.Quoted 8 lines
Quoted 6 lines
So
do_memory_opshould return long on Arm, yes. OTOH doing so will continue to be a problem in case a 32-bit guest doesn't use the multicall technique for handling possible 64-bit return values.So I continue to argue that on Arm the return value of a hypercall should be tested to fit into 32 bits.
It would make sense. But what would you return if the value doesn't fit?
I guess some errno value would be appropriate, like
-EDOM,-ERANGEor-E2BIG.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
This seems to be better than the alternative below as it is a lot simpler.
We would still need to special case
XENMEM_maximum_reservation(or rework the implementation of the sub-op) because the value returned is an unsigned long. So technically, the unsigned value for-EDOM& co could be interpreted as the maximum host frame number.I guess you meant
XENMEM_maximum_ram_page.
Hmmmm yes.
Quoted 6 lines
What about setting
-EDOMonly if the high 32 bits are not all the same? This would mean to clamp the highest RAM page to-EDOMin case the caller is interpreting it as an unsigned value. This would still be better than silently dropping the high bits, which could lead to a rather low page number instead.
This feels like quite a hack. So I would prefer the low page number. I am interested to hear about the others.
Quoted 5 lines
Quoted 2 lines
I also would like to see the hypercall returning 'int' when they are only meant to return 32-bit value. This will make easier to spot someone that decide to return a 64-bit value.
I guess this would need to include all hypercalls handled in common code?
Ideally yes.
Quoted 35 lines
Quoted 35 lines
Quoted 35 lines
Quoted 35 lines
Quoted 10 lines
Quoted 8 lines
The only really clean alternative
would be to have separate hypercall function classes for Arm 32- and 64-bit guests (which still could share most of the functions by letting those return "int"). This would allow to use the 64-bit variant even for 32-bit guests in multicall (fine as the return field is 64-bit wide), and a probably saturating compat version for the 32-bit guest direct hypercall.I am not entirely sure to understand this proposal. Can you clarify it?
1. In patch 5 modify the hypercall table by adding another column, so instead of:
+table: pv32 pv64 hvm32 hvm64 arm use:
+table: pv32 pv64 hvm32 hvm64 arm32 arm642. Let most of the hypercalls just return int instead of long:
+rettype: do int3. Have an explicit 64-bit variant of
memory_op(the 32-bit one is the compat variant existing already):
+rettype: do64 long
+prefix: do64PREFIX_hvm
+memory_op(unsigned long cmd, void *arg)4. Use the appropriate calls in each column:
+memory_op compat do64 hvm hvm compat do645. In the Arm hypercall trap handler do:
if (is_32bit_domain(current->domain))
call_handlers_arm32(...);
else
call_handlers_arm64(...);
Quoted 6 lines
Quoted 3 lines
Quoted 2 lines
Quoted 2 lines
6. In the multicall handler always do:
call_handlers_arm64(...);I am probably missing something. But why do we need to have separate call handlers for arm32/arm64?
How else could you have different functions called for 32- and 64-bit guests (other than doing the distinction in the called functions)?
At least for near future, I expect do_memory_op() to be the only one requiring special distinction. So my preference would be to handle the difference there rather than adding extra logic/indirection.
Cheers,
Signature · 1 line
Julien Grall
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
In reply to Stefano StabelliniQuoted 70 lines · Stefano Stabellini
Quoted 36 lines · Stefano Stabellini
Quoted 35 lines · Juergen Gross
Quoted 34 lines · Stefano Stabellini
Quoted 19 lines · Juergen Gross
Quoted 7 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Quoted 7 lines
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value
on Arm.This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?Quoted 7 lines
Quoted 2 lines
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both aarch32 and aarch64. It would make things simple.
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Then it looks like
XENMEM_maximum_ram_pageneeds to be able to return a value > 32-bit when called by a 32-bit guest.The hypercall ABI follows the ARM C calling convention, so a 64-bit value should be returned using r0 and r1. But looking at xen/arch/arm/traps.c:do_trap_hypercall, it doesn't seem it ever sets r1 today. Only r0 is set, so effectively we only support 32-bit return values on aarch32 and for aarch32 guests.
In other words, today all hypercalls on ARM return 64-bit to 64-bit guests and 32-bit to 32-bit guests. Which in the case of
memory_opis "technically" the correct thing to do because it matches the C declaration inxen/include/xen/hypercall.h:
Quoted 8 lines
extern long
do_memory_op(
unsigned long cmd,
XEN_GUEST_HANDLE_PARAM(void)arg);So... I guess the conclusion is that on ARM
do_memory_opshould return "long" although it is not actually enough for a correct implementation ofXENMEM_maximum_ram_pagefor aarch32 guests ?
For 32-bit guests the value needs to be saturated and allocations be restricted to the "visible" part of physical address space. Just like we do on x86. Except of course for Arm the question is in how far knowledge of the largest physical address in the system is actually relevant to guests (i.e. like for HVM on x86): This isn't transparent only for PV, or at least it better would be restricted to PV.
Jan
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
In reply to Stefano StabelliniHi Stefano,
Quoted 44 lines · Stefano Stabellini
Quoted 36 lines · Stefano Stabellini
Quoted 35 lines · Juergen Gross
Quoted 34 lines · Stefano Stabellini
Quoted 19 lines · Juergen Gross
Quoted 7 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
Quoted 7 lines
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value
on Arm.This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?Quoted 7 lines
Quoted 2 lines
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both aarch32 and aarch64. It would make things simple.
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
Quoted 7 lines
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.
I am a bit confused with what you wrote. Yes, 32-bit VM can only address 40-bit, but this is only limiting its own (guest) physical address space. Such VM would still be able to map any host physical address (assuming GFN != MFN).
Quoted 4 lines
I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Looking at the implementation, the hypercall is accessible by any domain. IOW a domU 32-bit could read a wrong value.
That said, it is not clear to me why an Arm or HVM x86 guest would want to read the value.
Cheers,
Signature · 1 line
Julien Grall
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
Quoted 62 lines · Julien Grall
Hi Stefano,
Quoted 59 lines · Stefano Stabellini
Quoted 45 lines · Stefano Stabellini
Quoted 44 lines · Juergen Gross
Quoted 43 lines · Stefano Stabellini
Quoted 29 lines · Juergen Gross
Quoted 13 lines · Julien Grall
Hi,
Quoted 5 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the
compat ones return an int. There are a few exceptions from that rule,
however.So on Arm64, I don't think you can make use of the full 64-bit because a
32-bit domain would not be able to see the top 32-bit.Quoted 6 lines
In fact, this could potentially cause us some trouble (see [1]) in Xen.
So it feels like the hypercalls should always return a 32-bit signed
value
on Arm.This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able
to return larger values, right?Quoted 3 lines
The other advantage is it would be clear that the top 32-bit are not
usuable. Stefano, what do you think?Quoted 5 lines
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?I can see where Julien is coming from: we have been trying to keep the arm32 and arm64 ABIs identical since the beginning of the project. So, like Julien, my preference would be to always return 32-bit on ARM, both
aarch32 and aarch64. It would make things simple.Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
The case of
XENMEM_maximum_ram_pageis interesting but it is not a problem in reality because the max physical address size is only 40-bit
for aarch32 guests, so 32-bit are always enough to return the highest page in memory for 32-bit guests.You are aware that this isn't the guest's max page, but the host's?
I can see now that you meant to say that, no matter what is the max pseudo-physical address supported by the VM,
XENMEM_maximum_ram_pageis supposed to return the max memory page, which could go above the addressibility limit of the VM.
Quoted 6 lines
Quoted 2 lines
So
XENMEM_maximum_ram_pageshould potentially be able to return (1<<44) even when called by an aarch32 VM, with max IPA 40-bit.I am a bit confused with what you wrote. Yes, 32-bit VM can only address 40-bit, but this is only limiting its own (guest) physical address space. Such VM would still be able to map any host physical address (assuming GFN != MFN).
I meant to say the same thing that you wrote, sorry it wasn't clear
Quoted 9 lines
Quoted 3 lines
I would imagine it could be useful if dom0 is 32-bit but domUs are 64-bit on a 64-bit hypervisor (which I think it would be a very rare configuration on ARM.)
Looking at the implementation, the hypercall is accessible by any domain. IOW a domU 32-bit could read a wrong value.
That said, it is not clear to me why an Arm or HVM x86 guest would want to read the value.
Right, indeed. AFAICT it is currently unused on ARM.
Going through the code, the only caller that could potentially use it on ARM is libxl_domain_core_dump and xc_maximum_ram_page is called on the if ( !auto_translated_physmap ) code path.
Re: [PATCH v3 02/13] xen: harmonize return types of hypercall handlers
In reply to Juergen GrossHi Juergen,
Quoted 16 lines · Juergen Gross
Quoted 11 lines · Julien Grall
Hi,
Quoted 3 lines · Juergen Gross
Today most hypercall handlers have a return type of long, while the compat ones return an int. There are a few exceptions from that rule, however.
So on Arm64, I don't think you can make use of the full 64-bit because a 32-bit domain would not be able to see the top 32-bit.
In fact, this could potentially cause us some trouble (see [1]) in Xen. So it feels like the hypercalls should always return a 32-bit signed value on Arm.
This would break hypercalls like
XENMEM_maximum_ram_pagewhich are able to return larger values, right?
Quoted 6 lines
Quoted 1 line
The other advantage is it would be clear that the top 32-bit are not usuable. Stefano, what do you think?
Wouldn't it make more sense to check the return value to be a sign extended 32-bit value for 32-bit guests in
do_trap_hypercall()instead?The question is what to return if this is not the case.
-EDOM?
It looks like there was a lot of discussion afterwards. I will read everything and answer on the last part of the thread :).
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Get rid of the exceptions by letting compat handlers always return int and others always return long.
For the compat hvm case use eax instead of rax for the stored result as it should have been from the beginning.
Additionally move some prototypes to
include/asm-x86/hypercall.has they are x86 specific. Move thedo_physdev_op()prototype from both architecture dependant headers to the common one. Move thecompat_platform_op()prototype to the common header.
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Switch some non style compliant types (u32, s32, s64) to style compliant ones.
TBH, I think this should have been split because the modifications are done on lines that are untouched.
The extra patch would have made the review easier (even if this patch is still quite small).
I can split the patch if you want.
I have already reviewed this patch. So it is not going to help me :). However, I would appreciate if in the future the coding style changes are separated at least when they are not meant to be untouched.
Cheers,
Signature · 1 line
Julien Grall
PATCH v3 3/13 xen: don't include asm/hypercall.h from C sources
In reply to Juergen GrossInstead of including asm/hypercall.h always use xen/hypercall.h. Additionally include xen/hypercall.h from all sources containing a hypercall handler.
This prepares for generating the handlers' prototypes at build time.
Add a guard in asm/hypercall.h to catch direct inclusion.
---
V2:
- remove platform_op hunk (Jan Beulich)
- remove including of xen/hypervisor.h from arch/x86/x86_64/mm.c (Jan Beulich)
- fix include order in common/compat/grant_table.c (Jan Beulich)
--- xen/arch/arm/hvm.c | 3 +-- xen/arch/arm/platform_hypercall.c | 1 + xen/arch/x86/cpu/vpmu.c | 1 + xen/arch/x86/mm.c | 1 - xen/arch/x86/platform_hypercall.c | 1 + xen/arch/x86/pv/iret.c | 1 + xen/arch/x86/traps.c | 2 +- xen/arch/x86/x86_64/compat/mm.c | 1 + xen/arch/x86/x86_64/mm.c | 2 -- xen/common/compat/grant_table.c | 1 + xen/common/compat/multicall.c | 2 +- xen/common/event_channel.c | 1 + xen/common/grant_table.c | 1 + xen/common/multicall.c | 1 + xen/include/asm-arm/hypercall.h | 4 ++++ xen/include/asm-x86/hypercall.h | 4 ++++ 16 files changed, 20 insertions(+), 7 deletions(-)
xen/arch/arm/hvm.c +1 -2
@@ -20,6 +20,7 @@#include <xen/lib.h> #include <xen/errno.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/sched.h> #include <xen/monitor.h>
@@ -29,8 +30,6 @@#include <public/hvm/params.h> #include <public/hvm/hvm_op.h> -#include <asm/hypercall.h> -static int hvm_allow_set_param (const struct domain *d,unsigned int param) { switch ( param )
xen/arch/arm/platform_hypercall.c +1 -0
@@ -9,6 +9,7 @@#include <xen/types.h> #include <xen/sched.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/spinlock.h> #include <public/platform.h> #include <xsm/xsm.h>
xen/arch/x86/cpu/vpmu.c +1 -0
@@ -22,6 +22,7 @@#include <xen/param.h> #include <xen/event.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/sched.h> #include <asm/regs.h> #include <asm/types.h>
xen/arch/x86/mm.c +0 -1
@@ -129,7 +129,6 @@#include <asm/ldt.h> #include <asm/x86_emulate.h> #include <asm/e820.h> -#include <asm/hypercall.h> #include <asm/shared.h> #include <asm/mem_sharing.h> #include <public/memory.h>
xen/arch/x86/platform_hypercall.c +1 -0
@@ -17,6 +17,7 @@#include <xen/console.h> #include <xen/iocap.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/acpi.h> #include <xen/efi.h> #include <xen/cpu.h>
xen/arch/x86/pv/iret.c +1 -0
@@ -18,6 +18,7 @@*/ #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/lib.h> #include <xen/sched.h>
xen/arch/x86/traps.c +1 -1
@@ -29,6 +29,7 @@#include <xen/lib.h> #include <xen/err.h> #include <xen/errno.h> +#include <xen/hypercall.h> #include <xen/mm.h> #include <xen/param.h> #include <xen/console.h>
@@ -70,7 +71,6 @@#include <asm/x86_emulate.h> #include <asm/traps.h> #include <asm/hvm/vpt.h> -#include <asm/hypercall.h> #include <asm/mce.h> #include <asm/apic.h> #include <asm/mc146818rtc.h>
xen/arch/x86/x86_64/compat/mm.c +1 -0
@@ -1,4 +1,5 @@#include <xen/event.h> +#include <xen/hypercall.h> #include <xen/mem_access.h> #include <xen/multicall.h> #include <compat/memory.h>
xen/arch/x86/x86_64/mm.c +0 -2
@@ -25,14 +25,12 @@ EMIT_FILE;#include <xen/numa.h> #include <xen/nodemask.h> #include <xen/guest_access.h> -#include <xen/hypercall.h> #include <xen/mem_access.h> #include <asm/current.h> #include <asm/asm_defns.h> #include <asm/page.h> #include <asm/flushtlb.h> #include <asm/fixmap.h> -#include <asm/hypercall.h> #include <asm/msr.h> #include <asm/pv/domain.h> #include <asm/setup.h>
xen/common/compat/grant_table.c +1 -0
@@ -3,6 +3,7 @@* */ +#include <xen/hypercall.h> #include <compat/grant_table.h> #define xen_grant_entry_v1 grant_entry_v1
xen/common/compat/multicall.c +1 -1
@@ -4,6 +4,7 @@EMIT_FILE ; +#include <xen/hypercall.h> #include <xen/types.h> #include <xen/multicall.h> #include <xen/trace.h>
@@ -19,7 +20,6 @@ static inline void xlat_multicall_entry(struct mc_state *mcs) mcs->compat_call.args[i] = mcs->call.args[i]; } -DEFINE_XEN_GUEST_HANDLE (multicall_entry_compat_t);#define multicall_entry compat_multicall_entry#define multicall_entry_t multicall_entry_compat_t#define do_multicall_call compat_multicall_call
xen/common/event_channel.c +1 -0
@@ -24,6 +24,7 @@#include <xen/iocap.h> #include <xen/compat.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/keyhandler.h> #include <asm/current.h>
xen/common/grant_table.c +1 -0
@@ -33,6 +33,7 @@#include <xen/trace.h> #include <xen/grant_table.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/domain_page.h> #include <xen/iommu.h> #include <xen/paging.h>
xen/common/multicall.c +1 -0
@@ -9,6 +9,7 @@#include <xen/event.h> #include <xen/multicall.h> #include <xen/guest_access.h> +#include <xen/hypercall.h> #include <xen/perfc.h> #include <xen/trace.h> #include <asm/current.h>
xen/include/asm-arm/hypercall.h +4 -0
@@ -1,3 +1,7 @@ +#ifndef __XEN_HYPERCALL_H__ +#error "asm/hypercall.h should not be included directly - include xen/hypercall.h instead" +#endif +#ifndef __ASM_ARM_HYPERCALL_H__#define __ASM_ARM_HYPERCALL_H__
xen/include/asm-x86/hypercall.h +4 -0
@@ -2,6 +2,10 @@* asm-x86/hypercall.h */ +#ifndef __XEN_HYPERCALL_H__ +#error "asm/hypercall.h should not be included directly - include xen/hypercall.h instead" +#endif +#ifndef __ASM_X86_HYPERCALL_H__#define __ASM_X86_HYPERCALL_H__
Signature · 1 line
2.26.2
PATCH v3 4/13 xen: include compat/platform.h from hypercall.h
In reply to Juergen GrossThe definition of compat_platform_op_t is in compat/platform.h already, so include that file from hypercall.h instead of repeating the typedef.
This allows to remove the related include statement from arch/x86/x86_64/platform_hypercall.c.
---
V3:
- new patch
--- xen/arch/x86/x86_64/platform_hypercall.c | 1 - xen/include/xen/hypercall.h | 4 +++- 2 files changed, 3 insertions(+), 2 deletions(-)
xen/arch/x86/x86_64/platform_hypercall.c +0 -1
@@ -6,7 +6,6 @@ EMIT_FILE;#include <xen/hypercall.h> #include <xen/lib.h> -#include <compat/platform.h> #define xen_platform_op compat_platform_op#define xen_platform_op_t compat_platform_op_t
xen/include/xen/hypercall.h +3 -1
@@ -15,6 +15,9 @@#include <public/version.h> #include <public/pmu.h> #include <public/hvm/dm_op.h> +#ifdef CONFIG_COMPAT +#include <compat/platform.h> +#endif #include <asm/hypercall.h> #include <xsm/xsm.h>
@@ -207,7 +210,6 @@ extern int compat_multicall(int compat_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg); -typedef struct compat_platform_op compat_platform_op_t ;DEFINE_XEN_GUEST_HANDLE (compat_platform_op_t);int compat_platform_op (XEN_GUEST_HANDLE_PARAM (compat_platform_op_t) u_xenpf_op);
Signature · 1 line
2.26.2
Re: [PATCH v3 04/13] xen: include compat/platform.h from hypercall.h
Quoted 8 lines · Juergen Gross
The definition of
compat_platform_op_tis incompat/platform.halready, so include that file fromhypercall.hinstead of repeating the typedef.This allows to remove the related include statement from
arch/x86/x86_64/platform_hypercall.c.Signed-off-by Juergen Gross <[email protected]>
Quoted 3 lines
---
V3:
- new patch
I was actually puzzled by the cover letter stating two already applied patches when my record said three, yet total patch count having gone down by just two. Then I came to spot this new patch ...
Jan
PATCH v3 5/13 xen: generate hypercall interface related code
In reply to Juergen GrossInstead of repeating similar data multiple times use a single source file and a generator script for producing prototypes and call sequences of the hypercalls.
As the script already knows the number of parameters used add generating a macro for populating an array with the number of parameters per hypercall.
The priorities for the specific hypercalls are based on two benchamrks performed in guests (PV and PVH):
- make -j 4 of the Xen hypervisor (resulting in cpu load with lots of processes created)
- scp of a large file to the guest (network load)
With a small additional debug patch applied the number of the different hypercalls in the guest and in dom0 (for looking at backend activity related hypercalls) were counted while the benchmark in domU was running:
PV-hypercall PV-guest build PV-guest scp dom0 build dom0 scpmmu_update 186175729 2865 20936 33725stack_switch 1273311 62381 108589 270764
multicall 2182803 50 302 524update_va_mapping 571868 10 60 80xen_version 73061 850 859 5432
grant_table_op 0 0 35557 139110 iret 75673006 484132 268157 757958 vcpu_op 453037 71199 138224 334988 set_segment_base 1650249 62387 108645 270823 mmuext_op 11225681 188 7239 3426 sched_op 280153 134645 70729 137943 event_channel_op 192327 66204 71409 214191
physdev_op 0 0 7721 4315
(the dom0 values are for the guest running the build or scp test, so dom0 acting as backend)
HVM-hypercall PVH-guest build PVH-guest scpvcpu_op 277684 2324event_channel_op 350233 57383
(the related dom0 counter values are in the same range as with the test running in the PV guest)
---
V2:
- split platform_op for doe and compat prefixes (Jan Beulich)
- add "addline:" directive
- add priorities to handlers (Jan Beulich)
V2.1:
- add missing "delete" statement in awk script
- optimize case of 2 hypercalls with same priority V2.2:
- avoid asort() function (Michal Orzel)
V3:
- drop "addline:" support, as no longer needed
- enclose call sequence macros in "({ ... })" (Jan Beulich)
- small style adjustment (Jan Beulich)
- move generating to xen/include/Makefile (Anthony PERARD)
--- .gitignore | 1 + xen/include/Makefile | 13 ++ xen/include/hypercall-defs.c | 280 ++++++++++++++++++++++++++++++ xen/scripts/gen_hypercall.awk | 314 ++++++++++++++++++++++++++++++++++ 4 files changed, 608 insertions(+) create mode 100644 xen/include/hypercall-defs.c create mode 100644 xen/scripts/gen_hypercall.awk
.gitignore +1 -0
@@ -336,6 +336,7 @@ xen/include/public/public xen/include/xen/*.new xen/include/xen/acm_policy.h xen/include/xen/compile.h +xen/include/xen/hypercall-defs.h xen/include/xen/lib/x86/cpuid-autogen.h xen/test/livepatch/config.h xen/test/livepatch/expect_config.h
xen/include/Makefile +13 -0
@@ -77,6 +77,18 @@ compat/xlat.h: $(addprefix compat/.xlat/,$(xlat-y)) config/auto.conf Makefile cat $(filter %.h,$^) >[email protected] mv -f [email protected] $@ +quiet_cmd_genhyp = GEN $@ +define cmd_genhyp + awk -f ../scripts/gen_hypercall.awk <$< >$@ +endef + +all: xen/hypercall-defs.h + +xen/hypercall-defs.h: hypercall-defs.i ../scripts/gen_hypercall.awk FORCE + $(call if_changed,genhyp) + +targets += xen/hypercall-defs.h + ifeq ($(XEN_TARGET_ARCH),$(XEN_COMPILE_ARCH)) all: headers.chk headers99.chk headers++.chk
@@ -133,4 +145,5 @@ endif clean:: rm -rf compat config generated headers*.chk + rm -f xen/hypercall-defs.h hypercall-defs.i rm -f $(BASEDIR)/include/xen/lib/x86/cpuid-autogen.h
xen/include/hypercall-defs.c new file +280 -0
280 lines not on this page · raw message
xen/scripts/gen_hypercall.awk new file +314 -0
314 lines not on this page · raw message
Signature · 1 line
2.26.2
Re: [PATCH v3 05/13] xen: generate hypercall interface related code
Quoted 37 lines · Juergen Gross
Instead of repeating similar data multiple times use a single source file and a generator script for producing prototypes and call sequences of the hypercalls.
As the script already knows the number of parameters used add generating a macro for populating an array with the number of parameters per hypercall.
The priorities for the specific hypercalls are based on two benchamrks performed in guests (PV and PVH):
- make -j 4 of the Xen hypervisor (resulting in cpu load with lots of processes created)
- scp of a large file to the guest (network load)With a small additional debug patch applied the number of the different hypercalls in the guest and in dom0 (for looking at backend activity related hypercalls) were counted while the benchmark in domU was running:
PV-hypercall PV-guest build PV-guest scp dom0 build dom0 scp
mmu_update186175729 2865 20936 33725stack_switch1273311 62381 108589 270764
multicall 2182803 50 302 524update_va_mapping571868 10 60 80xen_version73061 850 859 5432grant_table_op 0 0 35557 139110 iret 75673006 484132 268157 757958 vcpu_op 453037 71199 138224 334988 set_segment_base 1650249 62387 108645 270823 mmuext_op 11225681 188 7239 3426 sched_op 280153 134645 70729 137943 event_channel_op 192327 66204 71409 214191
physdev_op0 0 7721 4315
(the dom0 values are for the guest running the build or scp test, so dom0 acting as backend)
Quoted 7 lines
HVM-hypercall PVH-guest build PVH-guest scp
vcpu_op277684 2324event_channel_op350233 57383
(the related dom0 counter values are in the same range as with the test running in the PV guest)Signed-off-by Juergen Gross <[email protected]>
PATCH v3 6/13 xen: use generated prototypes for hypercall handlers
In reply to Juergen GrossRemove the hypercall handler's prototypes in the related header files and use the generated ones instead.
Some handlers having been static before need to be made globally visible.
--- xen/arch/x86/hvm/hypercall.c | 6 +- xen/include/asm-x86/hypercall.h | 133 ------------------------ xen/include/xen/hypercall.h | 178 +------------------------------- 3 files changed, 5 insertions(+), 312 deletions(-)
xen/arch/x86/hvm/hypercall.c +3 -3
@@ -31,7 +31,7 @@#include <public/hvm/hvm_op.h> #include <public/hvm/params.h> -static long hvm_memory_op (unsigned long cmd,XEN_GUEST_HANDLE_PARAM (void ) arg) +long hvm_memory_op (unsigned long cmd,XEN_GUEST_HANDLE_PARAM (void ) arg) {long rc;
@@ -51,7 +51,7 @@ static long hvm_memory_op(unsigned long cmd, XEN_GUEST_HANDLE_PARAM(void) arg) }#ifdef CONFIG_GRANT_TABLE -static long hvm_grant_table_op ( +long hvm_grant_table_op (unsigned int cmd,XEN_GUEST_HANDLE_PARAM (void ) uop,unsigned int count) { switch ( cmd )
@@ -77,7 +77,7 @@ static long hvm_grant_table_op( }#endif -static long hvm_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg) +long hvm_physdev_op (int cmd,XEN_GUEST_HANDLE_PARAM (void ) arg) {const struct vcpu *curr = current;const struct domain *currd = curr->domain;
xen/include/asm-x86/hypercall.h +0 -133
145 lines not on this page · raw message
xen/include/xen/hypercall.h +2 -176
206 lines not on this page · raw message
Signature · 1 line
2.26.2
PATCH v3 7/13 x86/pv-shim: don't modify hypercall table
In reply to Juergen GrossWhen running as pv-shim the hypercall is modified today in order to replace the functions for __HYPERVISOR_event_channel_op and __HYPERVISOR_grant_table_op hypercalls.
Change this to call the related functions from the normal handlers instead when running as shim. The performance implications are not really relevant, as a normal production hypervisor will not be configured to support shim mode, so the related calls will be dropped due to optimization of the compiler.
Note that for the CONFIG_PV_SHIM_EXCLUSIVE case there is a dummy wrapper do_grant_table_op() needed, as in this case grant_table.c isn't being built.
---
V2:
- add test for pv_shim to wrappers (Jan Beulich)
- add grant_table_op to hypercall table if CONFIG_PV_SHIM (Jan Beulich) V3:
- add [un]likely() to pv_shim tests (Jan Beulich)
--- xen/arch/x86/pv/hypercall.c | 2 +- xen/arch/x86/pv/shim.c | 54 +++++++++++++++++------------------ xen/common/event_channel.c | 9 ++++++ xen/common/grant_table.c | 9 ++++++ xen/include/asm-x86/pv/shim.h | 3 ++ 5 files changed, 49 insertions(+), 28 deletions(-)
xen/arch/x86/pv/hypercall.c +1 -1
@@ -62,7 +62,7 @@ const pv_hypercall_table_t pv_hypercall_table[] = {COMPAT_CALL (xen_version),HYPERCALL (console_io ),COMPAT_CALL (physdev_op_compat ), -#ifdef CONFIG_GRANT_TABLE +#if defined(CONFIG_GRANT_TABLE) || defined(CONFIG_PV_SHIM)COMPAT_CALL (grant_table_op ), #endif HYPERCALL(vm_assist),
xen/arch/x86/pv/shim.c +27 -27
90 lines not on this page · raw message
xen/common/event_channel.c +9 -0
@@ -32,6 +32,10 @@#include <public/event_channel.h> #include <xsm/xsm.h> +#ifdef CONFIG_PV_SHIM +#include <asm/guest.h> +#endif +#define ERROR_EXIT (_errno) \ do { \ gdprintk(XENLOG_WARNING, \
@@ -1190,6 +1194,11 @@ long do_event_channel_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg) {int rc; +#ifdef CONFIG_PV_SHIM +if (unlikely (pv_shim) ) +return pv_shim_event_channel_op (cmd, arg); +#endif +switch ( cmd ) {case EVTCHNOP_alloc_unbound: {
xen/common/grant_table.c +9 -0
@@ -45,6 +45,10 @@#include <asm/flushtlb.h> #include <asm/guest_atomics.h> +#ifdef CONFIG_PV_SHIM +#include <asm/guest.h> +#endif +/* Per-domain grant information. */ struct grant_table {/*
@@ -3543,6 +3547,11 @@ do_grant_table_op(long rc;unsigned int opaque_in = cmd &GNTTABOP_ARG_MASK , opaque_out =0 ; +#ifdef CONFIG_PV_SHIM +if (unlikely (pv_shim) ) +return pv_shim_grant_table_op (cmd, uop, count); +#endif +if ( (int )count <0 )return -EINVAL ;
xen/include/asm-x86/pv/shim.h +3 -0
@@ -19,6 +19,7 @@#ifndef __X86_PV_SHIM_H__#define __X86_PV_SHIM_H__ +#include <xen/hypercall.h> #include <xen/types.h> #if defined(CONFIG_PV_SHIM_EXCLUSIVE )
@@ -45,6 +46,8 @@ domid_t get_initial_domain_id(void);uint64_t pv_shim_mem (uint64_t avail);void pv_shim_fixup_e820 (struct e820map *e820);const struct platform_bad_page *pv_shim_reserved_pages (unsigned int *size); +typeof (do_event_channel_op) pv_shim_event_channel_op; +typeof (do_grant_table_op) pv_shim_grant_table_op;#else
Signature · 1 line
2.26.2
PATCH v3 8/13 xen/x86: don't use hypercall table for calling compat hypercalls
In reply to Juergen GrossToday the *_op_compat hypercalls call the modern handler functions by using the entries from the hypercall table. This is resulting in a not needed indirect function call which can be avoided by using the correct handler function directly. This is basically a revert of commit 1252e282311734 ("86/pv: Export pv_hypercall_table[] rather than working around it in several ways"), which reasoning no longer applies, as shim no longer modifies the hypercall table.
The hypercall table can now be made static as there is no external reference to it any longer.
Commit 834cb8761051f7 ("x86/PV32: fix physdev_op_compat handling") can be reverted, too, as using the direct call of the correct handler is already handled fine without that patch.
--- xen/arch/x86/compat.c | 14 ++++---------- xen/arch/x86/pv/hypercall.c | 9 ++++++++- xen/arch/x86/x86_64/compat.c | 1 - xen/include/asm-x86/hypercall.h | 8 -------- 4 files changed, 12 insertions(+), 20 deletions(-)
xen/arch/x86/compat.c +4 -10
@@ -17,14 +17,12 @@ typedef long ret_t;/* Legacy hypercall (as of 0x00030202). */ ret_t do_physdev_op_compat (XEN_GUEST_HANDLE_PARAM (physdev_op_t) uop) { -typeof (do_physdev_op) *fn = - (void *)pv_hypercall_table[__HYPERVISOR_physdev_op].native;struct physdev_op op;if (unlikely (copy_from_guest (&op, uop,1 ) !=0 ) )return -EFAULT ; -return fn (op.cmd,guest_handle_from_ptr (&uop.p->u, void)); +return do_physdev_op (op.cmd,guest_handle_from_ptr (&uop.p->u, void)); }#ifndef COMPAT
@@ -32,14 +30,11 @@ ret_t do_physdev_op_compat(XEN_GUEST_HANDLE_PARAM(physdev_op_t) uop)/* Legacy hypercall (as of 0x00030101). */ long do_sched_op_compat (int cmd,unsigned long arg) { -typeof (do_sched_op) *fn = - (void *)pv_hypercall_table[__HYPERVISOR_sched_op].native; -switch ( cmd ) {case SCHEDOP_yield:case SCHEDOP_block: -return fn (cmd,guest_handle_from_ptr (NULL , void)); +return do_sched_op (cmd,guest_handle_from_ptr (NULL , void));case SCHEDOP_shutdown: TRACE_3D(TRC_SCHED_SHUTDOWN,
@@ -57,8 +52,6 @@ long do_sched_op_compat(int cmd, unsigned long arg)/* Legacy hypercall (as of 0x00030202). */ long do_event_channel_op_compat (XEN_GUEST_HANDLE_PARAM (evtchn_op_t) uop) { -typeof (do_event_channel_op) *fn = - (void *)pv_hypercall_table[__HYPERVISOR_event_channel_op].native;struct evtchn_op op;if (unlikely (copy_from_guest (&op, uop,1 ) !=0 ) )
@@ -76,7 +69,8 @@ long do_event_channel_op_compat(XEN_GUEST_HANDLE_PARAM(evtchn_op_t) uop)case EVTCHNOP_bind_ipi:case EVTCHNOP_bind_vcpu:case EVTCHNOP_unmask: -return fn (op.cmd,guest_handle_from_ptr (&uop.p->u, void)); +return do_event_channel_op (op.cmd, +guest_handle_from_ptr (&uop.p->u, void));default :return -ENOSYS ;
xen/arch/x86/pv/hypercall.c +8 -1
@@ -27,6 +27,13 @@#include <asm/multicall.h> #include <irq_vectors.h> +typedef struct { +hypercall_fn_t *native; +#ifdef CONFIG_PV32 +hypercall_fn_t *compat; +#endif +}pv_hypercall_table_t ; +#ifdef CONFIG_PV32 #define HYPERCALL (x) \ [ __HYPERVISOR_ ## x ] = { (hypercall_fn_t *) do_ ## x, \
@@ -40,7 +47,7 @@#define COMPAT_CALL (x) HYPERCALL(x)#endif -const pv_hypercall_table_t pv_hypercall_table[] = { +static const pv_hypercall_table_t pv_hypercall_table[] = {COMPAT_CALL (set_trap_table),HYPERCALL (mmu_update),COMPAT_CALL (set_gdt),
xen/arch/x86/x86_64/compat.c +0 -1
@@ -12,7 +12,6 @@ EMIT_FILE;#define physdev_op_t physdev_op_compat_t#define do_physdev_op compat_physdev_op#define do_physdev_op_compat (x) compat_physdev_op_compat(_##x) -#define native compat#define COMPAT #define _XEN_GUEST_HANDLE (t) XEN_GUEST_HANDLE(t)
xen/include/asm-x86/hypercall.h +0 -8
@@ -21,13 +21,6 @@ typedef unsigned long hypercall_fn_t( unsigned long, unsigned long, unsigned long, unsigned long, unsigned long); -typedef struct { -hypercall_fn_t *native; -#ifdef CONFIG_PV32 -hypercall_fn_t *compat; -#endif -}pv_hypercall_table_t ; - typedef struct { uint8_t native; #ifdef CONFIG_COMPAT
@@ -38,7 +31,6 @@ typedef struct {extern const hypercall_args_t hypercall_args_table[NR_hypercalls];#ifdef CONFIG_PV -extern const pv_hypercall_table_t pv_hypercall_table[];void pv_hypercall (struct cpu_user_regs *regs);#endif
Signature · 1 line
2.26.2
PATCH v3 9/13 xen/x86: call hypercall handlers via generated macro
In reply to Juergen GrossInstead of using a function table use the generated macros for calling the appropriate hypercall handlers.
This is beneficial to performance and avoids speculation issues.
With calling the handlers using the correct number of parameters now it is possible to do the parameter register clobbering in the NDEBUG case after returning from the handler. With the additional generated data the hard coded hypercall_args_table[] can be replaced by tables using the generated number of parameters.
Note that this change modifies behavior of clobbering registers in a minor way: in case a hypercall is returning -ENOSYS (or the unsigned equivalent thereof) for any reason the parameter registers will no longer be clobbered. This should be of no real concern, as those cases ought to be extremely rare and reuse of the registers in those cases seems rather far fetched.
---
V2:
- make hypercall_args_*[] const (Jan Beulich)
- make clobber_regs*() independent from NDEBUG (Jan Beulich)
- drop "L" suffix for 32-bit register clobber value (Jan Beulich) V3:
- add array_access_nospec() (Jan Beulich)
- remove local variables in hvm_hypercall() (Andrew Cooper)
--- xen/arch/x86/hvm/hypercall.c | 166 +++------------------------- xen/arch/x86/hypercall.c | 59 ---------- xen/arch/x86/pv/hypercall.c | 184 +++----------------------------- xen/include/asm-x86/hypercall.h | 55 +++++++--- 4 files changed, 76 insertions(+), 388 deletions(-)
xen/arch/x86/hvm/hypercall.c +17 -149
@@ -108,56 +108,10 @@ long hvm_physdev_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg)return compat_physdev_op (cmd, arg); } -#define HYPERCALL (x) \ - [ __HYPERVISOR_ ## x ] = { (hypercall_fn_t *) do_ ## x, \ - (hypercall_fn_t *) do_ ## x } - -#define HVM_CALL (x) \ - [ __HYPERVISOR_ ## x ] = { (hypercall_fn_t *) hvm_ ## x, \ - (hypercall_fn_t *) hvm_ ## x } - -#define COMPAT_CALL (x) \ - [ __HYPERVISOR_ ## x ] = { (hypercall_fn_t *) do_ ## x, \ - (hypercall_fn_t *) compat_ ## x } - -static const struct { -hypercall_fn_t *native, *compat; -} hvm_hypercall_table[] = { -HVM_CALL (memory_op), -COMPAT_CALL (multicall), -#ifdef CONFIG_GRANT_TABLE -HVM_CALL (grant_table_op), -#endif -HYPERCALL (vm_assist), -COMPAT_CALL (vcpu_op), -HVM_CALL (physdev_op), -COMPAT_CALL (xen_version), -HYPERCALL (console_io), -HYPERCALL (event_channel_op), -COMPAT_CALL (sched_op), -COMPAT_CALL (set_timer_op), -COMPAT_CALL (xsm_op), -HYPERCALL (hvm_op), -HYPERCALL (sysctl), -HYPERCALL (domctl), -#ifdef CONFIG_ARGO -COMPAT_CALL (argo_op), -#endif -COMPAT_CALL (platform_op), -#ifdef CONFIG_PV -COMPAT_CALL (mmuext_op), -#endif -HYPERCALL (xenpmu_op), -COMPAT_CALL (dm_op), -#ifdef CONFIG_HYPFS -HYPERCALL (hypfs_op), +#ifndef NDEBUG +static const unsigned char hypercall_args_64[] = hypercall_args_hvm64; +static const unsigned char hypercall_args_32[] = hypercall_args_hvm32;#endif -HYPERCALL (paging_domctl_cont) -}; - -#undef HYPERCALL -#undef HVM_CALL -#undef COMPAT_CALLint hvm_hypercall (struct cpu_user_regs *regs) {
@@ -203,23 +157,6 @@ int hvm_hypercall(struct cpu_user_regs *regs)return ret; } -BUILD_BUG_ON (ARRAY_SIZE (hvm_hypercall_table) > -ARRAY_SIZE (hypercall_args_table)); - -if ( eax >=ARRAY_SIZE (hvm_hypercall_table) ) - { - regs->rax = -ENOSYS ; -return HVM_HCALL_completed; - } - - eax =array_index_nospec (eax,ARRAY_SIZE (hvm_hypercall_table)); - -if ( !hvm_hypercall_table[eax].native ) - { - regs->rax = -ENOSYS ; -return HVM_HCALL_completed; - } -/* * Caching is intended for instruction emulation only. Disable it * for any accesses by hypercall argument copy-in / copy-out.
@@ -230,85 +167,27 @@ int hvm_hypercall(struct cpu_user_regs *regs)if ( mode ==8 ) { -unsigned long rdi = regs->rdi; -unsigned long rsi = regs->rsi; -unsigned long rdx = regs->rdx; -unsigned long r10 = regs->r10; -unsigned long r8 = regs->r8; -HVM_DBG_LOG (DBG_LEVEL_HCALL ,"hcall%lu(%lx, %lx, %lx, %lx, %lx)" , - eax, rdi, rsi, rdx, r10, r8); - -#ifndef NDEBUG -/* Deliberately corrupt parameter regs not used by this hypercall. */ -switch ( hypercall_args_table[eax].native ) - { -case 0 : rdi =0xdeadbeefdeadf00dUL ; fallthrough; -case 1 : rsi =0xdeadbeefdeadf00dUL ; fallthrough; -case 2 : rdx =0xdeadbeefdeadf00dUL ; fallthrough; -case 3 : r10 =0xdeadbeefdeadf00dUL ; fallthrough; -case 4 : r8 =0xdeadbeefdeadf00dUL ; - } -#endif + eax, regs->rdi, regs->rsi, regs->rdx, regs->r10, regs->r8); - regs->rax = hvm_hypercall_table[eax].native (rdi, rsi, rdx, r10, r8); +call_handlers_hvm64 (eax, regs->rax, regs->rdi, regs->rsi, regs->rdx, + regs->r10, regs->r8); -#ifndef NDEBUG -if ( !curr->hcall_preempted ) - { -/* Deliberately corrupt parameter regs used by this hypercall. */ -switch ( hypercall_args_table[eax].native ) - { -case 5 : regs->r8 =0xdeadbeefdeadf00dUL ; fallthrough; -case 4 : regs->r10 =0xdeadbeefdeadf00dUL ; fallthrough; -case 3 : regs->rdx =0xdeadbeefdeadf00dUL ; fallthrough; -case 2 : regs->rsi =0xdeadbeefdeadf00dUL ; fallthrough; -case 1 : regs->rdi =0xdeadbeefdeadf00dUL ; - } - } -#endif +if ( !curr->hcall_preempted && regs->rax != -ENOSYS ) +clobber_regs (regs,get_nargs (hypercall_args_64, eax)); }else { -unsigned int ebx = regs->ebx; -unsigned int ecx = regs->ecx; -unsigned int edx = regs->edx; -unsigned int esi = regs->esi; -unsigned int edi = regs->edi; -HVM_DBG_LOG (DBG_LEVEL_HCALL ,"hcall%lu(%x, %x, %x, %x, %x)" , eax, - ebx, ecx, edx, esi, edi); - -#ifndef NDEBUG -/* Deliberately corrupt parameter regs not used by this hypercall. */ -switch ( hypercall_args_table[eax].compat ) - { -case 0 : ebx =0xdeadf00d ; fallthrough; -case 1 : ecx =0xdeadf00d ; fallthrough; -case 2 : edx =0xdeadf00d ; fallthrough; -case 3 : esi =0xdeadf00d ; fallthrough; -case 4 : edi =0xdeadf00d ; - } -#endif + regs->ebx, regs->ecx, regs->edx, regs->esi, regs->edi); curr->hcall_compat = true; - regs->eax = hvm_hypercall_table[eax].compat (ebx, ecx, edx, esi, edi); +call_handlers_hvm32 (eax, regs->eax, regs->ebx, regs->ecx, regs->edx, + regs->esi, regs->edi); curr->hcall_compat = false; -#ifndef NDEBUG -if ( !curr->hcall_preempted ) - { -/* Deliberately corrupt parameter regs used by this hypercall. */ -switch ( hypercall_args_table[eax].compat ) - { -case 5 : regs->rdi =0xdeadf00d ; fallthrough; -case 4 : regs->rsi =0xdeadf00d ; fallthrough; -case 3 : regs->rdx =0xdeadf00d ; fallthrough; -case 2 : regs->rcx =0xdeadf00d ; fallthrough; -case 1 : regs->rbx =0xdeadf00d ; - } - } -#endif +if ( !curr->hcall_preempted && regs->eax != -ENOSYS ) +clobber_regs32 (regs,get_nargs (hypercall_args_32, eax)); }hvmemul_cache_restore (curr, token);
@@ -327,31 +206,20 @@ int hvm_hypercall(struct cpu_user_regs *regs)enum mc_disposition hvm_do_multicall_call (struct mc_state *state) {struct vcpu *curr = current; -hypercall_fn_t *func =NULL ;if (hvm_guest_x86_mode (curr) ==8 ) {struct multicall_entry *call = &state->call; -if ( call->op <ARRAY_SIZE (hvm_hypercall_table) ) - func =array_access_nospec (hvm_hypercall_table, call->op).native; -if ( func ) - call->result =func (call->args[0 ], call->args[1 ], call->args[2 ], - call->args[3 ], call->args[4 ]); -else - call->result = -ENOSYS ; +call_handlers_hvm64 (call->op, call->result, call->args[0 ], call->args[1 ], + call->args[2 ], call->args[3 ], call->args[4 ]); }else {struct compat_multicall_entry *call = &state->compat_call; -if ( call->op <ARRAY_SIZE (hvm_hypercall_table) ) - func =array_access_nospec (hvm_hypercall_table, call->op).compat; -if ( func ) - call->result =func (call->args[0 ], call->args[1 ], call->args[2 ], - call->args[3 ], call->args[4 ]); -else - call->result = -ENOSYS ; +call_handlers_hvm32 (call->op, call->result, call->args[0 ], call->args[1 ], + call->args[2 ], call->args[3 ], call->args[4 ]); }return !hvm_get_cpl (curr) ? mc_continue : mc_preempt;
xen/arch/x86/hypercall.c +0 -59
65 lines not on this page · raw message
xen/arch/x86/pv/hypercall.c +17 -167
241 lines not on this page · raw message
xen/include/asm-x86/hypercall.h +42 -13
65 lines not on this page · raw message
Signature · 1 line
2.26.2
PATCH v3 10/13 xen/arm: call hypercall handlers via generated macro
In reply to Juergen GrossInstead of using a function table use the generated macros for calling the appropriate hypercall handlers.
This makes the calls of the handlers type safe.
For deprecated hypercalls define stub functions.
---
V2:
- make hypercall_args[] const (Jan Beulich)
--- xen/arch/arm/traps.c | 119 ++++++++++--------------------------------- 1 file changed, 26 insertions(+), 93 deletions(-)
xen/arch/arm/traps.c +26 -93
@@ -1337,62 +1337,20 @@ static register_t do_deprecated_hypercall(void)return -ENOSYS ; } -typedef register_t (*arm_hypercall_fn_t )( -register_t ,register_t ,register_t ,register_t ,register_t ); - -typedef struct { -arm_hypercall_fn_t fn; -int nr_args; -}arm_hypercall_t ; - -#define HYPERCALL (_name, _nr_args) \ - [ __HYPERVISOR_ ## _name ] = { \ - .fn = (arm_hypercall_fn_t) &do_ ## _name, \ - .nr_args = _nr_args, \ - } +long dep_sched_op_compat (int cmd,unsigned long arg) +{ +return do_deprecated_hypercall (); +} -/* -* Only use this for hypercalls which were deprecated (i.e. replaced -* by something else) before Xen on ARM was created, i.e. *not* for -* hypercalls which are simply not yet used on ARM. -*/ -#define HYPERCALL_DEPRECATED (_name, _nr_args) \ - [ __HYPERVISOR_##_name ] = { \ - .fn = (arm_hypercall_fn_t) &do_deprecated_hypercall, \ - .nr_args = _nr_args, \ - } +long dep_event_channel_op_compat (XEN_GUEST_HANDLE_PARAM (evtchn_op_t) uop) +{ +return do_deprecated_hypercall (); +} -static arm_hypercall_t arm_hypercall_table[] = { -HYPERCALL (memory_op,2 ), -HYPERCALL (domctl,1 ), -HYPERCALL (sched_op,2 ), -HYPERCALL_DEPRECATED (sched_op_compat,2 ), -HYPERCALL (console_io,3 ), -HYPERCALL (xen_version,2 ), -HYPERCALL (xsm_op,1 ), -HYPERCALL (event_channel_op,2 ), -HYPERCALL_DEPRECATED (event_channel_op_compat,1 ), -HYPERCALL (physdev_op,2 ), -HYPERCALL_DEPRECATED (physdev_op_compat,1 ), -HYPERCALL (sysctl,2 ), -HYPERCALL (hvm_op,2 ), -#ifdef CONFIG_GRANT_TABLE -HYPERCALL (grant_table_op,3 ), -#endif -HYPERCALL (multicall,2 ), -HYPERCALL (platform_op,1 ), -HYPERCALL (vcpu_op,3 ), -HYPERCALL (vm_assist,2 ), -#ifdef CONFIG_ARGO -HYPERCALL (argo_op,5 ), -#endif -#ifdef CONFIG_HYPFS -HYPERCALL (hypfs_op,5 ), -#endif -#ifdef CONFIG_IOREQ_SERVER -HYPERCALL (dm_op,3 ), -#endif -}; +long dep_physdev_op_compat (XEN_GUEST_HANDLE_PARAM (physdev_op_t) uop) +{ +return do_deprecated_hypercall (); +}#ifndef NDEBUG static void do_debug_trap (struct cpu_user_regs *regs,unsigned int code)
@@ -1431,7 +1389,6 @@ static void do_debug_trap(struct cpu_user_regs *regs, unsigned int code)#define HYPERCALL_ARG3 (r) (r)->x2#define HYPERCALL_ARG4 (r) (r)->x3#define HYPERCALL_ARG5 (r) (r)->x4 -#define HYPERCALL_ARGS (r) (r)->x0, (r)->x1, (r)->x2, (r)->x3, (r)->x4#else #define HYPERCALL_RESULT_REG (r) (r)->r0#define HYPERCALL_ARG1 (r) (r)->r0
@@ -1439,52 +1396,40 @@ static void do_debug_trap(struct cpu_user_regs *regs, unsigned int code)#define HYPERCALL_ARG3 (r) (r)->r2#define HYPERCALL_ARG4 (r) (r)->r3#define HYPERCALL_ARG5 (r) (r)->r4 -#define HYPERCALL_ARGS (r) (r)->r0, (r)->r1, (r)->r2, (r)->r3, (r)->r4#endif +static const unsigned char hypercall_args[] = hypercall_args_arm; +static void do_trap_hypercall (struct cpu_user_regs *regs,register_t *nr,const union hsr hsr) { -arm_hypercall_fn_t call =NULL ;struct vcpu *curr = current; -BUILD_BUG_ON (NR_hypercalls <ARRAY_SIZE (arm_hypercall_table) ); -if ( hsr.iss !=XEN_HYPERCALL_TAG ) {gprintk (XENLOG_WARNING ,"Invalid HVC imm 0x%x\n" , hsr.iss);return inject_undef_exception (regs, hsr); } -if ( *nr >=ARRAY_SIZE (arm_hypercall_table) ) - { -perfc_incr (invalid_hypercalls); -HYPERCALL_RESULT_REG (regs) = -ENOSYS ; -return ; - } - curr->hcall_preempted = false;perfc_incra (hypercalls, *nr); - call = arm_hypercall_table[*nr].fn; -if ( call ==NULL ) - { -HYPERCALL_RESULT_REG (regs) = -ENOSYS ; -return ; - } -HYPERCALL_RESULT_REG (regs) =call (HYPERCALL_ARGS (regs)); +call_handlers_arm (*nr,HYPERCALL_RESULT_REG (regs),HYPERCALL_ARG1 (regs), +HYPERCALL_ARG2 (regs),HYPERCALL_ARG3 (regs), +HYPERCALL_ARG4 (regs),HYPERCALL_ARG5 (regs));#ifndef NDEBUG -if ( !curr->hcall_preempted ) +if ( !curr->hcall_preempted &&HYPERCALL_RESULT_REG (regs) != -ENOSYS ) {/* Deliberately corrupt parameter regs used by this hypercall. */ -switch ( arm_hypercall_table[*nr].nr_args ) { +switch ( hypercall_args[*nr] ) {case 5 :HYPERCALL_ARG5 (regs) =0xDEADBEEF ;case 4 :HYPERCALL_ARG4 (regs) =0xDEADBEEF ;case 3 :HYPERCALL_ARG3 (regs) =0xDEADBEEF ;case 2 :HYPERCALL_ARG2 (regs) =0xDEADBEEF ;case 1 :/* Don't clobber x0/r0 -- it's the return value */ +case 0 :/* -ENOSYS case */ break ;default :BUG (); }
@@ -1521,7 +1466,10 @@ static bool check_multicall_32bit_clean(struct multicall_entry *multi) {int i; -for ( i =0 ; i < arm_hypercall_table[multi->op].nr_args; i++ ) +if ( multi->op >=ARRAY_SIZE (hypercall_args) ) +return true; + +for ( i =0 ; i < hypercall_args[multi->op]; i++ ) {if (unlikely (multi->args[i] &0xffffffff00000000ULL ) ) {
@@ -1538,28 +1486,13 @@ static bool check_multicall_32bit_clean(struct multicall_entry *multi)enum mc_disposition arch_do_multicall_call (struct mc_state *state) {struct multicall_entry *multi = &state->call; -arm_hypercall_fn_t call =NULL ; - -if ( multi->op >=ARRAY_SIZE (arm_hypercall_table) ) - { - multi->result = -ENOSYS ; -return mc_continue; - } - - call = arm_hypercall_table[multi->op].fn; -if ( call ==NULL ) - { - multi->result = -ENOSYS ; -return mc_continue; - }if (is_32bit_domain (current->domain) && !check_multicall_32bit_clean (multi) )return mc_continue; - multi->result =call (multi->args[0 ], multi->args[1 ], - multi->args[2 ], multi->args[3 ], - multi->args[4 ]); +call_handlers_arm (multi->op, multi->result, multi->args[0 ], multi->args[1 ], + multi->args[2 ], multi->args[3 ], multi->args[4 ]);return likely (!psr_mode_is_user (guest_cpu_user_regs ())) ? mc_continue : mc_preempt;
Signature · 1 line
2.26.2
PATCH v3 11/13 xen/x86: add hypercall performance counters for hvm, correct pv
In reply to Juergen GrossThe HVM hypercall handler is missing incrementing the per hypercall counters. Add that.
The counters for PV are handled wrong, as they are not using perf_incra() with the number of the hypercall as index, but are incrementing the first hypercall entry (set_trap_table) for each hypercall. Fix that.
--- xen/arch/x86/hvm/hypercall.c | 2 ++ xen/arch/x86/pv/hypercall.c | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-)
xen/arch/x86/hvm/hypercall.c +2 -0
@@ -200,6 +200,8 @@ int hvm_hypercall(struct cpu_user_regs *regs)ioreq_signal_mapcache_invalidate (); } +perfc_incra (hypercalls, eax); +return curr->hcall_preempted ? HVM_HCALL_preempted : HVM_HCALL_completed; }
xen/arch/x86/pv/hypercall.c +1 -1
@@ -102,7 +102,7 @@ _pv_hypercall(struct cpu_user_regs *regs, bool compat)if ( curr->hcall_preempted ) regs->rip -=2 ; -perfc_incr (hypercalls); +perfc_incra (hypercalls, eax); }enum mc_disposition pv_do_multicall_call (struct mc_state *state)
Signature · 1 line
2.26.2
PATCH v3 12/13 xen: drop calls_to_multicall performance counter
In reply to Juergen GrossThe calls_to_multicall performance counter is basically redundant to the multicall hypercall counter. The only difference is the counting of continuation calls, which isn't really that interesting.
Drop the calls_to_multicall performance counter.
---
V2:
- new patch
--- xen/common/multicall.c | 1 - xen/include/xen/perfc_defn.h | 1 - 2 files changed, 2 deletions(-)
xen/common/multicall.c +0 -1
@@ -114,7 +114,6 @@ do_multicall(if (unlikely (disp == mc_preempt) && i < nr_calls ) goto preempted; -perfc_incr (calls_to_multicall);perfc_add (calls_from_multicall, i); mcs->flags =0 ;return rc;
xen/include/xen/perfc_defn.h +0 -1
@@ -6,7 +6,6 @@ PERFCOUNTER_ARRAY(hypercalls, "hypercalls", NR_hypercalls) -PERFCOUNTER(calls_to_multicall, "calls to multicall") PERFCOUNTER(calls_from_multicall, "calls from multicall")PERFCOUNTER (irqs,"#interrupts" )
Signature · 1 line
2.26.2
PATCH v3 13/13 tools/xenperf: update hypercall names
In reply to Juergen GrossThe hypercall names need some update.
---
V2:
- new patch
--- tools/misc/xenperf.c | 5 +++++ 1 file changed, 5 insertions(+)
tools/misc/xenperf.c +5 -0
@@ -57,6 +57,11 @@ const char *hypercall_name_table[64] =X (sysctl),X (domctl),X (kexec_op), +X (tmem_op), +X (argo_op), +X (xenpmu_op), +X (dm_op), +X (hypfs_op),X (arch_0),X (arch_1), X(arch_2),
Signature · 1 line
2.26.2
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressed
Quoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall names
It's not easy to tell which, if any, of the later patches are fully independent of earlier ones and could go in ahead of those awaiting further acks. Do you have any suggestion there, or should we wait until things can be applied in order?
Jan
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall names
Quoted 4 lines
It's not easy to tell which, if any, of the later patches are fully independent of earlier ones and could go in ahead of those awaiting further acks. Do you have any suggestion there, or should we wait until things can be applied in order?
I think all but the last patch should be applied in order. The last one obviously can be applied at any time.
Juergen
Quoted 44 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 41 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedJuergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall names
Quoted 7 lines
Quoted 4 lines
It's not easy to tell which, if any, of the later patches are fully independent of earlier ones and could go in ahead of those awaiting further acks. Do you have any suggestion there, or should we wait until things can be applied in order?
I think all but the last patch should be applied in order. The last one obviously can be applied at any time.
Hmm, I think 11 and 12 are fine to go ahead as well; I actually need them for some immediate purpose and hence I did pull them (but nothing else) into my local tree, without observing issues.
Jan
Quoted 50 lines · Jan Beulich
Quoted 49 lines · Juergen Gross
Quoted 47 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesIt's not easy to tell which, if any, of the later patches are fully independent of earlier ones and could go in ahead of those awaiting further acks. Do you have any suggestion there, or should we wait until things can be applied in order?
Quoted 6 lines
Quoted 2 lines
I think all but the last patch should be applied in order. The last one obviously can be applied at any time.
Hmm, I think 11 and 12 are fine to go ahead as well; I actually need them for some immediate purpose and hence I did pull them (but nothing else) into my local tree, without observing issues.
Yeah, those should be okay to take.
Juergen
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressed
Quoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall names
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Jan
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall names
Quoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Yes, I was planning to spin that up soon.
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
Juergen
Quoted 48 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesQuoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Quoted 5 lines
Yes, I was planning to spin that up soon.
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
Could you remind me of the (sub)thread this was in, to read through the justification again? Without recalling any details I guess I'd prefer to stick to long for non-compat flavors.
Jan
Quoted 51 lines · Jan Beulich
Quoted 50 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesQuoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Yes, I was planning to spin that up soon.
Quoted 7 lines
Quoted 3 lines
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
Could you remind me of the (sub)thread this was in, to read through the justification again? Without recalling any details I guess I'd prefer to stick to long for non-compat flavors.
This discussion started with:
https://lists.xen.org/archives/html/xen-devel/2021-12/threads.html#01293
Juergen
Quoted 48 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesQuoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Quoted 5 lines
Yes, I was planning to spin that up soon.
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
After walking through the earlier discussion (Jürgen - thanks for the link) I'm inclined to say that if Arm wants their return values limited to 32 bits (with exceptions where needed), so be it. But on x86 I'd rather not see us change this aspect. Of course I'd much prefer if architectures didn't diverge in this regard, yet then again Arm has already diverged in avoiding the compat layer (in this case I view the divergence as helpful, though, as it avoids unnecessary headache).
Jan
Quoted 55 lines · Jan Beulich
Quoted 48 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesQuoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Quoted 5 lines
Yes, I was planning to spin that up soon.
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
Quoted 7 lines
After walking through the earlier discussion (Jürgen - thanks for the link) I'm inclined to say that if Arm wants their return values limited to 32 bits (with exceptions where needed), so be it. But on x86 I'd rather not see us change this aspect. Of course I'd much prefer if architectures didn't diverge in this regard, yet then again Arm has already diverged in avoiding the compat layer (in this case I view the divergence as helpful, though, as it avoids unnecessary headache).
How to handle this in common code then? Have a hypercall_ret_t type (exact naming TBD) which is defined as long on x86 and int on Arm? Or use long in the handlers and check the value on Arm side to be a valid 32-bit signed int (this would be cumbersome for the exceptions, though)?
Juergen
Quoted 64 lines · Juergen Gross
Quoted 55 lines · Jan Beulich
Quoted 48 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesQuoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Quoted 5 lines
Yes, I was planning to spin that up soon.
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
Quoted 7 lines
After walking through the earlier discussion (Jürgen - thanks for the link) I'm inclined to say that if Arm wants their return values limited to 32 bits (with exceptions where needed), so be it. But on x86 I'd rather not see us change this aspect. Of course I'd much prefer if architectures didn't diverge in this regard, yet then again Arm has already diverged in avoiding the compat layer (in this case I view the divergence as helpful, though, as it avoids unnecessary headache).
Quoted 5 lines
How to handle this in common code then? Have a
hypercall_ret_ttype (exact naming TBD) which is defined as long on x86 and int on Arm? Or use long in the handlers and check the value on Arm side to be a valid 32-bit signed int (this would be cumbersome for the exceptions, though)?
I was thinking along the lines of hypercall_ret_t, yes, but the compiler wouldn't be helping with spotting truncation issues (we can't reasonably enable the respective warnings, as they would trigger all over the place). If we were to go that route, we'd rely on an initial audit and subsequent patch review to spot issues. Therefore, cumbersome or not, the checking approach may be the more viable one.
Then again Julien may have a better plan in mind; I'd anyway expect him to supply details on how he thinks such a transition could be done safely, as he was the one to request limiting to 32 bits.
Jan
Quoted 78 lines · Jan Beulich
Quoted 64 lines · Juergen Gross
Quoted 55 lines · Jan Beulich
Quoted 48 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesQuoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Quoted 5 lines
Yes, I was planning to spin that up soon.
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
Quoted 7 lines
After walking through the earlier discussion (Jürgen - thanks for the link) I'm inclined to say that if Arm wants their return values limited to 32 bits (with exceptions where needed), so be it. But on x86 I'd rather not see us change this aspect. Of course I'd much prefer if architectures didn't diverge in this regard, yet then again Arm has already diverged in avoiding the compat layer (in this case I view the divergence as helpful, though, as it avoids unnecessary headache).
Quoted 5 lines
How to handle this in common code then? Have a
hypercall_ret_ttype (exact naming TBD) which is defined as long on x86 and int on Arm? Or use long in the handlers and check the value on Arm side to be a valid 32-bit signed int (this would be cumbersome for the exceptions, though)?I was thinking along the lines of
hypercall_ret_t, yes, but the compiler wouldn't be helping with spotting truncation issues (we can't reasonably enable the respective warnings, as they would trigger all over the place). If we were to go that route, we'd rely on an initial audit and subsequent patch review to spot issues. Therefore, cumbersome or not, the checking approach may be the more viable one.
Quoted 3 lines
Then again Julien may have a better plan in mind; I'd anyway expect him to supply details on how he thinks such a transition could be done safely, as he was the one to request limiting to 32 bits.
In order to have some progress I could just leave the Arm side alone in my series. It could be added later if a solution has been agreed on.
What do you think?
Juergen
Quoted 83 lines · Juergen Gross
Quoted 78 lines · Jan Beulich
Quoted 64 lines · Juergen Gross
Quoted 55 lines · Jan Beulich
Quoted 48 lines · Juergen Gross
Quoted 43 lines · Jan Beulich
Quoted 27 lines · Juergen Gross
In order to avoid indirect function calls on the hypercall path as much as possible this series is removing the hypercall function tables and is replacing the hypercall handler calls via the function array by automatically generated call macros.
Another by-product of generating the call macros is the automatic generating of the hypercall handler prototypes from the same data base which is used to generate the macros.
This has the additional advantage of using type safe calls of the handlers and to ensure related handler (e.g. PV and HVM ones) share the same prototypes.
A very brief performance test (parallel build of the Xen hypervisor in a 6 vcpu guest) showed a very slim improvement (less than 1%) of the performance with the patches applied. The test was performed using a PV and a PVH guest.
Changes in V2:
- new patches 6, 14, 15
- patch 7: support hypercall priorities for faster code
- comments addressedChanges in V3:
- patches 1 and 4 removed as already applied
- comments addressedQuoted 14 lines
Juergen Gross (13):
xen: movedo_vcpu_op()to arch specific code
xen: harmonize return types of hypercall handlers
xen: don't includeasm/hypercall.hfrom C sources
xen: includecompat/platform.hfromhypercall.h
xen: generate hypercall interface related code
xen: use generated prototypes for hypercall handlers x86/pv-shim: don't modify hypercall table
xen/x86: don't use hypercall table for calling compat hypercalls xen/x86: call hypercall handlers via generated macro xen/arm: call hypercall handlers via generated macro xen/x86: add hypercall performance counters for hvm, correct pv
xen: dropcalls_to_multicallperformance countertools/xenperf: update hypercall namesQuoted 3 lines
As it's pretty certain now that parts of this which didn't go in yet will need re-basing, I'm going to drop this from my waiting-to-be-acked folder, expecting a v4 instead.
Quoted 5 lines
Yes, I was planning to spin that up soon.
The main remaining question is whether we want to switch the return type of all hypercalls (or at least the ones common to all archs) not requiring to return 64-bit values to "int", as Julien requested.
Quoted 7 lines
After walking through the earlier discussion (Jürgen - thanks for the link) I'm inclined to say that if Arm wants their return values limited to 32 bits (with exceptions where needed), so be it. But on x86 I'd rather not see us change this aspect. Of course I'd much prefer if architectures didn't diverge in this regard, yet then again Arm has already diverged in avoiding the compat layer (in this case I view the divergence as helpful, though, as it avoids unnecessary headache).
Quoted 5 lines
How to handle this in common code then? Have a
hypercall_ret_ttype (exact naming TBD) which is defined as long on x86 and int on Arm? Or use long in the handlers and check the value on Arm side to be a valid 32-bit signed int (this would be cumbersome for the exceptions, though)?I was thinking along the lines of
hypercall_ret_t, yes, but the compiler wouldn't be helping with spotting truncation issues (we can't reasonably enable the respective warnings, as they would trigger all over the place). If we were to go that route, we'd rely on an initial audit and subsequent patch review to spot issues. Therefore, cumbersome or not, the checking approach may be the more viable one.Quoted 3 lines
Then again Julien may have a better plan in mind; I'd anyway expect him to supply details on how he thinks such a transition could be done safely, as he was the one to request limiting to 32 bits.
Quoted 5 lines
In order to have some progress I could just leave the Arm side alone in my series. It could be added later if a solution has been agreed on.
What do you think?
I see no issue with this if there's no other dependency on Arm following suit.
Jan