public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Bandan Das <bsd@redhat.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [RFC PATCH 0/4] Add support for EPT execute only for nested hypervisors
Date: Wed, 22 Jun 2016 12:34:54 -0400	[thread overview]
Message-ID: <jpglh1xw5ap.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <576A169B.5090608@linux.intel.com> (Xiao Guangrong's message of "Wed, 22 Jun 2016 12:39:55 +0800")

Xiao Guangrong <guangrong.xiao@linux.intel.com> writes:

> On 06/21/2016 11:12 AM, Bandan Das wrote:
>> 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" :)
>
> Thank you, Bandan! I really hope all mmu related patches can be CCed to me
> in case if i am too busy to watch patches in kvm mail list. :)

We all try but it's easy to miss interested people in the cc list :)

> Some points are missed in this patchset:
> 1) You also need to tech is_present_gpte() about this fact.

If I understood right, this isn't needed anymore since a check
for rsvd bits follows and is_present_gpte already does pte & 7.

> 2) update_permission_bitmask() need to be fixed as it always expects
>    that read-access is available (actually, read-access is equal with
>    user-access if ept is shadowed).
Do you mean this part of update_permission_bitmask() ?
...
} else
  	/* Not really needed: no U/S accesses on ept  */
	u = 1;
        

  reply	other threads:[~2016-06-22 16:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  3:12 [RFC PATCH 0/4] Add support for EPT execute only for nested hypervisors Bandan Das
2016-06-21  3:12 ` [RFC PATCH 1/4] mmu: add a boolean to indicate host ept execute only support Bandan Das
2016-06-21  3:12 ` [RFC PATCH 2/4] mmu: Update ept specific valid bit values Bandan Das
2016-06-21  8:08   ` Paolo Bonzini
2016-06-22  4:09   ` Xiao Guangrong
2016-06-21  3:12 ` [RFC PATCH 3/4] mmu: don't set the present bit unconditionally Bandan Das
2016-06-21  8:12   ` Paolo Bonzini
2016-06-21  8:40     ` Paolo Bonzini
2016-06-22 16:10     ` Bandan Das
2016-06-22 16:12       ` Paolo Bonzini
2016-06-22 16:23         ` Bandan Das
2016-06-22  4:30   ` Xiao Guangrong
2016-06-22 16:21     ` Bandan Das
2016-06-21  3:12 ` [RFC PATCH 4/4] vmx: advertise support for ept execute only Bandan Das
2016-06-22  4:39 ` [RFC PATCH 0/4] Add support for EPT execute only for nested hypervisors Xiao Guangrong
2016-06-22 16:34   ` Bandan Das [this message]
2016-06-23  5:03     ` Xiao Guangrong
2016-06-24  2:56       ` Bandan Das
2016-06-24  4:22         ` Paolo Bonzini
2016-06-24  4:50           ` Bandan Das
2016-06-24  6:46             ` Paolo Bonzini
2016-06-24  7:02               ` Xiao Guangrong
2016-06-24 16:19               ` 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=jpglh1xw5ap.fsf@linux.bootlegged.copy \
    --to=bsd@redhat.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kvm@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