Re: [Xen-devel] [PATCH] x86/HVM: EOI handling function adjustments

2015-06-18 Thread Jan Beulich
>>> On 18.06.15 at 15:29, wrote: > On 18/06/15 13:51, Jan Beulich wrote: >> -void vlapic_handle_EOI_induced_exit(struct vlapic *vlapic, int vector) >> +void vlapic_handle_EOI(struct vlapic *vlapic, u8 vector) >> { >> +struct domain *d = vlapic_domain(vlapic); >> + >> if ( vlapic_test_and

Re: [Xen-devel] [PATCH] x86/HVM: EOI handling function adjustments

2015-06-18 Thread Andrew Cooper
On 18/06/15 13:51, Jan Beulich wrote: > --- a/xen/arch/x86/hvm/vlapic.c > +++ b/xen/arch/x86/hvm/vlapic.c > @@ -421,18 +421,17 @@ void vlapic_EOI_set(struct vlapic *vlapi > if ( hvm_funcs.handle_eoi ) > hvm_funcs.handle_eoi(vector); > > -if ( vlapic_test_and_clear_vector(vector,

[Xen-devel] [PATCH] x86/HVM: EOI handling function adjustments

2015-06-18 Thread Jan Beulich
The vector parameters are more usefully u8 right away. This is particularly important for the vioapic_update_EOI() invocation from vioapic_write() (which luckily is only a latent issue, as VIOAPIC_VERSION_ID is still hard coded to 0x11 right now). But it at once allows simplifying VMX's EXIT_REASON