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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>, "Niraj Tolia" <ntolia@xxxxxxxxx>
Subject: RE: [Xen-devel] Problems with enabling hypervisor C and P-statecontrol
From: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>
Date: Mon, 27 Oct 2008 15:02:14 -0000
Cc: "Liu, Jinsong" <jinsong.liu@xxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 27 Oct 2008 08:02:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C52B557A.286EA%keir.fraser@xxxxxxxxxxxxx>
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>
References: <D8078B8B3B09934AA9F8F2D5FB3F28CE09395A5F7F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C52B557A.286EA%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ack1k09vvX8kyUpuQteURFjSSiRC2wABxX6wAATWm9AAAS6wMAAlY1EgABo7cqQAVeedoAAHgcaXAAeI4lA=
Thread-topic: [Xen-devel] Problems with enabling hypervisor C and P-statecontrol
> > Also how about BSP? If BSP is not thread0/core0/package0,
> > then all the rest sorting effort is just meaningless. :-(
> 
> True. Another possibility would be to provide a remapping between CPU
> identifiers used within Xen and those exposed to tools via
> sysctl/domctl.
> The latter could be sorted; and no ordering constraints placed on the
> former.

That's likely to get very confusing when it comes to debugging...

Have we seen any systems where the boot CPU isn't thread 0, core 0,
socket 0?

Thanks,
Ian
 
> > This is necessary information. Is there any existing interface
> reporting
> > similar info? If not, could you suggest which interface to carry?
> Tools
> > like xenpm may need to query such infro to construct a better
> summary.
> > If it's not there, we can consider to add.
> 
> The info is not available right now. It could be exposed via sysctl.
> Either
> a new sysctl or by extending existing XEN_SYSCTL_getcpuinfo.
> 
>  -- keir
> 


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

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