From: Paolo Bonzini <pbonzini@redhat.com>
To: David Matlack <dmatlack@google.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jmattson@google.com, rkrcmar@redhat.com
Subject: Re: [PATCH v3 0/5] VMX Capability MSRs
Date: Wed, 30 Nov 2016 12:22:00 +0100 [thread overview]
Message-ID: <7aad1d11-ef44-9d11-e7b5-c46f84aac5e5@redhat.com> (raw)
In-Reply-To: <1480472050-58023-1-git-send-email-dmatlack@google.com>
On 30/11/2016 03:14, David Matlack wrote:
> This patchset adds support setting the VMX capability MSRs from userspace.
> This is required for migration of nested-capable VMs to different CPUs and
> KVM versions.
>
> Patch 1 generates the non-true VMX MSRs using the true MSRs, which allows
> userspace to skip restoring them.
>
> Patch 2 adds support for restoring the VMX capability MSRs.
>
> Patches 3 and 4 make KVM's emulation of MSR_IA32_VMX_CR{0,4}_FIXED1 more
> accurate.
>
> Patch 5 fixes a bug in emulated VM-entry that came up when testing patches
> 3 and 4.
>
> Changes since v2:
> * Generate CR0_FIXED1 in addition to CR4_FIXED1
> * Generate "non-true" capability MSRs from the "true" versions and remove
> "non-true" MSRs from struct nested_vmx.
> * Disallow restore of CR{0,4}_FIXED1 and "non-true" MSRs since they are
> generated.
>
> Changes since v1:
> * Support restoring less-capable versions of MSR_IA32_VMX_BASIC,
> MSR_IA32_VMX_CR{0,4}_FIXED{0,1}.
> * Include VMX_INS_OUTS in MSR_IA32_VMX_BASIC initial value.
>
> David Matlack (5):
> KVM: nVMX: generate non-true VMX MSRs based on true versions
> KVM: nVMX: support restore of VMX capability MSRs
> KVM: nVMX: fix checks on CR{0,4} during virtual VMX operation
> KVM: nVMX: generate MSR_IA32_CR{0,4}_FIXED1 from guest CPUID
> KVM: nVMX: load GUEST_EFER after GUEST_CR0 during emulated VM-entry
>
> arch/x86/include/asm/vmx.h | 31 +++
> arch/x86/kvm/vmx.c | 479 +++++++++++++++++++++++++++++++++++++--------
> 2 files changed, 427 insertions(+), 83 deletions(-)
Just a small nit that can be fixed on applying. Thanks!
Paolo
next prev parent reply other threads:[~2016-11-30 11:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 2:14 David Matlack
2016-11-30 2:14 ` [PATCH v3 1/5] KVM: nVMX: generate non-true VMX MSRs based on true versions David Matlack
2016-11-30 11:16 ` Paolo Bonzini
2016-11-30 18:05 ` David Matlack
2016-11-30 20:45 ` Paolo Bonzini
2016-11-30 2:14 ` [PATCH v3 2/5] KVM: nVMX: support restore of VMX capability MSRs David Matlack
2016-11-30 2:14 ` [PATCH v3 3/5] KVM: nVMX: fix checks on CR{0,4} during virtual VMX operation David Matlack
2016-11-30 21:52 ` Radim Krčmář
2016-11-30 22:33 ` Paolo Bonzini
2016-11-30 23:53 ` David Matlack
2016-12-01 13:21 ` Radim Krčmář
2016-11-30 2:14 ` [PATCH v3 4/5] KVM: nVMX: generate MSR_IA32_CR{0,4}_FIXED1 from guest CPUID David Matlack
2016-11-30 2:14 ` [PATCH v3 5/5] KVM: nVMX: load GUEST_EFER after GUEST_CR0 during emulated VM-entry David Matlack
2016-11-30 11:22 ` Paolo Bonzini [this message]
2016-11-30 18:05 ` [PATCH v3 0/5] VMX Capability MSRs David Matlack
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=7aad1d11-ef44-9d11-e7b5-c46f84aac5e5@redhat.com \
--to=pbonzini@redhat.com \
--cc=dmatlack@google.com \
--cc=jmattson@google.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®