[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Deferrable jobs & hypercalls


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Ying-Shiuan Pan <yingshiuan.pan@xxxxxxxxx>
  • Date: Mon, 3 Jan 2011 14:52:12 +0800
  • Delivery-date: Sun, 02 Jan 2011 22:53:34 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=tN5M2+63V2cTh0IBDY91xOTBXLmOb2yHcHl2gLsJLhBt2Kq1uTK3ReXsKHrW1QLAo3 YGnYLMD75yrjrR6H2evlGfpqtJiWxCdlRCW3haPfZ8xTlpGgW9NcnNNfNpfuKYUlRvQ3 ia7t1+EvltixKUnqOKxETXDvXoXulgY0qMhyc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi, All,

Can anyone suggest a way to perform a long-term/periodic task inside hypervisor?
We have implemented a hypercall which performs a long-term task (e.g. a few seconds).
However, we found that if this is being called, then other hypercalls in dom0 (xm dmesg) will
be blocked until our hypercall is done.

Is there any locking between each hypercall execution or any kind of restriction to
perform tasks inside hypercall routine?

In addition, instead of puting the long-term task inside hypercall, we also try to use the timer
inside xen (i.e. init_timer, set_timer) and the workqueue patch from:
http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00882.html,
but the situation remains the same to block the dom0 hypercalls.

----
Best Regards,
Ying-Shiuan Pan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.