From: David Gibson <david@gibson.dropbear.id.au> To: dgilbert@redhat.com, frankja@linux.ibm.com, pair@us.ibm.com, qemu-devel@nongnu.org, pbonzini@redhat.com, brijesh.singh@amd.com Cc: ehabkost@redhat.com, marcel.apfelbaum@gmail.com, "Michael S. Tsirkin" <mst@redhat.com>, qemu-ppc@nongnu.org, kvm@vger.kernel.org, pasic@linux.ibm.com, qemu-s390x@nongnu.org, "David Gibson" <david@gibson.dropbear.id.au>, "David Hildenbrand" <david@redhat.com>, "Christian Borntraeger" <borntraeger@de.ibm.com>, "Richard Henderson" <rth@twiddle.net>, "Daniel P. Berrangé" <berrange@redhat.com>, mdroth@linux.vnet.ibm.com, "Thomas Huth" <thuth@redhat.com>, "Cornelia Huck" <cohuck@redhat.com> Subject: [for-5.2 v4 00/10] Generalize memory encryption models Date: Fri, 24 Jul 2020 12:57:34 +1000 [thread overview] Message-ID: <20200724025744.69644-1-david@gibson.dropbear.id.au> (raw) A number of hardware platforms are implementing mechanisms whereby the hypervisor does not have unfettered access to guest memory, in order to mitigate the security impact of a compromised hypervisor. AMD's SEV implements this with in-cpu memory encryption, and Intel has its own memory encryption mechanism. POWER has an upcoming mechanism to accomplish this in a different way, using a new memory protection level plus a small trusted ultravisor. s390 also has a protected execution environment. The current code (committed or draft) for these features has each platform's version configured entirely differently. That doesn't seem ideal for users, or particularly for management layers. AMD SEV introduces a notionally generic machine option "machine-encryption", but it doesn't actually cover any cases other than SEV. This series is a proposal to at least partially unify configuration for these mechanisms, by renaming and generalizing AMD's "memory-encryption" property. It is replaced by a "host-trust-limitation" property pointing to a platform specific object which configures and manages the specific details. Please apply. Changes since v3: * Rebased * Added first cut at handling of s390 protected virtualization Changes since RFCv2: * Rebased * Removed preliminary SEV cleanups (they've been merged) * Changed name to "host trust limitation" * Added migration blocker to the PEF code (based on SEV's version) Changes since RFCv1: * Rebased * Fixed some errors pointed out by Dave Gilbert David Gibson (10): host trust limitation: Introduce new host trust limitation interface host trust limitation: Handle memory encryption via interface host trust limitation: Move side effect out of machine_set_memory_encryption() host trust limitation: Rework the "memory-encryption" property host trust limitation: Decouple kvm_memcrypt_*() helpers from KVM host trust limitation: Add Error ** to HostTrustLimitation::kvm_init spapr: Add PEF based host trust limitation spapr: PEF: block migration host trust limitation: Alter virtio default properties for protected guests s390: Recognize host-trust-limitation option accel/kvm/kvm-all.c | 40 ++------ accel/kvm/sev-stub.c | 7 +- accel/stubs/kvm-stub.c | 10 -- backends/Makefile.objs | 2 + backends/host-trust-limitation.c | 29 ++++++ hw/core/machine.c | 61 +++++++++-- hw/i386/pc_sysfw.c | 6 +- hw/s390x/pv.c | 61 +++++++++++ include/exec/host-trust-limitation.h | 72 +++++++++++++ include/hw/boards.h | 2 +- include/qemu/typedefs.h | 1 + include/sysemu/kvm.h | 17 --- include/sysemu/sev.h | 4 +- target/i386/sev.c | 148 ++++++++++++--------------- target/ppc/Makefile.objs | 2 +- target/ppc/pef.c | 89 ++++++++++++++++ 16 files changed, 387 insertions(+), 164 deletions(-) create mode 100644 backends/host-trust-limitation.c create mode 100644 include/exec/host-trust-limitation.h create mode 100644 target/ppc/pef.c -- 2.26.2
WARNING: multiple messages have this Message-ID (diff)
From: David Gibson <david@gibson.dropbear.id.au> To: dgilbert@redhat.com, frankja@linux.ibm.com, pair@us.ibm.com, qemu-devel@nongnu.org, pbonzini@redhat.com, brijesh.singh@amd.com Cc: "Thomas Huth" <thuth@redhat.com>, "Cornelia Huck" <cohuck@redhat.com>, "Daniel P. Berrangé" <berrange@redhat.com>, ehabkost@redhat.com, kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, "David Hildenbrand" <david@redhat.com>, mdroth@linux.vnet.ibm.com, pasic@linux.ibm.com, "Christian Borntraeger" <borntraeger@de.ibm.com>, qemu-s390x@nongnu.org, qemu-ppc@nongnu.org, "Richard Henderson" <rth@twiddle.net>, "David Gibson" <david@gibson.dropbear.id.au> Subject: [for-5.2 v4 00/10] Generalize memory encryption models Date: Fri, 24 Jul 2020 12:57:34 +1000 [thread overview] Message-ID: <20200724025744.69644-1-david@gibson.dropbear.id.au> (raw) A number of hardware platforms are implementing mechanisms whereby the hypervisor does not have unfettered access to guest memory, in order to mitigate the security impact of a compromised hypervisor. AMD's SEV implements this with in-cpu memory encryption, and Intel has its own memory encryption mechanism. POWER has an upcoming mechanism to accomplish this in a different way, using a new memory protection level plus a small trusted ultravisor. s390 also has a protected execution environment. The current code (committed or draft) for these features has each platform's version configured entirely differently. That doesn't seem ideal for users, or particularly for management layers. AMD SEV introduces a notionally generic machine option "machine-encryption", but it doesn't actually cover any cases other than SEV. This series is a proposal to at least partially unify configuration for these mechanisms, by renaming and generalizing AMD's "memory-encryption" property. It is replaced by a "host-trust-limitation" property pointing to a platform specific object which configures and manages the specific details. Please apply. Changes since v3: * Rebased * Added first cut at handling of s390 protected virtualization Changes since RFCv2: * Rebased * Removed preliminary SEV cleanups (they've been merged) * Changed name to "host trust limitation" * Added migration blocker to the PEF code (based on SEV's version) Changes since RFCv1: * Rebased * Fixed some errors pointed out by Dave Gilbert David Gibson (10): host trust limitation: Introduce new host trust limitation interface host trust limitation: Handle memory encryption via interface host trust limitation: Move side effect out of machine_set_memory_encryption() host trust limitation: Rework the "memory-encryption" property host trust limitation: Decouple kvm_memcrypt_*() helpers from KVM host trust limitation: Add Error ** to HostTrustLimitation::kvm_init spapr: Add PEF based host trust limitation spapr: PEF: block migration host trust limitation: Alter virtio default properties for protected guests s390: Recognize host-trust-limitation option accel/kvm/kvm-all.c | 40 ++------ accel/kvm/sev-stub.c | 7 +- accel/stubs/kvm-stub.c | 10 -- backends/Makefile.objs | 2 + backends/host-trust-limitation.c | 29 ++++++ hw/core/machine.c | 61 +++++++++-- hw/i386/pc_sysfw.c | 6 +- hw/s390x/pv.c | 61 +++++++++++ include/exec/host-trust-limitation.h | 72 +++++++++++++ include/hw/boards.h | 2 +- include/qemu/typedefs.h | 1 + include/sysemu/kvm.h | 17 --- include/sysemu/sev.h | 4 +- target/i386/sev.c | 148 ++++++++++++--------------- target/ppc/Makefile.objs | 2 +- target/ppc/pef.c | 89 ++++++++++++++++ 16 files changed, 387 insertions(+), 164 deletions(-) create mode 100644 backends/host-trust-limitation.c create mode 100644 include/exec/host-trust-limitation.h create mode 100644 target/ppc/pef.c -- 2.26.2
next reply other threads:[~2020-07-24 2:58 UTC|newest] Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-24 2:57 David Gibson [this message] 2020-07-24 2:57 ` [for-5.2 v4 00/10] Generalize memory encryption models David Gibson 2020-07-24 2:57 ` [for-5.2 v4 01/10] host trust limitation: Introduce new host trust limitation interface David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-24 2:57 ` [for-5.2 v4 02/10] host trust limitation: Handle memory encryption via interface David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-24 2:57 ` [for-5.2 v4 03/10] host trust limitation: Move side effect out of machine_set_memory_encryption() David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-24 2:57 ` [for-5.2 v4 04/10] host trust limitation: Rework the "memory-encryption" property David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-24 2:57 ` [for-5.2 v4 05/10] host trust limitation: Decouple kvm_memcrypt_*() helpers from KVM David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-24 2:57 ` [for-5.2 v4 06/10] host trust limitation: Add Error ** to HostTrustLimitation::kvm_init David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-24 2:57 ` [for-5.2 v4 07/10] spapr: Add PEF based host trust limitation David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-24 2:57 ` [for-5.2 v4 08/10] spapr: PEF: block migration David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-27 15:01 ` Dr. David Alan Gilbert 2020-07-27 15:01 ` Dr. David Alan Gilbert 2020-07-24 2:57 ` [for-5.2 v4 09/10] host trust limitation: Alter virtio default properties for protected guests David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-27 15:05 ` Dr. David Alan Gilbert 2020-07-27 15:05 ` Dr. David Alan Gilbert 2020-08-13 7:43 ` Greg Kurz 2020-08-13 7:43 ` Greg Kurz 2020-08-13 8:19 ` Greg Kurz 2020-08-13 8:19 ` Greg Kurz 2020-09-07 15:10 ` Halil Pasic 2020-09-07 15:10 ` Halil Pasic 2020-09-11 2:04 ` David Gibson 2020-09-11 2:04 ` David Gibson 2020-09-11 13:49 ` Halil Pasic 2020-09-11 13:49 ` Halil Pasic 2020-07-24 2:57 ` [for-5.2 v4 10/10] s390: Recognize host-trust-limitation option David Gibson 2020-07-24 2:57 ` David Gibson 2020-07-27 15:50 ` Cornelia Huck 2020-07-27 15:50 ` Cornelia Huck 2020-08-03 7:40 ` Janosch Frank 2020-08-03 7:40 ` Janosch Frank 2020-08-06 6:14 ` David Gibson 2020-08-06 6:14 ` David Gibson 2020-08-06 7:18 ` David Hildenbrand 2020-08-06 7:18 ` David Hildenbrand 2020-08-03 7:49 ` Janosch Frank 2020-08-03 7:49 ` Janosch Frank 2020-08-03 7:54 ` David Gibson 2020-08-03 7:54 ` David Gibson 2020-08-03 8:07 ` Janosch Frank 2020-08-03 8:07 ` Janosch Frank 2020-08-03 8:14 ` David Gibson 2020-08-03 8:14 ` David Gibson 2020-08-03 8:33 ` Cornelia Huck 2020-08-03 8:33 ` Cornelia Huck 2020-09-07 15:22 ` Halil Pasic 2020-09-07 15:22 ` Halil Pasic 2020-09-10 11:36 ` Cornelia Huck 2020-09-10 11:36 ` Cornelia Huck 2020-09-10 18:29 ` Halil Pasic 2020-09-10 18:29 ` Halil Pasic 2020-09-11 0:07 ` David Gibson 2020-09-11 0:07 ` David Gibson 2020-09-11 6:25 ` Greg Kurz 2020-09-11 6:25 ` Greg Kurz 2020-09-11 12:45 ` Halil Pasic 2020-09-11 12:45 ` Halil Pasic
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=20200724025744.69644-1-david@gibson.dropbear.id.au \ --to=david@gibson.dropbear.id.au \ --cc=berrange@redhat.com \ --cc=borntraeger@de.ibm.com \ --cc=brijesh.singh@amd.com \ --cc=cohuck@redhat.com \ --cc=david@redhat.com \ --cc=dgilbert@redhat.com \ --cc=ehabkost@redhat.com \ --cc=frankja@linux.ibm.com \ --cc=kvm@vger.kernel.org \ --cc=marcel.apfelbaum@gmail.com \ --cc=mdroth@linux.vnet.ibm.com \ --cc=mst@redhat.com \ --cc=pair@us.ibm.com \ --cc=pasic@linux.ibm.com \ --cc=pbonzini@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=qemu-ppc@nongnu.org \ --cc=qemu-s390x@nongnu.org \ --cc=rth@twiddle.net \ --cc=thuth@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: linkBe 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.