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] halt() and safe_halt()

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] halt() and safe_halt()
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 23 May 2006 17:49:32 +0200
Delivery-date: Tue, 23 May 2006 08:48:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Considering that halt() is e.g. called (in an endless loop) from 
smp_send_stop() on all but the current CPU, wouldn't it
make more sense to make this HYPERVISOR_block() rather than just ((void)0)? It 
would seem to me that HYPERVISOR_block()
comes fairly close the what the hlt instruction means on real hardware.

Thanks, Jan

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] halt() and safe_halt(), Jan Beulich <=