From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, skiboot@lists.ozlabs.org
Cc: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v2 (skiboot)] dt: add /cpus/ibm, powerpc-cpu-features device tree bindings
Date: Wed, 21 Feb 2018 14:28:41 +1100 [thread overview]
Message-ID: <87sh9vvx5i.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180216034042.7356-1-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> This is a new CPU feature advertising interface that is fine-grained,
> extensible, aware of privilege levels, and gives control of features
> to all levels of the stack (firmware, hypervisor, and OS).
>
> The design and binding specification is described in detail in doc/.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
> Since v1:
>
> - Fold branch-v3 into fixed-point-v3, as pointed out by Segher they
> are all fixed point facilities.
>
> - Fixed typo (Segher)
>
> core/Makefile.inc | 2 +-
> core/cpufeatures.c | 921 +++++++++++++++++++++
> core/device.c | 7 +
> core/init.c | 1 +
> .../ibm,powerpc-cpu-features/binding.txt | 245 ++++++
> .../ibm,powerpc-cpu-features/design.txt | 157 ++++
> include/device.h | 1 +
> include/skiboot.h | 5 +
> 8 files changed, 1338 insertions(+), 1 deletion(-)
> create mode 100644 core/cpufeatures.c
> create mode 100644 doc/device-tree/ibm,powerpc-cpu-features/binding.txt
> create mode 100644
> doc/device-tree/ibm,powerpc-cpu-features/design.txt
Merged to master as of 7f4c8e8ce0b78ca046643d7f4f63d81f4fd11746 and has
made it into -rc4
--
Stewart Smith
OPAL Architect, IBM.
prev parent reply other threads:[~2018-02-21 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 3:40 [PATCH v2 (skiboot)] dt: add /cpus/ibm, powerpc-cpu-features device tree bindings Nicholas Piggin
2018-02-21 3:28 ` Stewart Smith [this message]
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=87sh9vvx5i.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=skiboot@lists.ozlabs.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).