From: Avi Kivity <avi@qumranet.com>
To: Zachary Amsden <zach@vmware.com>
Cc: Gabriel Barazer <gabriel@oxeva.fr>, Andi Kleen <ak@suse.de>,
Jim Mattson <jmattson@vmware.com>,
linux-kernel@vger.kernel.org,
Virtualization Mailing List <virtualization@lists.osdl.org>,
kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: 2.6.22 x86_64 : kernel initial decompression hangs on vmware
Date: Thu, 09 Aug 2007 23:57:48 +0300 [thread overview]
Message-ID: <46BB7FCC.4040509@qumranet.com> (raw)
In-Reply-To: <46B4A7E4.4030907@vmware.com>
Zachary Amsden wrote:
>
> Since I was just involved in the boot decompressor for another bug, I
> took a look at this. 2.6.22 switches it to be 64-bit code. VT is
> very picky about what state it can run in. Not using VT on Intel
> 64-bit hardware cripples performance, running at far below normal
> speed, and taking minutes to decompress the kernel, which is nearly
> instantaneous otherwise.
>
> To get back into VT in this case, not only do we need to load FS and
> GS, we also need to setup an initial LDT and task. Can you try the
> attached patch and see that it does the right thing?
>
> I've also cc'd the KVM developers, as the same problem will affect
> them, and hopefully the same patch will fix it.
>
We haven't seen any issue with the 2.6.22 boot decompressor. Which of
the four (fs, gs, ldt, or tr) were proving problematic and why?
next prev parent reply other threads:[~2007-08-09 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 0:08 2.6.22 x86_64 : kernel initial decompression hangs on vmware Gabriel Barazer
2007-07-26 0:19 ` Zachary Amsden
2007-08-04 16:23 ` Zachary Amsden
2007-08-04 17:18 ` Gabriel Barazer
2007-08-09 20:57 ` Avi Kivity [this message]
2007-08-09 23:28 ` Zachary Amsden
2007-08-10 1:48 ` 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=46BB7FCC.4040509@qumranet.com \
--to=avi@qumranet.com \
--cc=ak@suse.de \
--cc=gabriel@oxeva.fr \
--cc=jmattson@vmware.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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