From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Andy Walls <awalls@md.metrocast.net>
Subject: Re: [PATCH] KVM: Don't allow lmsw to clear cr0.pe
Date: Thu, 13 May 2010 00:31:24 -0300 [thread overview]
Message-ID: <20100513033124.GA4867@amt.cnet> (raw)
In-Reply-To: <1273613324-31910-1-git-send-email-avi@redhat.com>
On Wed, May 12, 2010 at 12:28:44AM +0300, Avi Kivity wrote:
> The current lmsw implementation allows the guest to clear cr0.pe, contrary
> to the manual, which breaks EMM386.EXE.
>
> Fix by ORing the old cr0.pe with lmsw's operand.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> arch/x86/kvm/x86.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2010-05-13 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 21:28 [PATCH] KVM: Don't allow lmsw to clear cr0.pe Avi Kivity
2010-05-11 22:13 ` Andy Walls
2010-05-12 16:18 ` Andy Walls
2010-05-13 3:31 ` Marcelo Tosatti [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=20100513033124.GA4867@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=awalls@md.metrocast.net \
--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).