[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH] Export Multicore information



Hi John,
   Thanks for your comments. The situation is, dom0 may not see all the
processors in the system. Only hyper visor is capable of seeing all. I
would let tools/apps on dom0 to see information about CPUs assigned to
dom0, not the whole set available in the system. So it is necessary to
have a hyper visor specific interface, and in my opinion xm is the best
choice for that.

Thanks & Regards,
Nitin 
Open Source Technology Center, Intel Corporation.
------------------------------------------------------------------------
-
The mind is like a parachute; it works much better when it's open.
-----Original Message-----
From: John Levon [mailto:levon@xxxxxxxxxxxxxxxxx] 
Sent: Monday, December 11, 2006 3:47 PM
To: Kamble, Nitin A
Cc: Keir Fraser; Ian Pratt; Mallick, Asit K; Yu, Wilfred; Xen devel
list; Nakajima, Jun; Yang, Fred
Subject: Re: [Xen-devel] [PATCH] Export Multicore information

On Mon, Dec 11, 2006 at 03:25:49PM -0800, Kamble, Nitin A wrote:

> This information is for administrator/end user of the system to make
> better decisions about partitioning the processors in the system
across
> multiple domains. Dom0 may not be running on all the CPUs in the
system,
> so this gives a view from hyper visor about all the CPUs that hyper
> visor sees. And also the cache info may not always be symmetric in the
> system.

Whilst it might be useful to provide hypercalls for such, I do not think
it makes sense for 'xm' to have this information. It should be provided
as part of whatever OS tools already exist to output this information.
Adding xm cacheinfo seems like a hack.

regards
john

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.