From: Scott Wood <oss@buserror.net>
To: Diana Madalina Craciun <diana.craciun@nxp.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: Leo Li <leoyang.li@nxp.com>
Subject: Re: [RFC PATCH] powerpc/fsl: Add barrier_nospec implementation for NXP PowerPC Book E
Date: Thu, 31 May 2018 17:03:35 -0500 [thread overview]
Message-ID: <1527804215.30674.35.camel@buserror.net> (raw)
In-Reply-To: <VI1PR0401MB2463C17743BC5C25C2152631FF630@VI1PR0401MB2463.eurprd04.prod.outlook.com>
On Thu, 2018-05-31 at 14:35 +0000, Diana Madalina Craciun wrote:
> On 5/31/2018 5:21 PM, Michael Ellerman wrote:
> >
> > We can add a nospectre_v1 command line option if necessary.
>
> What about nobarrier_nospec (or similar) instead of nospectre_v1 command
> line? We are not disabling all the v1 mitigations, the masking part will
> remain unchanged.
I think nospectre_v1 makes more sense as it's about the user's intentions
rather than the implementation. The user is giving the kernel permission to
not defend against spectre v1, and it's up to the implementation which
mitigations (if any) to disable in response to that, same as any other
optimization.
-Scott
next prev parent reply other threads:[~2018-05-31 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1526973031-9543-1-git-send-email-diana.craciun@nxp.com>
2018-05-22 20:29 ` [RFC PATCH] powerpc/fsl: Add barrier_nospec implementation for NXP PowerPC Book E Scott Wood
2018-05-29 15:22 ` Diana Madalina Craciun
2018-05-29 19:14 ` Scott Wood
2018-05-30 15:09 ` Diana Madalina Craciun
2018-05-31 14:21 ` Michael Ellerman
2018-05-31 14:35 ` Diana Madalina Craciun
2018-05-31 22:03 ` Scott Wood [this message]
2018-06-01 10:40 ` Michael Ellerman
2018-06-01 14:58 ` Diana Madalina Craciun
2018-05-23 8:56 ` [RESEND RFC " Diana Craciun
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=1527804215.30674.35.camel@buserror.net \
--to=oss@buserror.net \
--cc=diana.craciun@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linuxppc-dev@lists.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).