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] Problems with enabling hypervisor C and P-statecontrol

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, 'Ian Pratt' <Ian.Pratt@xxxxxxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>, Niraj Tolia <ntolia@xxxxxxxxx>
Subject: Re: [Xen-devel] Problems with enabling hypervisor C and P-statecontrol
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sat, 25 Oct 2008 15:50:02 +0100
Cc: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>, Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 25 Oct 2008 07:50:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <D8078B8B3B09934AA9F8F2D5FB3F28CE09395A5F73@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack1k09vvX8kyUpuQteURFjSSiRC2wABxX6wAATWm9AAAS6wMAAlY1EgABo7cqQ=
Thread-topic: [Xen-devel] Problems with enabling hypervisor C and P-statecontrol
User-agent: Microsoft-Entourage/11.4.0.080122
On 25/10/08 04:01, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

>> We really ought to have code in Xen to make the enumeration consistent
>> regardless of the BIOS order. I don't really care whether its
>> sockets/cores/threads or threads/cores/sockets, but we really ought to
>> be consistent.
> 
> If Xen wants to be consistent with one policy, as you suggested, it
> requires core/thread info known before booting APs, and then take
> that info in alloc_cpu_id. However core/thread info can be only
> acquired on AP by CPUID and sibling/core map can be constructed
> after all APs are booted.

Sort by LAPIC ID. The LAPIC ID is defined to be hierarchical, so this would
automatically get us sorting by thread then core then socket. This could be
as simple as arranging for the calls to mp_register_lapic() to happen in the
correct order.

> Then you may need a temporary cpu id
> allocated and then switch it to a real one later. This looks a bit
> messed on some arrays[NR_CPUS]. Is it worthy of doing that way,
> or just expose the mapping between xen cpu id and sockets/cores/
> threads?

The mapping between flat identifier and socket/core/thread should be made
available, and/or modify tools to accept a hierarchical cpu identifier in
addition to the old-style flat identifier.

 -- Keir



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

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