Re: [RFC v2 11/18] guest memory protection: Handle memory encrption via interface

2020-06-03 Thread David Gibson
On Mon, May 25, 2020 at 12:26:55PM +0200, Greg Kurz wrote: > > s/encrption/encryption Fixed. > On Thu, 21 May 2020 13:42:57 +1000 > David Gibson wrote: > > > At the moment AMD SEV sets a special function pointer, plus an opaque > > handle in KVMState to let things know how to encrypt guest mem

Re: [RFC v2 11/18] guest memory protection: Handle memory encrption via interface

2020-06-01 Thread Richard Henderson
On 5/20/20 8:42 PM, David Gibson wrote: > At the moment AMD SEV sets a special function pointer, plus an opaque > handle in KVMState to let things know how to encrypt guest memory. > > Now that we have a QOM interface for handling things related to guest > memory protection, use a QOM method on th

Re: [RFC v2 11/18] guest memory protection: Handle memory encrption via interface

2020-05-25 Thread Greg Kurz
s/encrption/encryption On Thu, 21 May 2020 13:42:57 +1000 David Gibson wrote: > At the moment AMD SEV sets a special function pointer, plus an opaque > handle in KVMState to let things know how to encrypt guest memory. > > Now that we have a QOM interface for handling things related to guest

[RFC v2 11/18] guest memory protection: Handle memory encrption via interface

2020-05-20 Thread David Gibson
At the moment AMD SEV sets a special function pointer, plus an opaque handle in KVMState to let things know how to encrypt guest memory. Now that we have a QOM interface for handling things related to guest memory protection, use a QOM method on that interface, rather than a bare function pointer