From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: srutherford@google.com, seanjc@google.com, joro@8bytes.org,
brijesh.singh@amd.com, thomas.lendacky@amd.com,
ashish.kalra@amd.com
Subject: [PATCH v3 0/2] KVM: x86: guest interface for SEV live migration
Date: Thu, 29 Apr 2021 06:47:05 -0400 [thread overview]
Message-ID: <20210429104707.203055-1-pbonzini@redhat.com> (raw)
This is a reviewed version of the guest interface (hypercall+MSR)
for SEV live migration. The differences lie mostly in the API
for userspace. In particular:
- the CPUID feature is not exposed in KVM_GET_SUPPORTED_CPUID
- the hypercall must be enabled manually with KVM_ENABLE_CAP
- the MSR has sensible behavior if not filtered
Compared to v2, the KVM-provided behavior of the MSR is different:
it is set to 0 if the guest memory is encrypted, and 1 if it is not.
The idea is that the MSR is read-only if KVM_FEATURE_HC_PAGE_ENC_STATUS
is not exposed to the guest (it should only be exposed if the guest has
encrypted memory), but it also has a sensible value for non-encrypted
guests. QEMU could however expose a "0" value for the special "-cpu
host,migratable=no" mode if it wanted.
Because of this new behavior, the CPUID bit are split.
Paolo
Ashish Kalra (1):
KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall
Paolo Bonzini (1):
KVM: x86: add MSR_KVM_MIGRATION_CONTROL
Documentation/virt/kvm/api.rst | 14 +++++++
Documentation/virt/kvm/cpuid.rst | 9 +++++
Documentation/virt/kvm/hypercalls.rst | 21 ++++++++++
Documentation/virt/kvm/msr.rst | 14 +++++++
arch/x86/include/asm/kvm-x86-ops.h | 1 +
arch/x86/include/asm/kvm_host.h | 3 ++
arch/x86/include/uapi/asm/kvm_para.h | 5 +++
arch/x86/kvm/cpuid.c | 3 +-
arch/x86/kvm/svm/svm.c | 1 +
arch/x86/kvm/vmx/vmx.c | 7 ++++
arch/x86/kvm/x86.c | 56 +++++++++++++++++++++++++++
include/uapi/linux/kvm.h | 1 +
include/uapi/linux/kvm_para.h | 1 +
13 files changed, 135 insertions(+), 1 deletion(-)
--
2.26.2
next reply other threads:[~2021-04-29 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:47 Paolo Bonzini [this message]
2021-04-29 10:47 ` [PATCH v3 1/2] KVM: x86: add MSR_KVM_MIGRATION_CONTROL Paolo Bonzini
2021-04-29 10:47 ` [PATCH v3 2/2] KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall Paolo Bonzini
2021-04-30 20:10 ` Sean Christopherson
2021-05-01 9:01 ` Paolo Bonzini
2021-05-03 23:22 ` Steve Rutherford
2021-05-04 8:06 ` Paolo Bonzini
2021-05-04 17:09 ` Sean Christopherson
2021-05-04 20:27 ` Paolo Bonzini
2021-05-04 20:33 ` Sean Christopherson
2021-05-04 20:56 ` Paolo Bonzini
2021-05-04 21:16 ` Steve Rutherford
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=20210429104707.203055-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=ashish.kalra@amd.com \
--cc=brijesh.singh@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=srutherford@google.com \
--cc=thomas.lendacky@amd.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;
as well as URLs for NNTP newsgroup(s).