Re: [for-6.0 v5 03/13] securable guest memory: Handle memory encryption via interface

2021-01-11 Thread David Gibson
On Fri, Dec 04, 2020 at 02:10:05PM +0100, Cornelia Huck wrote: > On Fri, 4 Dec 2020 16:44:05 +1100 > 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

Re: [for-6.0 v5 03/13] securable guest memory: Handle memory encryption via interface

2021-01-07 Thread David Gibson
On Fri, Dec 04, 2020 at 02:10:05PM +0100, Cornelia Huck wrote: > On Fri, 4 Dec 2020 16:44:05 +1100 > 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

Re: [for-6.0 v5 03/13] securable guest memory: Handle memory encryption via interface

2020-12-04 Thread Cornelia Huck
On Fri, 4 Dec 2020 16:44:05 +1100 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 securable > guest memory, use a

[for-6.0 v5 03/13] securable guest memory: Handle memory encryption via interface

2020-12-03 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 securable guest memory, use a QOM method on that interface, rather than a bare function pointer f