All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH][STABLE] kvm: Fix cpuid initialization
Date: Mon, 13 Apr 2009 18:20:59 +0200	[thread overview]
Message-ID: <49E3666B.209@web.de> (raw)
In-Reply-To: <20090413140727.GA13193@lst.de>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Christoph Hellwig wrote:
> On Mon, Apr 13, 2009 at 10:53:06AM +0200, Jan Kiszka wrote:
>> [ Looks like we need more kvm users via upstream qemu... ]
>>
>> Fix (more or less) spurious guest boot failures due to corrupted cpuid
>> states. The reason was insufficient initialization of cpuid entries
>> before passing them to the kernel.
>>
>> At this chance also fix improper entry pointer progression and simplify
>> the code a bit.
> 
> Is that guest kernel stuck on the "testing hlt" message in the Linux
> kernel with that one?  I've seen that hang for a while now, but haven't
> been able to bisect it yet.

Maybe. For me it was "This kernel requires an XXX CPU, but only detected
an *i086* CPU." from arch/x86/boot/cpu.c. But if the hlt test depends on
certain cpuid values to do the right thing, your case may be fixed, too.
Does qemu from the kvm tree work for you?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-04-13 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  8:53 [Qemu-devel] [PATCH][STABLE] kvm: Fix cpuid initialization Jan Kiszka
2009-04-13 14:07 ` Christoph Hellwig
2009-04-13 16:20   ` Jan Kiszka [this message]
2009-04-13 18:21     ` [Qemu-devel] " Christoph Hellwig
2009-04-17 21:21 ` [Qemu-devel] " Anthony Liguori

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=49E3666B.209@web.de \
    --to=jan.kiszka@web.de \
    --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.