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: [PATCH v3 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti
Date: Wed, 31 Jan 2018 16:09:21 -0500 [thread overview]
Message-ID: <20180131210924.22812-1-pbonzini@redhat.com> (raw)
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 904e14fb7cb96401a7dc803ca2863fd5ba32ffe6:
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
for 4.16 anyway.
Radim, please pull this into kvm.git too. As before I've placed my
resolution on kvm.git, branch refs/heads/msr-bitmaps-merge-resolution.
It's based on kvm/next this time.
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 | 440 ++++++++++++++++++++++-------------------------------
1 file changed, 186 insertions(+), 254 deletions(-)
--
2.14.3
next reply other threads:[~2018-01-31 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 21:09 Paolo Bonzini [this message]
2018-01-31 21:09 ` [PATCH 1/3] KVM: nVMX: Eliminate vmcs02 pool Paolo Bonzini
2018-01-31 21:09 ` [PATCH 2/3] KVM: VMX: introduce alloc_loaded_vmcs Paolo Bonzini
2018-01-31 21:09 ` [PATCH 3/3] KVM: VMX: make MSR bitmaps per-VCPU Paolo Bonzini
2018-02-01 1:48 ` [PATCH v3 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti Konrad Rzeszutek Wilk
2018-02-01 15:58 ` Radim Krčmář
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=20180131210924.22812-1-pbonzini@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 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®