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

[Xen-users] Question regarding Hypervisor_sched_op function


  • To: xen-users <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Mahendra Kutare <mahendra.kutare@xxxxxxxxx>
  • Date: Thu, 19 Aug 2010 20:47:13 -0400
  • Cc:
  • Delivery-date: Thu, 19 Aug 2010 17:48:50 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=gY1hjzkUb/d7Mi2gryEdFHTpWiEtcSOgenXuU3feg3ktehIuY93RX/bVg0iKJ2VXeH 0Y95u3/XuZfMCo5bJHRcoCikznvsAG3s5dFn51VS/nK4AKUuUy18U6zsM3QawsCKxC8D 3kIh2sXAFvsysUh6UOO6UuFvtrMGV8vp+b6xs=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I am trying to understand Hypervisor_sched_op function and I have few question regarding this -

1. I understand that a guest VM can use the above function with "yield", in order to relinquish CPU time to other guests with running tasks.

a) So when the guest VM makes this call does it save/persist any scheduling information about its current processes like runqueue, process state - runnable, ready etc ? If it does can someone point to the code I can look at.

c) When yielded guest VM is scheduled back by the hypervisor, does it uses the previous state of the processes which were yielded ?

2. Is there a way in which the Hypervisor_sched_op call can be made from hypervisor itself or Dom0 if required ?

Thanks
Mahendra

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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