From: Ashish Kalra <Ashish.Kalra@amd.com>
To: pbonzini@redhat.com
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
rkrcmar@redhat.com, joro@8bytes.org, bp@suse.de,
thomas.lendacky@amd.com, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, srutherford@google.com,
brijesh.singh@amd.com, dovmurik@linux.vnet.ibm.com,
tobin@ibm.com, jejb@linux.ibm.com, frankeh@us.ibm.com,
dgilbert@redhat.com
Subject: [PATCH 0/9] Add AMD SEV page encryption bitmap support.
Date: Mon, 30 Nov 2020 23:30:50 +0000 [thread overview]
Message-ID: <cover.1606633738.git.ashish.kalra@amd.com> (raw)
From: Ashish Kalra <ashish.kalra@amd.com>
The series add support for AMD SEV page encryption bitmap.
SEV guest VMs have the concept of private and shared memory. Private memory
is encrypted with the guest-specific key, while shared memory may be encrypted
with hypervisor key. The patch series introduces a new hypercall.
The guest OS can use this hypercall to notify the page encryption status.
The patch adds new ioctls KVM_{SET,GET}_PAGE_ENC_BITMAP. The ioctl can be used
by qemu to get the page encryption bitmap. Qemu can consult this bitmap
during guest live migration / page migration and/or guest debugging to know
whether the page is encrypted.
The page encryption bitmap support is required for SEV guest live migration,
guest page migration and guest debugging.
The patch-set also adds support for bypassing unencrypted guest memory
regions for DBG_DECRYPT API calls, guest memory region encryption status
in sev_dbg_decrypt() is now referenced using the page encryption bitmap.
A branch containing these patches is available here:
https://github.com/AMDESE/linux/tree/sev-page-encryption-bitmap-v1
Ashish Kalra (4):
KVM: SVM: Add support for static allocation of unified Page Encryption
Bitmap.
KVM: x86: Mark _bss_decrypted section variables as decrypted in page
encryption bitmap.
KVM: x86: Add kexec support for SEV page encryption bitmap.
KVM: SVM: Bypass DBG_DECRYPT API calls for unecrypted guest memory.
Brijesh Singh (5):
KVM: x86: Add AMD SEV specific Hypercall3
KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall
KVM: x86: Introduce KVM_GET_PAGE_ENC_BITMAP ioctl
mm: x86: Invoke hypercall when page encryption status is changed.
KVM: x86: Introduce KVM_SET_PAGE_ENC_BITMAP ioctl
Documentation/virt/kvm/api.rst | 71 ++++++
Documentation/virt/kvm/hypercalls.rst | 15 ++
arch/x86/include/asm/kvm_host.h | 7 +
arch/x86/include/asm/kvm_para.h | 12 +
arch/x86/include/asm/mem_encrypt.h | 4 +
arch/x86/include/asm/paravirt.h | 10 +
arch/x86/include/asm/paravirt_types.h | 2 +
arch/x86/kernel/kvm.c | 28 +++
arch/x86/kernel/kvmclock.c | 12 +
arch/x86/kernel/paravirt.c | 1 +
arch/x86/kvm/svm/sev.c | 319 ++++++++++++++++++++++++++
arch/x86/kvm/svm/svm.c | 5 +
arch/x86/kvm/svm/svm.h | 7 +
arch/x86/kvm/vmx/vmx.c | 1 +
arch/x86/kvm/x86.c | 35 +++
arch/x86/mm/mem_encrypt.c | 63 ++++-
arch/x86/mm/pat/set_memory.c | 7 +
include/uapi/linux/kvm.h | 13 ++
include/uapi/linux/kvm_para.h | 1 +
19 files changed, 612 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2020-11-30 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 23:30 Ashish Kalra [this message]
2020-11-30 23:31 ` [PATCH 1/9] KVM: x86: Add AMD SEV specific Hypercall3 Ashish Kalra
2020-11-30 23:32 ` [PATCH 2/9] KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall Ashish Kalra
2020-11-30 23:32 ` [PATCH 3/9] KVM: x86: Introduce KVM_GET_PAGE_ENC_BITMAP ioctl Ashish Kalra
2020-11-30 23:32 ` [PATCH 4/9] mm: x86: Invoke hypercall when page encryption status is changed Ashish Kalra
2020-11-30 23:32 ` [PATCH 5/9] KVM: x86: Introduce KVM_SET_PAGE_ENC_BITMAP ioctl Ashish Kalra
2020-11-30 23:33 ` [PATCH 6/9] KVM: SVM: Add support for static allocation of unified Page Encryption Bitmap Ashish Kalra
2020-11-30 23:33 ` [PATCH 7/9] KVM: x86: Mark _bss_decrypted section variables as decrypted in page encryption bitmap Ashish Kalra
2020-11-30 23:33 ` [PATCH 8/9] KVM: x86: Add kexec support for SEV " Ashish Kalra
2020-11-30 23:34 ` [PATCH 9/9] KVM: SVM: Bypass DBG_DECRYPT API calls for unecrypted guest memory Ashish Kalra
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=cover.1606633738.git.ashish.kalra@amd.com \
--to=ashish.kalra@amd.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=dgilbert@redhat.com \
--cc=dovmurik@linux.vnet.ibm.com \
--cc=frankeh@us.ibm.com \
--cc=hpa@zytor.com \
--cc=jejb@linux.ibm.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=srutherford@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tobin@ibm.com \
--cc=x86@kernel.org \
/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