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

Re: [Xen-devel] Re: [Xen-staging] [xen-unstable] Added some more fields to host_cpu.

On 2/3/07 20:39, "Alex Williamson" <alex.williamson@xxxxxx> wrote:

>   On ia64, dom0 doesn't automatically get vcpus for each physical cpu,
> so the first problem is that we're not going to have a /proc/cpuinfo
> entry for every cpu in self.cpus.keys.  I think it's likely x86 could
> run into this problem too if a cpu was hotplugged or booted with the
> dom0_max_vcpus options.

We have indeed hit this problem and I put a patch in this afternoon to
duplicate cpu0's info for any non-existent cpu. Given that the dom0 cpus
could be migrating around on arbitrary physical cpus (even across the
multiple CPUID invocations that the kernel will have made to build the
information for a single 'cpu' in /proc!) this is fine -- x86 multiprocessor
systems are supposed to be symmetric (homogeneous CPUs down to the same
stepping in some cases) anyway.

 -- Keir

>    The second problem is that /proc/cpuinfo fields are very architecture
> specific.  I'd suggest importing arch and having separate cases for x86,
> ia64, and powerpc.  For ia64, think the most appropriate mapping would
> be:

Xen-devel mailing list



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