From: Avi Kivity <avi@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "Yang, Wei Y" <wei.y.yang@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Patch v5 0/4] Enable SMEP feature support for kvm
Date: Mon, 30 May 2011 12:13:41 +0300 [thread overview]
Message-ID: <4DE35FC5.5030804@redhat.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1505CA61C0506@shsmsx502.ccr.corp.intel.com>
On 05/30/2011 12:08 PM, Tian, Kevin wrote:
> > From: Avi Kivity
> > Sent: Monday, May 30, 2011 4:52 PM
> >
> > On 05/30/2011 06:01 AM, Yang, Wei Y wrote:
> > > This patchset enables a new CPU feature SMEP (Supervisor Mode Execution
> > > Protection) in KVM. SMEP prevents kernel from executing code in application.
> > > Updated Intel SDM describes this CPU feature. The document will be
> > > published soon.
> > >
> > > This patchset is based on Fenghua's SMEP patch series, as referred by:
> > > https://lkml.org/lkml/2011/5/17/523
> >
> > Looks good. I'll post the cr0.wp=0 fixup soon.
> >
>
> what's your planned fix? through NX bit? :-)
Yes.
> btw, why is current scheme used to emulate cr0.wp=0 case instead of simply
> emulating it?
How would you simply emulate it?
We have to force cr0.wp=1, otherwise we cannot write-protect guest page
tables. Once we do that, we have to set U=1 to allow user reads or U=0
to allow kernel writes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-30 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 3:01 [Patch v5 0/4] Enable SMEP feature support for kvm Yang, Wei Y
2011-05-30 8:52 ` Avi Kivity
2011-05-30 9:08 ` Tian, Kevin
2011-05-30 9:13 ` Avi Kivity [this message]
2011-05-30 9:18 ` Tian, Kevin
2011-05-30 10:00 ` Avi Kivity
2011-05-30 10:32 ` Tian, Kevin
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=4DE35FC5.5030804@redhat.com \
--to=avi@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=wei.y.yang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.