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

Re: [Xen-devel] rendezvousing all physical CPUs


  • To: "Keir Fraser" <keir@xxxxxxxxxxxxx>
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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


 


Rackspace

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