[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 2/7] vm-event: VM_EVENT_FLAG_DENY requires VM_EVENT_FLAG_VCPU_PAUSED
On 6/16/2016 7:11 PM, Tamas K Lengyel wrote: On Thu, Jun 16, 2016 at 8:07 AM, Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx> wrote:For VM_EVENT_FLAG_DENY to work, the vcpu must be paused (sync = 1) until the vm-event is handled. A vm-event response having VM_EVENT_FLAG_DENY flag set should also set the VM_EVENT_FLAG_VCPU_PAUSED flag. Enforce that in vm_event_register_write_resume().Well, the problem with this is that the user can set the VCPU_PAUSED flag any time it wants. It can happen that Xen hasn't paused the vCPU but the user still sends that flag, in which case the unpause the flag induces will not actually do anything. You should also check if the vCPU is in fact paused rather then just relying on this flag. Tamas Right, I actually meant to take a second look over that.I see a situation like that was taken into account in vm_event_vcpu_unpause (comment "prevent underflow of the vcpu pause count.") How can I check for vcpu pause here? Thanks, Corneliu. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |