From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, eddie.dong@intel.com
Subject: Re: Commit 3d28613c225ba94062950dacbb2304b2d2024abc breaks linux boot
Date: Wed, 1 Apr 2009 17:52:43 +0300 [thread overview]
Message-ID: <20090401145243.GF4013@redhat.com> (raw)
In-Reply-To: <49D37EE4.9080608@redhat.com>
On Wed, Apr 01, 2009 at 05:49:08PM +0300, Avi Kivity wrote:
> Gleb Natapov wrote:
>> Commit 3d28613c225ba94062950dacbb2304b2d2024abc break linux boot.
>> It hangs after printing:
>> SMP alternatives: switching to UP code
>>
>
> Does dropping bit 8 from context->rsvd_bits_mask[0][1] (PT64_ROOT_LEVEL)
> help?
>
Yep.
--
Gleb.
next prev parent reply other threads:[~2009-04-01 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 14:43 Commit 3d28613c225ba94062950dacbb2304b2d2024abc breaks linux boot Gleb Natapov
2009-04-01 14:49 ` Avi Kivity
2009-04-01 14:52 ` Gleb Natapov [this message]
2009-04-02 21:15 ` Ryan Harper
2009-04-03 1:49 ` Sheng Yang
2009-04-03 11:07 ` Avi Kivity
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=20090401145243.GF4013@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=eddie.dong@intel.com \
--cc=kvm@vger.kernel.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 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).