[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOSf1CF2YEG1U_1XP_Vvk3Bn1RCiNa1DAKEbemWu00JimoPsUQ@mail.gmail.com>
Date: Tue, 21 Apr 2020 23:43:56 +1000
From: "Oliver O'Halloran" <oohall@...il.com>
To: Michael Ellerman <mpe@...erman.id.au>
Cc: Laurent Dufour <ldufour@...ux.ibm.com>, kvm-ppc@...r.kernel.org,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Alexey Kardashevskiy <aik@...abs.ru>,
Paul Mackerras <paulus@...ba.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] KVM: PPC: Book3S HV: read ibm,secure-memory nodes
On Tue, Apr 21, 2020 at 11:37 PM Michael Ellerman <mpe@...erman.id.au> wrote:
>
> Hi Laurent,
>
> Laurent Dufour <ldufour@...ux.ibm.com> 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
> > read the new one and if not found rollback to the older one.
There's some in Ryan's UV support series for skiboot:
https://patchwork.ozlabs.org/project/skiboot/patch/20200227204023.22125-2-grimm@linux.ibm.com/
...which is also marked RFC. Cool.
Oliver
Powered by blists - more mailing lists