Re: [for-6.0 v5 00/13] Generalize memory encryption models

2021-01-11 Thread David Gibson
On Fri, Dec 04, 2020 at 09:50:05AM +, Daniel P. Berrangé wrote: > On Fri, Dec 04, 2020 at 04:44:02PM +1100, David Gibson wrote: > > A number of hardware platforms are implementing mechanisms whereby the > > hypervisor does not have unfettered access to guest memory, in order > > to mitigate the

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-17 Thread Cornelia Huck
On Thu, 17 Dec 2020 17:21:16 +1100 David Gibson wrote: > On Tue, Dec 08, 2020 at 01:43:08PM +0100, Cornelia Huck wrote: > > On Tue, 8 Dec 2020 13:57:28 +1100 > > David Gibson wrote: > > > > > On Fri, Dec 04, 2020 at 02:12:29PM +0100, Cornelia Huck wrote: > > > > On Fri, 4 Dec 2020 13:07:27

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-16 Thread David Gibson
On Tue, Dec 08, 2020 at 01:43:08PM +0100, Cornelia Huck wrote: > On Tue, 8 Dec 2020 13:57:28 +1100 > David Gibson wrote: > > > On Fri, Dec 04, 2020 at 02:12:29PM +0100, Cornelia Huck wrote: > > > On Fri, 4 Dec 2020 13:07:27 + > > > "Dr. David Alan Gilbert" wrote: > > > > > > > * Cornelia

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-08 Thread Cornelia Huck
On Tue, 8 Dec 2020 13:57:28 +1100 David Gibson wrote: > On Fri, Dec 04, 2020 at 02:12:29PM +0100, Cornelia Huck wrote: > > On Fri, 4 Dec 2020 13:07:27 + > > "Dr. David Alan Gilbert" wrote: > > > > > * Cornelia Huck (coh...@redhat.com) wrote: > > > > On Fri, 4 Dec 2020 09:06:50 +0100 > >

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-07 Thread David Gibson
On Fri, Dec 04, 2020 at 02:12:29PM +0100, Cornelia Huck wrote: > On Fri, 4 Dec 2020 13:07:27 + > "Dr. David Alan Gilbert" wrote: > > > * Cornelia Huck (coh...@redhat.com) wrote: > > > On Fri, 4 Dec 2020 09:06:50 +0100 > > > Christian Borntraeger wrote: > > > > > > > On 04.12.20 06:44, Dav

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-07 Thread David Gibson
On Fri, Dec 04, 2020 at 02:02:05PM +0100, Cornelia Huck wrote: > On Fri, 4 Dec 2020 09:06:50 +0100 > Christian Borntraeger wrote: > > > On 04.12.20 06:44, David Gibson wrote: > > > A number of hardware platforms are implementing mechanisms whereby the > > > hypervisor does not have unfettered acc

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-04 Thread Halil Pasic
On Fri, 4 Dec 2020 13:25:00 + Daniel P. Berrangé wrote: > On Fri, Dec 04, 2020 at 01:07:27PM +, Dr. David Alan Gilbert wrote: > > * Cornelia Huck (coh...@redhat.com) wrote: > > > On Fri, 4 Dec 2020 09:06:50 +0100 > > > Christian Borntraeger wrote: > > > > > > > On 04.12.20 06:44, David

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-04 Thread Daniel P . Berrangé
On Fri, Dec 04, 2020 at 01:07:27PM +, Dr. David Alan Gilbert wrote: > * Cornelia Huck (coh...@redhat.com) wrote: > > On Fri, 4 Dec 2020 09:06:50 +0100 > > Christian Borntraeger wrote: > > > > > On 04.12.20 06:44, David Gibson wrote: > > > > A number of hardware platforms are implementing mech

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-04 Thread Cornelia Huck
On Fri, 4 Dec 2020 13:07:27 + "Dr. David Alan Gilbert" wrote: > * Cornelia Huck (coh...@redhat.com) wrote: > > On Fri, 4 Dec 2020 09:06:50 +0100 > > Christian Borntraeger wrote: > > > > > On 04.12.20 06:44, David Gibson wrote: > > > > A number of hardware platforms are implementing mech

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-04 Thread Dr. David Alan Gilbert
* Cornelia Huck (coh...@redhat.com) wrote: > On Fri, 4 Dec 2020 09:06:50 +0100 > Christian Borntraeger wrote: > > > On 04.12.20 06:44, David Gibson wrote: > > > A number of hardware platforms are implementing mechanisms whereby the > > > hypervisor does not have unfettered access to guest memory,

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-04 Thread Cornelia Huck
On Fri, 4 Dec 2020 09:06:50 +0100 Christian Borntraeger wrote: > On 04.12.20 06:44, David Gibson wrote: > > A number of hardware platforms are implementing mechanisms whereby the > > hypervisor does not have unfettered access to guest memory, in order > > to mitigate the security impact of a comp

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-04 Thread Daniel P . Berrangé
On Fri, Dec 04, 2020 at 04:44:02PM +1100, David Gibson wrote: > A number of hardware platforms are implementing mechanisms whereby the > hypervisor does not have unfettered access to guest memory, in order > to mitigate the security impact of a compromised hypervisor. > > AMD's SEV implements this

Re: [for-6.0 v5 00/13] Generalize memory encryption models

2020-12-04 Thread Christian Borntraeger
On 04.12.20 06:44, David Gibson wrote: > A number of hardware platforms are implementing mechanisms whereby the > hypervisor does not have unfettered access to guest memory, in order > to mitigate the security impact of a compromised hypervisor. > > AMD's SEV implements this with in-cpu memory

[for-6.0 v5 00/13] Generalize memory encryption models

2020-12-03 Thread David Gibson
A number of hardware platforms are implementing mechanisms whereby the hypervisor does not have unfettered access to guest memory, in order to mitigate the security impact of a compromised hypervisor. AMD's SEV implements this with in-cpu memory encryption, and Intel has its own memory encryption