All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: Jimi Xenidis <jimix@watson.ibm.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	ewan@xensource.com
Subject: Re: [Xen-staging] [xen-unstable] Added some more fields to host_cpu.
Date: Fri, 02 Mar 2007 15:01:39 -0600	[thread overview]
Message-ID: <1172869299.24623.28.camel@basalt> (raw)
In-Reply-To: <1172867986.5941.49.camel@bling>

On Fri, 2007-03-02 at 13:39 -0700, Alex Williamson 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.

Not sure if this affects us.

>    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:
> 
>                 self.cpus[u].update(
>                     { 'host'     : self.uuid,
>                       'features' : cpu_features,
>                       'speed'    : int(float(cpuinfo[0]['cpu MHz'])),
>                       'vendor'   : cpuinfo[0]['vendor'],
>                       'modelname': cpuinfo[0]['family'],
>                       'stepping' : cpuinfo[0]['model'],
>                       'flags'    : cpuinfo[0]['features'],
>                     })

This absolutely does. Ewan, what are you trying to do here, and could
you please revert it until we figure out a solution that will work?

-- 
Hollis Blanchard
IBM Linux Technology Center

  parent reply	other threads:[~2007-03-02 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200702270156.l1R1uLfk014775@latara.uk.xensource.com>
2007-03-02 20:39 ` [Xen-staging] [xen-unstable] Added some more fields to host_cpu Alex Williamson
2007-03-02 20:46   ` Keir Fraser
2007-03-02 20:55     ` Alex Williamson
2007-03-02 20:58       ` Keir Fraser
2007-03-02 20:47   ` John Levon
2007-03-02 20:54     ` John Levon
2007-03-02 21:01   ` Hollis Blanchard [this message]
2007-03-07 17:54   ` Hollis Blanchard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1172869299.24623.28.camel@basalt \
    --to=hollisb@us.ibm.com \
    --cc=alex.williamson@hp.com \
    --cc=ewan@xensource.com \
    --cc=jimix@watson.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.