From: Ingo Molnar <mingo@elte.hu>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "Yang, Wei Y" <wei.y.yang@intel.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Avi Kivity <avi@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Patch v5 1/4] Remove SMEP bit from CR4_RESERVED_BITS
Date: Wed, 1 Jun 2011 09:46:49 +0200 [thread overview]
Message-ID: <20110601074649.GA774@elte.hu> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1505CA61C0F62@shsmsx502.ccr.corp.intel.com>
* Tian, Kevin <kevin.tian@intel.com> wrote:
> > From: Ingo Molnar
> > Sent: Monday, May 30, 2011 3:41 PM
> >
> >
> > * Yang, Wei Y <wei.y.yang@intel.com> wrote:
> >
> > > This patch removes SMEP bit from CR4_RESERVED_BITS.
> >
> > I'm wondering, what is the best-practice way for tools/kvm/ to set
> > SMEP for the guest kernel automatically, even if the guest kernel
> > itsef has not requested SMEP?
> >
>
> enabling SMEP w/o guest's knowledge can be problematic if the guest
> is doing U/S 0->1 bit change w/o TLB invalidation, which is a
> required action to ensure SMEP protection working correctly. Linux
> versions known so far don't have this behavior because TLB
> invalidation due to P bit change covers U/S 0->1 change. [...]
We'd like to use this in the 'kvm' tool:
git clone git://github.com/penberg/linux-kvm master
cd linux-kvm/tools/kvm/
make -j
Which is only interested in Linux guests.
Thanks,
Ingo
next prev parent reply other threads:[~2011-06-01 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 3:01 [Patch v5 1/4] Remove SMEP bit from CR4_RESERVED_BITS Yang, Wei Y
2011-05-30 7:40 ` Ingo Molnar
2011-05-30 7:49 ` Avi Kivity
2011-05-30 8:05 ` Ingo Molnar
2011-05-30 8:43 ` Avi Kivity
2011-05-30 8:52 ` Ingo Molnar
2011-05-30 8:53 ` Avi Kivity
2011-05-30 8:57 ` Ingo Molnar
2011-05-30 9:00 ` Avi Kivity
2011-06-01 7:18 ` Tian, Kevin
2011-06-01 7:46 ` Ingo Molnar [this message]
2011-06-01 7:55 ` Avi Kivity
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=20110601074649.GA774@elte.hu \
--to=mingo@elte.hu \
--cc=avi@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--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.