xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "AP Xen" <apxeng@gmail.com>
To: 'Jeremy Fitzhardinge' <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: RE: Ubuntu 10.04 stuck in detect_extended_topology()
Date: Wed, 9 Jun 2010 17:29:39 -0700	[thread overview]
Message-ID: <007a01cb0834$052e8ed0$0f8bac70$@com> (raw)
In-Reply-To: <4C101896.8090608@goop.org>

> > The ECX leaf subtype never returns CORE_TYPE or INVALID_TYPE. So
> think
> > I might be running in to a bug / quirk in the CPUID handling code in
> > Xen packaged with CentOS 5.4. Is there a work around for it? Maybe
> > specifying something in the cpuid option in the config file.
> >
> 
> What's the host cpu type?  You should be able to completely disable the
> extended topology leaf (0xb) with the cpuid= directive in the config
> file.

The host cpu type is "Intel(R) Xeon(R) CPU E5520  @ 2.27GHz" (x86_64).

What should I specify in "cpuid=" in the config file? I tried the following:

cpuid = [ '0xb:ebx=xxxxxxxxxxxxxxxx0000000000000000' ]

Is that correct?

However, it did not have any effect. I do not see any mention of it in
xend.log. Maybe the version of Xen packaged with CentOS 5.4 not support the
cpuid config option.

xen_major              : 3
xen_minor              : 1
xen_extra              : .2-164.11.1.el5

AP

  reply	other threads:[~2010-06-10  0:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 21:55 Ubuntu 10.04 stuck in detect_extended_topology() AP Xen
2010-06-09 22:41 ` Jeremy Fitzhardinge
2010-06-10  0:29   ` AP Xen [this message]
2010-06-10  0:54     ` Jeremy Fitzhardinge
2010-06-10  6:01       ` Pasi Kärkkäinen
2010-06-10 16:53         ` AP Xen
2010-07-02 13:48       ` Andrew Jones

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='007a01cb0834$052e8ed0$0f8bac70$@com' \
    --to=apxeng@gmail.com \
    --cc=jeremy@goop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).