Re: [RFC PATCH 00/11] Secure Virtual Machine Enablement

2019-09-03 Thread Sukadev Bhattiprolu
Thiago Jung Bauermann [bauer...@linux.ibm.com] wrote: > [ Some people didn't receive all the patches in this series, even though > the linuxppc-dev list did so trying to send again. This is exactly the > same series I posted yesterday. Sorry for the clutter. ] > > This series contains

Re: [RFC PATCH 00/11] Secure Virtual Machine Enablement

2018-08-24 Thread Ram Pai
On Fri, Aug 24, 2018 at 06:33:30PM +0200, Christoph Hellwig wrote: > On Fri, Aug 24, 2018 at 01:25:24PM -0300, Thiago Jung Bauermann wrote: > > [ Some people didn't receive all the patches in this series, even though > > the linuxppc-dev list did so trying to send again. This is exactly the > >

Re: [RFC PATCH 00/11] Secure Virtual Machine Enablement

2018-08-24 Thread Christoph Hellwig
On Fri, Aug 24, 2018 at 01:25:24PM -0300, Thiago Jung Bauermann wrote: > [ Some people didn't receive all the patches in this series, even though > the linuxppc-dev list did so trying to send again. This is exactly the > same series I posted yesterday. Sorry for the clutter. ] I'm still only

[RFC PATCH 00/11] Secure Virtual Machine Enablement

2018-08-24 Thread Thiago Jung Bauermann
[ Some people didn't receive all the patches in this series, even though the linuxppc-dev list did so trying to send again. This is exactly the same series I posted yesterday. Sorry for the clutter. ] This series contains preliminary work to enable Secure Virtual Machines (SVM) on powerpc.

Re: [RFC PATCH 00/11] Secure Virtual Machine Enablement

2018-08-23 Thread Christoph Hellwig
It seems like you only sent out 6 our of the actual 11 patches according to the numbering, please resend the full series.

[RFC PATCH 00/11] Secure Virtual Machine Enablement

2018-08-23 Thread Thiago Jung Bauermann
This series contains preliminary work to enable Secure Virtual Machines (SVM) on powerpc. SVMs request to be migrated to secure memory very early in the boot process (in prom_init()), so by default all of their memory is inaccessible to the hypervisor. There is an ultravisor call that the VM can