From: Avi Kivity <avi@redhat.com>
To: BuraphaLinux Server <buraphalinuxserver@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: random crash in post_kvm_run()
Date: Mon, 05 Jul 2010 10:42:46 +0300 [thread overview]
Message-ID: <4C318CF6.9000601@redhat.com> (raw)
In-Reply-To: <AANLkTim2cEC5_n7Zaa1iSm-Vkrp4XP87sG1t1nVDI3aN@mail.gmail.com>
Please don't top-post.
On 07/03/2010 05:23 PM, BuraphaLinux Server wrote:
> Ok, I kept going like you said. Here is what it said:
>
> $git bisect good
> 44ea2b1758d88ad822e65b1c4c21ca6164494e27 is the first bad commit
> commit 44ea2b1758d88ad822e65b1c4c21ca6164494e27
> Author: Avi Kivity<avi@redhat.com>
> Date: Sun Sep 6 15:55:37 2009 +0300
>
> KVM: VMX: Move MSR_KERNEL_GS_BASE out of the vmx autoload msr area
>
> Currently MSR_KERNEL_GS_BASE is saved and restored as part of the
> guest/host msr reloading. Since we wish to lazy-restore all the other
> msrs, save and reload MSR_KERNEL_GS_BASE explicitly instead of using
> the common code.
>
> Signed-off-by: Avi Kivity<avi@redhat.com>
>
That doesn't make any sense. This commit shouldn't affect anything in
user-kernel communications.
Can you describe your environment? I'll try to reproduce it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-07-05 7:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 17:28 random crash in post_kvm_run() BuraphaLinux Server
2010-06-28 18:38 ` Brian Jackson
2010-06-30 17:57 ` BuraphaLinux Server
2010-06-29 12:16 ` Avi Kivity
2010-06-30 18:25 ` BuraphaLinux Server
2010-07-01 11:44 ` Avi Kivity
2010-07-02 19:08 ` BuraphaLinux Server
2010-07-03 10:28 ` Avi Kivity
2010-07-03 14:23 ` BuraphaLinux Server
2010-07-05 7:42 ` Avi Kivity [this message]
2010-07-05 8:52 ` BuraphaLinux Server
2010-07-05 10:15 ` Avi Kivity
2010-07-06 7:46 ` Avi Kivity
2010-07-06 8:37 ` Avi Kivity
2010-07-06 15:58 ` BuraphaLinux Server
2010-07-07 9:12 ` Avi Kivity
2010-06-30 18:06 ` Anthony Liguori
2010-06-30 18:32 ` BuraphaLinux Server
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=4C318CF6.9000601@redhat.com \
--to=avi@redhat.com \
--cc=buraphalinuxserver@gmail.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).