From: Laurent Dufour <ldufour@linux.ibm.com>
To: "Oliver O'Halloran" <oohall@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: kvm-ppc@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Paul Mackerras <paulus@samba.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: PPC: Book3S HV: read ibm,secure-memory nodes
Date: Tue, 21 Apr 2020 19:39:31 +0200 [thread overview]
Message-ID: <db211c9c-3e6c-761c-8c9f-4110d3c0fcbe@linux.ibm.com> (raw)
In-Reply-To: <CAOSf1CF2YEG1U_1XP_Vvk3Bn1RCiNa1DAKEbemWu00JimoPsUQ@mail.gmail.com>
Le 21/04/2020 à 15:43, Oliver O'Halloran a écrit :
> On Tue, Apr 21, 2020 at 11:37 PM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> Hi Laurent,
>>
>> Laurent Dufour <ldufour@linux.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.
Thanks Oliver for this pointer.
Yes this is an RFC but this documentation details the secure memory nodes
created by skiboot and parsed by this patch.
Michael, is that enough for you?
Laurent.
next prev parent reply other threads:[~2020-04-21 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 16:27 [PATCH] KVM: PPC: Book3S HV: read ibm,secure-memory nodes Laurent Dufour
2020-04-21 13:34 ` Michael Ellerman
2020-04-21 13:43 ` Oliver O'Halloran
2020-04-21 17:39 ` Laurent Dufour [this message]
2020-05-26 17:51 ` Laurent Dufour
2020-05-27 4:16 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db211c9c-3e6c-761c-8c9f-4110d3c0fcbe@linux.ibm.com \
--to=ldufour@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).