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] [PATCH] Export Multicore information

To: "Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Export Multicore information
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Sat, 16 Dec 2006 08:56:57 +0000
Cc: "Yu, Wilfred" <wilfred.yu@xxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Yang, Fred" <fred.yang@xxxxxxxxx>, "Mallick, Asit K" <asit.k.mallick@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Delivery-date: Sat, 16 Dec 2006 00:56:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <5461330FA59EDB46BE9AB8AAF2C431AD029692DB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: Accdfoc0GRLPeHB9QVCU3IZatg004QABSxZgAA83HIgAGIzYkAAcCLcFAAJ+hP0AIEOFAABfvpGAABTO0v8=
Thread-topic: [Xen-devel] [PATCH] Export Multicore information
User-agent: Microsoft-Entourage/11.2.5.060620
On 15/12/06 11:18 pm, "Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx> wrote:

> 2. Temporary altering vcpu-pcpu binding: To get information for all cpus
> in the guest_land.
>   One issue with this approach is, if the admin has giving fewer than
> total cpus to dom0, and it has hard bound the dom0 vpcus to pvcpus, then
> this will not work.

There is no such hard binding. You can always re-bind a dom0 vcpu to some
other pcpu if you really want to. If we do add hard binding for dom0 then it
will be because we want a 1:1 relationship between vcpus and pcpus -- if
this is added we'll provide a way for the application to detect and switch
to a different mode of operation (where it switches affinity among vcpus,
rather than sitting on one vcpu and switching among pcpus).

We don't want any more hypercall interfaces, and we probably don't want any
more sysfs interfaces. This can all be coded in userland.

 -- Keir


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