sev: Remove false abstraction of flash encryption
commitaacdb8441376de05d9e21e93799d5a37b81f0f38
authorDavid Gibson <david@gibson.dropbear.id.au>
Tue, 12 Jan 2021 00:58:04 +0000 (12 11:58 +1100)
committerDavid Gibson <david@gibson.dropbear.id.au>
Mon, 8 Feb 2021 05:57:38 +0000 (8 16:57 +1100)
tree54a4ee4f459f74e19f139211a430b8fdfbb04eb8
parentf91f9f254ba10e94468663b23d0b780c240df268
sev: Remove false abstraction of flash encryption

When AMD's SEV memory encryption is in use, flash memory banks (which are
initialed by pc_system_flash_map()) need to be encrypted with the guest's
key, so that the guest can read them.

That's abstracted via the kvm_memcrypt_encrypt_data() callback in the KVM
state.. except, that it doesn't really abstract much at all.

For starters, the only call site is in code specific to the 'pc'
family of machine types, so it's obviously specific to those and to
x86 to begin with.  But it makes a bunch of further assumptions that
need not be true about an arbitrary confidential guest system based on
memory encryption, let alone one based on other mechanisms:

 * it assumes that the flash memory is defined to be encrypted with the
   guest key, rather than being shared with hypervisor
 * it assumes that that hypervisor has some mechanism to encrypt data into
   the guest, even though it can't decrypt it out, since that's the whole
   point
 * the interface assumes that this encrypt can be done in place, which
   implies that the hypervisor can write into a confidential guests's
   memory, even if what it writes isn't meaningful

So really, this "abstraction" is actually pretty specific to the way SEV
works.  So, this patch removes it and instead has the PC flash
initialization code call into a SEV specific callback.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
accel/kvm/kvm-all.c
accel/kvm/sev-stub.c
accel/stubs/kvm-stub.c
hw/i386/pc_sysfw.c
include/sysemu/kvm.h
include/sysemu/sev.h
target/i386/sev-stub.c
target/i386/sev.c