On Thu, Apr 16, 2020 at 06:27:15PM +0200, Laurent Dufour wrote:
> The newly introduced ibm,secure-memory nodes supersede the
> ibm,uv-firmware's property secure-memory-ranges.
>
> Firmware will no more expose the secure-memory-ranges property so first
> read the new one and if not found rollback t
Paul, could you please take that patch?
Le 16/04/2020 à 18:27, Laurent Dufour a écrit :
The newly introduced ibm,secure-memory nodes supersede the
ibm,uv-firmware's property secure-memory-ranges.
Firmware will no more expose the secure-memory-ranges property so first
read the new one and if not
Le 21/04/2020 à 15:43, Oliver O'Halloran a écrit :
On Tue, Apr 21, 2020 at 11:37 PM Michael Ellerman wrote:
Hi Laurent,
Laurent Dufour writes:
The newly introduced ibm,secure-memory nodes supersede the
ibm,uv-firmware's property secure-memory-ranges.
Is either documented in a device tree
On Tue, Apr 21, 2020 at 11:37 PM Michael Ellerman wrote:
>
> Hi Laurent,
>
> Laurent Dufour writes:
> > The newly introduced ibm,secure-memory nodes supersede the
> > ibm,uv-firmware's property secure-memory-ranges.
>
> Is either documented in a device tree binding document anywhere?
>
> cheers
>
Hi Laurent,
Laurent Dufour writes:
> The newly introduced ibm,secure-memory nodes supersede the
> ibm,uv-firmware's property secure-memory-ranges.
Is either documented in a device tree binding document anywhere?
cheers
> Firmware will no more expose the secure-memory-ranges property so first
>
The newly introduced ibm,secure-memory nodes supersede the
ibm,uv-firmware's property secure-memory-ranges.
Firmware will no more expose the secure-memory-ranges property so first
read the new one and if not found rollback to the older one.
Signed-off-by: Laurent Dufour
---
arch/powerpc/kvm/boo