WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Question about VCPU's and VM's Blocked state

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Question about VCPU's and VM's Blocked state
From: Huibin QIAN <qianhb@xxxxxxxxxx>
Date: Tue, 19 Jan 2010 11:49:26 +0800
Cc: g00138124@xxxxxxxxxxxxxxxxxxxx, cqj@xxxxxxxxxx, q00147403@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 18 Jan 2010 19:49:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I have some doubt about the vcpu scheduling in xen.

what would make the vcpu be blocked?
In HVM, does the hlt instruction make a vmexit and the hypervisor put the vcpu into sleep queue? Or anything else causes it? What about the PV?

When we use 'xm list' we can get the vm state ,usually it is blocked or running, and what meaning is the blocked state?
Is that mean all the vcpus blonged to this domain are in the sleep queue?
 
Thanks
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>