From: Nicholas Piggin <npiggin@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] powerpc/64s: Add dt_cpu_ftrs boot time setup option
Date: Tue, 30 May 2017 17:22:42 +1000 [thread overview]
Message-ID: <20170530172242.251c9b9d@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <1496125689-27900-1-git-send-email-mpe@ellerman.id.au>
On Tue, 30 May 2017 16:28:09 +1000
Michael Ellerman <mpe@ellerman.id.au> wrote:
> From: Nicholas Piggin <npiggin@gmail.com>
>
> Provide a dt_cpu_ftrs= cmdline option to disable the dt_cpu_ftrs CPU
> feature discovery, and fall back to the "cputable" based version.
>
> Also allow control of advertising unknown features to userspace and
> with this parameter, and remove the clunky CONFIG option.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> [mpe: Add explicit early check of bootargs in dt_cpu_ftrs_init()]
Thanks for fixing that up. The patch is more yours than mine now :P
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -866,6 +866,16 @@
>
> dscc4.setup= [NET]
>
> + dt_cpu_ftrs= [PPC]
> + Format: {"off" | "known"}
> + Control how the dt_cpu_ftrs device-tree binding is
> + used for CPU feature discovery and setup (if it
> + exists).
> + off: Do not use it, fall back to legacy cpu table.
> + known: Do not pass through unknown features to guests
> + or userspace, only those that the kernel is not aware
> + of.
Well that's not the right number of nots. Better make it:
+ known: Do not pass through unknown features to guests
+ or userspace, only those that the kernel is not not
+ aware of.
next prev parent reply other threads:[~2017-05-30 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 6:28 [PATCH v2] powerpc/64s: Add dt_cpu_ftrs boot time setup option Michael Ellerman
2017-05-30 7:22 ` Nicholas Piggin [this message]
2017-06-01 10:04 ` Michael Ellerman
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=20170530172242.251c9b9d@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).