>>> On 04.01.18 at 13:11, <[email protected]> wrote: > In case the vCPU has pending events to inject. This fixes a bug that > happened if the guest mapped the vcpu info area using > VCPUOP_register_vcpu_info without having setup the event channel > upcall, and then setup the upcall vector. > > In this scenario the guest would not receive any upcalls, because the > call to VCPUOP_register_vcpu_info would have marked the vCPU as having > pending events, but the vector could not be injected because it was > not yet setup. > > This has not caused issues so far because all the consumers first > setup the vector callback and then map the vcpu info page, but there's > no limitation that prevents doing it in the inverse order. > > Signed-off-by: Roger Pau Monné <[email protected]>
Despite my small concern Reviewed-by: Jan Beulich <[email protected]> Jan _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
