Re: [PATCH v3 01/13] xen: move do_vcpu_op() to arch specific code

2021-12-15 Thread Julien Grall
Hi Juergen, On 15/12/2021 07:12, Juergen Gross wrote: On 14.12.21 18:21, Julien Grall wrote: Hi Juergen, On 08/12/2021 15:55, Juergen Gross wrote: Today Arm is using another entry point for the vcpu_op hypercall as NIT: The 'as' doesn't sound right here. Did you mean 'compare to'? Hmm, it

Re: [PATCH v3 01/13] xen: move do_vcpu_op() to arch specific code

2021-12-14 Thread Juergen Gross
On 14.12.21 18:21, Julien Grall wrote: Hi Juergen, On 08/12/2021 15:55, Juergen Gross wrote: Today Arm is using another entry point for the vcpu_op hypercall as NIT: The 'as' doesn't sound right here. Did you mean 'compare to'? Hmm, it should even be "different" instead of "another". And th

Re: [PATCH v3 01/13] xen: move do_vcpu_op() to arch specific code

2021-12-14 Thread Julien Grall
Hi Juergen, On 08/12/2021 15:55, Juergen Gross wrote: Today Arm is using another entry point for the vcpu_op hypercall as NIT: The 'as' doesn't sound right here. Did you mean 'compare to'? x86, as some of the common sub-ops are not supported on Arm. The Arm specific handler filetrs out the n

[PATCH v3 01/13] xen: move do_vcpu_op() to arch specific code

2021-12-08 Thread Juergen Gross
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_