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

Re: [Xen-devel] rendezvousing all physical CPUs

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] rendezvousing all physical CPUs
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Thu, 30 Nov 2006 16:55:16 +0000
Delivery-date: Thu, 30 Nov 2006 08:55:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <456F116D.76E4.0078.0@xxxxxxxxxx>
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
Thread-index: AccUoE87jZDon4CTEdubHwAX8io7RQ==
Thread-topic: [Xen-devel] rendezvousing all physical CPUs
User-agent: Microsoft-Entourage/11.2.5.060620
On 30/11/06 16:14, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Will it be acceptable to create hypercall sub-functions (would probably go
> into the platform group, but should be architecture independent) to allow
> Dom0 to halt all physical CPUs but the current one, and later restart them?
> Or should it rather be a single call with an event-channel based call back
> to carry out the operation that must be protected?

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.

As you say this could be used for things arguably more useful than this RNG
example, like microcode updates and maybe even the MTRR updates could be
done in dom0 too, which would be very nice. :-)

 -- Keir


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