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

[Xen-devel] Avoiding VmEntry/VmExit.


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Devdutt Patnaik" <xendevid@xxxxxxxxx>
  • Date: Mon, 29 Oct 2007 07:49:22 -0400
  • Delivery-date: Mon, 29 Oct 2007 04:50:05 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=GebLhUiwe/nBITNjy+4TyP+HdKE2dbKaHzUSH5lKGRbgHIJALXLFDyeCPvUqq045K/tGyQF/TMxalPy15KSLGTqUssbUqV+P4fEEoyKM7pJuLVf9xSFYuqpUHM+EAvxILTlkSQFBXS5mopkMohXxfMeIai1SUr0QOPSFD4N1UHY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi All,
 
I am trying to provide services to guest VMs where I wish to run guest VMs in a loop.
 
I wish to use a core to schedule a guest VM, service it eg. execute an ISR etc and then return to the context of Xen on that core, so that I can then schedule the next VM on that core.
In doing all this, the goal is to avoid the calls to VMEntry and VMExit. Is there a workaround for this to be done or will I always have to face a VMExit to return to the Xen context on that core ?
 
Looking forward to some pointers.
 
Thanks,
Devdutt.
_______________________________________________
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®.