Re: [PATCH] x86/hvm: save/restore per-VCPU event channel upcall vector

2022-01-07 Thread David Vrabel
On 06/01/2022 16:48, Jan Beulich wrote: On 06.01.2022 16:54, David Vrabel wrote: The Windows XENBUS driver sets the per-VCPU LAPIC vector for event channel interrupts using the HVMOP_set_evtchn_upcall_vector hypercall (rather than using a vector-type callback in the CALLBACK_IRQ HVM parameter

Re: [PATCH] x86/hvm: save/restore per-VCPU event channel upcall vector

2022-01-06 Thread Jan Beulich
On 06.01.2022 16:54, David Vrabel wrote: > The Windows XENBUS driver sets the per-VCPU LAPIC vector for event > channel interrupts using the HVMOP_set_evtchn_upcall_vector hypercall > (rather than using a vector-type callback in the CALLBACK_IRQ HVM > parameter since the vectors might be different

[PATCH] x86/hvm: save/restore per-VCPU event channel upcall vector

2022-01-06 Thread David Vrabel
The Windows XENBUS driver sets the per-VCPU LAPIC vector for event channel interrupts using the HVMOP_set_evtchn_upcall_vector hypercall (rather than using a vector-type callback in the CALLBACK_IRQ HVM parameter since the vectors might be different for different VCPUs). This state needs to be