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>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] rendezvousing all physical CPUs
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 01 Dec 2006 09:11:17 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Dec 2006 01:11:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <456FF2F8.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: AccVKKhP5pMOToEbEduAwAAX8io7RQ==
Thread-topic: [Xen-devel] rendezvousing all physical CPUs
User-agent: Microsoft-Entourage/11.2.5.060620
On 1/12/06 08:16, "Jan Beulich" <jbeulich@xxxxxxxxxx> 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.
> 
> Hmm??? I would have to question why dom0 currently gets run in ring 1 then.

Uniformity with execution of other domains and it's also a useful safety
mechanism for catching dom0 bugs. It is *not* for security reasons!

> I would at best consider allowing the guest to pass a batch of operations that
> it wants carried out - I/O memory accesses (normal RAM not allowed), MSR
> reads/writes, port I/O. However, for the specific case of the RNG, PCI config
> space accesses would also need to be supported - while they can be reduced
> to iomem or port accesses, abstracting this out from the requester and from
> Xen would require some thought.

Dom0 can map any memory, DMA to any memory, and with your original proposed
hypercall would be able to tear down physical CPUs for unbounded time
periods. It 0wns the machine already. ;-)

 -- Keir


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

<Prev in Thread] Current Thread [Next in Thread>