Re: [Xen-devel] rendezvousing all physical CPUs

To:	"Keir Fraser" <keir@xxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] rendezvousing all physical CPUs
From:	"ron minnich" <rminnich@xxxxxxxxx>
Date:	Thu, 30 Nov 2006 10:12:29 -0700
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <jbeulich@xxxxxxxxxx>
Delivery-date:	Thu, 30 Nov 2006 09:12:30 -0800
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=g97Y/n5QX+Mp4Sgm2e5b9uMVFXYe0lqG1WrwjuUI5brfE3sR9XruG7OxIG9zY5O0MuZy0JCk8Q0PlX5CYDWc7vUqV6Mo/2u9V72WTSLyEEh6tn8YcSC0i3aDpdctJHo5bOB+KNkntuG7r2oC0+GL2yHDNiYtqQ/PBxbkL9AWkRg=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<C194BD74.54FD%keir@xxxxxxxxxxxxx>
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>
References:	<456F116D.76E4.0078.0@xxxxxxxxxx> <C194BD74.54FD%keir@xxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 11/30/06, Keir Fraser <keir@xxxxxxxxxxxxx> wrote:

How about providing the linear address of a chunk of dom0 code that Xen
should run in ring 0 with CPUs in a particular configuration? We could
provide flags to represent useful configurations: e.g., run on all CPUs
atomicaly, run on CPU0 only and quiesce others, etc.


I thought the goal of Jan's proposal was to have Dom0 take over this
kind of thing, not extend Xen to do it. So his idea of getting CPUs in
a known state, then letting Dom0 handle it, is different, is it not?
Does this really address his problem?

ron

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