All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
	"David Woodhouse" <dwmw@amazon.co.uk>,
	"KarimAllah Ahmed" <karahmed@amazon.de>
Subject: Re: [PATCH 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti
Date: Sat, 27 Jan 2018 09:39:52 +0100	[thread overview]
Message-ID: <0c0ea511-23bd-bef0-7275-1943c2aa7959@redhat.com> (raw)
In-Reply-To: <1517007111-13659-1-git-send-email-pbonzini@redhat.com>

On 26/01/2018 23:51, Paolo Bonzini wrote:
> David and others,
> 
> the following changes since commit ba804bb4b72e57374b5f567b783aa0298fba0ce6:
> 
>   Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2018-01-26 09:03:16 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/virt/kvm/kvm.git msr-bitmaps
> 
> for you to fetch changes up to de4004d8b8c9da2a3923e42577307c59c71ab8e6:
> 
>   KVM: VMX: make MSR bitmaps per-VCPU (2018-01-26 22:59:32 +0100)
> 
> The patches are on top of Linus's tree and I checked that they apply okay
> on top of the latest 4.14 tree as well as required for tip x86/pti.
> One extra commit is needed that is pretty safe and would have been merged
> next week.

... and there's an issue in the patches (the choice of whether to
intercept MSR_KERNEL_GS_BASE is inverted).  I'll blame what's left of
this week's flu and send v2.

Paolo

> Radim, please pull this into kvm.git too.  The merge is a bit messy, so I've
> placed my resolution on kvm.git, branch refs/heads/msr-bitmaps-merge-resolution.
> It's based on kvm/queue, assuming that all of kvm/queue will get into the
> pull requests for the 4.16 merge window (and thus soonish in kvm/next).
> Hopefully the next few releases will be much more uneventful...
> 
> Thanks,
> 
> Paolo
> 
> Jim Mattson (1):
>   KVM: nVMX: Eliminate vmcs02 pool
> 
> Paolo Bonzini (2):
>   KVM: VMX: introduce alloc_loaded_vmcs
>   KVM: VMX: make MSR bitmaps per-VCPU
> 
>  arch/x86/kvm/vmx.c | 437 ++++++++++++++++++++++-------------------------------
>  1 file changed, 183 insertions(+), 254 deletions(-)
> 

      parent reply	other threads:[~2018-01-27  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 22:51 [PATCH 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti Paolo Bonzini
2018-01-26 22:51 ` [PATCH 1/3] KVM: nVMX: Eliminate vmcs02 pool Paolo Bonzini
2018-01-26 22:51 ` [PATCH 2/3] KVM: VMX: introduce alloc_loaded_vmcs Paolo Bonzini
2018-01-26 22:51 ` [PATCH 3/3] KVM: VMX: make MSR bitmaps per-VCPU Paolo Bonzini
2018-01-30 17:12   ` Jim Mattson
2018-01-27  8:39 ` 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=0c0ea511-23bd-bef0-7275-1943c2aa7959@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dwmw@amazon.co.uk \
    --cc=karahmed@amazon.de \
    --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 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.