From: Avi Kivity <avi@redhat.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: deactivate fpu when cr0.PE ON?
Date: Sat, 11 Apr 2009 14:43:19 +0300 [thread overview]
Message-ID: <49E08257.9090503@redhat.com> (raw)
In-Reply-To: <9832F13BD22FB94A829F798DA4A8280501A4041722@pdsmsx503.ccr.corp.intel.com>
Dong, Eddie wrote:
> Following code deactivate fpu when CR0.PE is on, any explaination? Rest of code active/deactive fpu based on cr0.TS bit.
>
>
>
The idea is, if the guest is doing a context switch, then it will likely
set its own lazy fpu code, so we anticipate it and deactivate the cpu.
When cr0.pe is cleared, lazy fpu usually doesn't work so we leave it
enabled.
However the mechanism of deactivating the fpu on cr3 write doesn't work
with npt or ept, I'd like to replace it with something better.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-04-11 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 8:19 deactivate fpu when cr0.PE ON? Dong, Eddie
2009-04-11 11:43 ` 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=49E08257.9090503@redhat.com \
--to=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