Re: [for-6.0 v5 08/13] securable guest memory: Introduce sgm "ready" flag

2020-12-17 Thread Cornelia Huck
On Thu, 17 Dec 2020 16:38:20 +1100 David Gibson wrote: > On Mon, Dec 14, 2020 at 06:00:36PM +0100, Cornelia Huck wrote: > > On Fri, 4 Dec 2020 16:44:10 +1100 > > David Gibson wrote: > > > > > The platform specific details of mechanisms for implementing securable > > > guest memory may

Re: [for-6.0 v5 08/13] securable guest memory: Introduce sgm "ready" flag

2020-12-16 Thread David Gibson
On Mon, Dec 14, 2020 at 06:00:36PM +0100, Cornelia Huck wrote: > On Fri, 4 Dec 2020 16:44:10 +1100 > David Gibson wrote: > > > The platform specific details of mechanisms for implementing securable > > guest memory may require setup at various points during initialization. > > Thus, it's not

Re: [for-6.0 v5 08/13] securable guest memory: Introduce sgm "ready" flag

2020-12-14 Thread Cornelia Huck
On Fri, 4 Dec 2020 16:44:10 +1100 David Gibson wrote: > The platform specific details of mechanisms for implementing securable > guest memory may require setup at various points during initialization. > Thus, it's not really feasible to have a single sgm initialization hook, > but instead each

[for-6.0 v5 08/13] securable guest memory: Introduce sgm "ready" flag

2020-12-03 Thread David Gibson
The platform specific details of mechanisms for implementing securable guest memory may require setup at various points during initialization. Thus, it's not really feasible to have a single sgm initialization hook, but instead each mechanism needs its own initialization calls in arch or machine