All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>, gleb@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] QEMU maxcpus support v4
Date: Thu, 23 Jul 2009 17:03:41 +0200	[thread overview]
Message-ID: <20090723150341.281387164@sgi.com> (raw)

Hi,

Ok so this time I think i nailed the problem. Using Anthony's tree I
was able to reproduce the failure. Why it worked with my testing
previously I have no idea :-(

The problem was that the local processor APICs were not marked
disabled for the processors not being active. I also changed the code
to mark unused processors as disabled in the MP table, though that
seemed to have no impact on this particular failure.

With this version I can boot Ubuntu all the way to X using Anthony's
tree.

Sorry for the noise, I am still mystified :-(

Cheers,
Jes

             reply	other threads:[~2009-07-23 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 15:03 Jes Sorensen [this message]
2009-07-23 15:03 ` [Qemu-devel] [PATCH 1/2] Introduce -smp , maxcpus= flag to specify maximum number of CPUS Jes Sorensen
2009-07-23 15:03 ` [Qemu-devel] [PATCH 2/2] QEMU BOCHS bios patches to use maxcpus value Jes Sorensen

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=20090723150341.281387164@sgi.com \
    --to=jes@sgi.com \
    --cc=aliguori@us.ibm.com \
    --cc=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.