s390: Recognize confidential-guest-support option
commit651615d92d244a6dfd7c81ab97bd3369fbe41d06
authorDavid Gibson <david@gibson.dropbear.id.au>
Thu, 23 Jul 2020 04:36:45 +0000 (23 14:36 +1000)
committerDavid Gibson <david@gibson.dropbear.id.au>
Mon, 8 Feb 2021 05:57:38 +0000 (8 16:57 +1100)
tree411fe2e3ff602f0ee3c20be0dbfaf46c1a28e866
parent9f88a7a3df11a5aaa6212ea535d40d5f92561683
s390: Recognize confidential-guest-support option

At least some s390 cpu models support "Protected Virtualization" (PV),
a mechanism to protect guests from eavesdropping by a compromised
hypervisor.

This is similar in function to other mechanisms like AMD's SEV and
POWER's PEF, which are controlled by the "confidential-guest-support"
machine option.  s390 is a slightly special case, because we already
supported PV, simply by using a CPU model with the required feature
(S390_FEAT_UNPACK).

To integrate this with the option used by other platforms, we
implement the following compromise:

 - When the confidential-guest-support option is set, s390 will
   recognize it, verify that the CPU can support PV (failing if not)
   and set virtio default options necessary for encrypted or protected
   guests, as on other platforms.  i.e. if confidential-guest-support
   is set, we will either create a guest capable of entering PV mode,
   or fail outright.

 - If confidential-guest-support is not set, guests might still be
   able to enter PV mode, if the CPU has the right model.  This may be
   a little surprising, but shouldn't actually be harmful.

To start a guest supporting Protected Virtualization using the new
option use the command line arguments:
    -object s390-pv-guest,id=pv0 -machine confidential-guest-support=pv0

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
docs/confidential-guest-support.txt
docs/system/s390x/protvirt.rst
hw/s390x/pv.c
hw/s390x/s390-virtio-ccw.c
include/hw/s390x/pv.h