linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bandan Das <bsd@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, guangrong.xiao@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Add support for EPT execute only for nested hypervisors
Date: Tue, 28 Jun 2016 00:32:35 -0400	[thread overview]
Message-ID: <1467088360-10186-1-git-send-email-bsd@redhat.com> (raw)

These patches are based on reviews to my RFC
http://www.spinics.net/lists/kvm/msg134440.html

Changes since RFC:
 - Remove shadow_xonly_valid, it's not needed
 - Remove checks from is_shadow_present_pte()
 - In reset_tdp_shadow_zero_bits_mask, pass correct execonly to __reset_rsvds_bits_mask_ept
 - Reuse shadow_user_mask in set_spte()
 - Remove is_present_gpte() and inline the operation at the two call sites

I spoke to Paolo about this a while back and thought to post this as
RFC while I am thinking of adding some unit tests.

Background: ESX refuses to run as L1 if support for EPT execute only isn't
found. I am not really sure if it uses it for anything since just advertising
the bits seems to work but adding the necessary plumbing seemed like a good idea.

Xiao, I took the liberty of adding you based on "git blame" :)

Thanks in advance.

Bandan Das (5):
  mmu: mark spte present if the x bit is set
  mmu: pass execonly value when initializing rsvd bits
  mmu: don't set the present bit unconditionally
  mmu: remove is_present_gpte()
  nvmx: advertise support for ept execute only

 arch/x86/kvm/mmu.c         | 26 ++++++++++++++++++--------
 arch/x86/kvm/mmu.h         |  5 -----
 arch/x86/kvm/paging_tmpl.h |  4 ++--
 arch/x86/kvm/vmx.c         |  5 ++++-
 arch/x86/kvm/x86.c         |  2 +-
 5 files changed, 25 insertions(+), 17 deletions(-)

-- 
2.5.5

             reply	other threads:[~2016-06-28  4:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  4:32 Bandan Das [this message]
2016-06-28  4:32 ` [PATCH 1/5] mmu: mark spte present if the x bit is set Bandan Das
2016-06-28  8:44   ` Paolo Bonzini
2016-06-28 17:33     ` Bandan Das
2016-06-28 20:17       ` Paolo Bonzini
2016-06-28 20:37         ` Bandan Das
2016-06-28 20:49           ` Paolo Bonzini
2016-06-28 21:04             ` Bandan Das
2016-06-29  3:01             ` Xiao Guangrong
2016-07-05  3:06             ` Wanpeng Li
2016-07-05 10:50               ` Paolo Bonzini
2016-07-05 11:29                 ` Wanpeng Li
2016-06-28  4:32 ` [PATCH 2/5] mmu: pass execonly value when initializing rsvd bits Bandan Das
2016-06-29  3:07   ` Xiao Guangrong
2016-06-28  4:32 ` [PATCH 3/5] mmu: don't set the present bit unconditionally Bandan Das
2016-06-28  8:57   ` Paolo Bonzini
2016-06-28 17:30     ` Bandan Das
2016-06-28 20:21       ` Paolo Bonzini
2016-07-05  5:50     ` Wanpeng Li
2016-07-05 10:50       ` Paolo Bonzini
2016-06-29  3:17   ` Xiao Guangrong
2016-06-29  8:18     ` Paolo Bonzini
2016-06-30  7:18       ` Xiao Guangrong
2016-06-28  4:32 ` [PATCH 4/5] mmu: remove is_present_gpte() Bandan Das
2016-06-28  4:32 ` [PATCH 5/5] nvmx: advertise support for ept execute only Bandan Das

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=1467088360-10186-1-git-send-email-bsd@redhat.com \
    --to=bsd@redhat.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@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;
as well as URLs for NNTP newsgroup(s).