From: Avi Kivity <avi@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] kvm: fix cr0 initialization on SIPI reset
Date: Sun, 25 Oct 2009 11:40:51 +0200 [thread overview]
Message-ID: <4AE41D23.4080200@redhat.com> (raw)
In-Reply-To: <1256359800-16893-1-git-send-email-ehabkost@redhat.com>
On 10/24/2009 06:49 AM, Eduardo Habkost wrote:
> Hi,
>
> The following patches fix a bug on the SIPI reset code for SVM. cr0 was not
> being reset properly, making KVM keep the vcpu on paging mode, thus not
> being able to run the real-mode boostrap code. This bug was reported at:
> https://bugzilla.redhat.com/show_bug.cgi?id=525699
>
> The first patch is cosmetic, and it just changes the vmx code to use the same
> macros when initializing cr0, instead of a hardcoded hex value.
>
> The patches were tested by running a RHEL-5.4 guest and and triggering the
> SIPI reset by offlining and onlining cpus on the guest. They were tested on
> both NPT-enabled and NPT-disabled cases.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-10-25 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 4:49 [PATCH 0/3] kvm: fix cr0 initialization on SIPI reset Eduardo Habkost
2009-10-24 4:49 ` [PATCH 1/3] kvm: vmx: use macros instead of hex value on cr0 initialization Eduardo Habkost
2009-10-24 4:49 ` [PATCH 2/3] kvm: svm: reset cr0 properly on vcpu reset Eduardo Habkost
2010-03-17 18:17 ` Alexander Graf
2010-03-17 21:42 ` Eduardo Habkost
2010-03-17 21:48 ` Alexander Graf
2010-03-19 14:51 ` Eduardo Habkost
2010-03-19 15:14 ` Alexander Graf
2009-10-24 4:50 ` [PATCH 3/3] kvm: svm: init_vmcb(): remove redundant save->cr0 initialization Eduardo Habkost
2009-10-25 9:40 ` Avi Kivity [this message]
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=4AE41D23.4080200@redhat.com \
--to=avi@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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