|
xen-devel
Re: [Xen-devel] [PATCH] Export Multicore information
|
To: |
"Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] [PATCH] Export Multicore information |
|
From: |
Emmanuel Ackaouy <ack@xxxxxxxxxxxxx> |
|
Date: |
Tue, 12 Dec 2006 20:01:52 +0000 |
|
Cc: |
"Yu, Wilfred" <wilfred.yu@xxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, "Mallick, Asit K" <asit.k.mallick@xxxxxxxxx>, "Yang, Fred" <fred.yang@xxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx> |
|
Delivery-date: |
Tue, 12 Dec 2006 12:01:49 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<5461330FA59EDB46BE9AB8AAF2C431AD0282E0FC@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> |
|
Mail-followup-to: |
"Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, "Mallick, Asit K" <asit.k.mallick@xxxxxxxxx>, "Yu, Wilfred" <wilfred.yu@xxxxxxxxx>, Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Yang, Fred" <fred.yang@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx> |
|
References: |
<5461330FA59EDB46BE9AB8AAF2C431AD0282E0FC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.4.1i |
Nitin,
In terms of topology, aren't the sibling and core maps enough
information? I guess we could plan ahead for nodes in the
interface too. Do we really need to export cpu, core, and
package ids though? Also, should we export info for anything
other than online cpus?
I've only looked at the code to support XEN_SYSCTL_cpuinfo in
sysctl.c. I don't get the "count" check here. Looks like we
ignore the size of the array passed by the user. We read it
but ignore it. Am I missing something?
Cheers,
Emmanuel.
On Fri, Dec 08, 2006 at 05:41:26PM -0800, Kamble, Nitin A wrote:
> Hi Keir, Ian,
>
> Attached is a patch which implements "xm cpuinfo" and "xm cacheinfo"
> commands. Output of these commands on a 4 way paxville (2 core per socket,
> 2 threads per core) and 2 way clovertown (Quadcore) system is shown
> bellow.
>
> It would be easy to extend this functionality to other architectures
> such as IA64 or power by reusing most of the code. Other architectures
> would need to implement switch-cases XEN_SYSCTL_cpuinfo: &
> XEN_SYSCTL_cacheinfo: in their arch_do_sysctl() in the function hyper
> visor to get this functionality.
>
>
>
> The Changes are distributed in 3 areas viz hyper visor, libxc and
> python code as seen in the diffstat bellow.
>
>
>
> Please apply and/or provide comments for the patch.
>
>
>
> Signed-Off-By: Nitin A Kamble <nitin.a.kamble@xxxxxxxxx>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home