From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Hypercall continuation and wait_event Date: Mon, 09 Apr 2012 19:54:22 +0100 Message-ID: References: <1333993865.95130.YahooMailNeo@web124504.mail.ne1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1333993865.95130.YahooMailNeo@web124504.mail.ne1.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ruslan Nikolaev , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 09/04/2012 18:51, "Ruslan Nikolaev" wrote: > Hi > > I am curious how I can properly support hypercall continuation and wait_event. > I have a dedicated VCPU in a domain which makes a special hypercall, and the > hypercall waits for certain event to arrive. I am using queues available in > Xen, so wait_event will be invoked in the hypercall once its ready to accept > events. However, my understanding that even though I have a dedicated VCPU for > this hypercall, I still may need to support hypercall continuation properly. > (Is this the case?) So, my question is how exactly the need for hypercall No it's not the case, the old hypercall_create_continuation() mechanism does not need to be used with wait_event(). -- Keir > preemption may affect wait_event() and wait() operations, and where would I > need to do hypercall_preempt_check()? > > Thank you! > Ruslan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel