[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 0/4] VMX: Properly handle pi descriptor and per-cpu blocking list
On Fri, 2016-06-24 at 06:33 +0000, Wu, Feng wrote: > > -----Original Message----- > > From: Dario Faggioli [mailto:dario.faggioli@xxxxxxxxxx] > > In your case, AFAICUI, it's: > > - the vCPU should block, waiting for an event > > - the event is _not_ arrived, so we indeed should block > > - we do *not* block, due to some other reason > > > > That does not look right to me... what about the fact that we > > wanted to > > actually wait for the event? :-O > I understand your point. In my understanding, currently, vcpu_block() > is > for guest's HLT operation, which means, guest has nothing to do. In > this case, even we return (not blocking), seems the function is not > broken. > So, basically, you're saying that the vcpu has nothing to do, and in fact it executed an HLT instruction, and you want to let it continue to run? :-O Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |