mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Bandan Das <bsd@redhat.com>, kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] vmx: miscellaneous cleanups
Date: Thu, 4 Aug 2016 14:21:18 +0200	[thread overview]
Message-ID: <2ca22110-012a-ba62-a9c7-d4977e7e7fda@redhat.com> (raw)
In-Reply-To: <1470169957-12616-1-git-send-email-bsd@redhat.com>



On 02/08/2016 22:32, Bandan Das wrote:
> v1 posted here https://lkml.org/lkml/2016/7/20/605
> 
> v2:
> 1/3 : Replacing BUG_ONs with WARN_ONs is not necessary
> 2/3 : No change
> 3/3 : Remove the kvm parameter from two other functions
> 4/3 : Removed, although the spec says to do it, it can't be triggered
> 
> These are some very minor vmx cleanups.
> 2/4 is necessary for nested esx to be able to
> successfully launch a guest of its own. Without single context
> invalidation present, it just disables ept altogether.
> 
> Bandan Das (3):
>   nvmx: remove comment about missing nested vpid support
>   nvmx: mark ept single context invalidation as supported
>   mmu: don't pass *kvm to spte_write_protect and spte_*_dirty
> 
>  arch/x86/kvm/mmu.c | 12 ++++++------
>  arch/x86/kvm/vmx.c | 15 +++++++--------
>  2 files changed, 13 insertions(+), 14 deletions(-)
> 

Applied patches 1-2, while 3 will wait for 4.9.

Paolo

      parent reply	other threads:[~2016-08-04 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 20:32 Bandan Das
2016-08-02 20:32 ` [PATCH v2 1/3] nvmx: remove comment about missing nested vpid support Bandan Das
2016-08-02 20:32 ` [PATCH v2 2/3] nvmx: mark ept single context invalidation as supported Bandan Das
2016-08-02 20:32 ` [PATCH v2 3/3] mmu: don't pass *kvm to spte_write_protect and spte_*_dirty Bandan Das
2016-08-04 12:21 ` Paolo Bonzini [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=2ca22110-012a-ba62-a9c7-d4977e7e7fda@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=bsd@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkrcmar@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

all inboxes | Powered by JetHome®