linux-toolchains.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	"H.J. Lu" <hjl.tools@gmail.com>,
	llvm@lists.linux.dev, linux-toolchains@vger.kernel.org,
	Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH] x86: Use -mindirect-branch-cs-prefix for RETPOLINE builds
Date: Fri, 19 Nov 2021 16:11:25 +0100	[thread overview]
Message-ID: <YZe+nfVmA5wrIcv6@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKwvOdkrN0tLMrEyx98JY6wGdwi0Be3Z8fbTQ3vNHckM4dmG8g@mail.gmail.com>

On Thu, Nov 18, 2021 at 02:08:04PM -0800, Nick Desaulniers wrote:
> On Thu, Nov 18, 2021 at 10:54 AM Peter Zijlstra <peterz@infradead.org> wrote:
> >
> >
> > In order to further enable commit:
> >
> >   bbe2df3f6b6d ("x86/alternative: Try inline spectre_v2=retpoline,amd")
> >
> > add the new GCC flag -mindirect-branch-cs-prefix:
> >
> >   https://gcc.gnu.org/g:2196a681d7810ad8b227bf983f38ba716620545e
> >
> > to RETPOLINE=y builds. This should allow fully inlining retpoline,amd
> > for GCC builds.
> 
> Do you mind adding the following link tags:
> 
> Link: https://gcc.gnu.org/g:2196a681d7810ad8b227bf983f38ba716620545e
> Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102952
> Link: https://bugs.llvm.org/show_bug.cgi?id=52323

My scripts will strip that, they only like to have a Link to to the
actual email as posted. I can put in the URLs, the first is already in
the Changelog.

> If the feature would be helpful to implement in Clang, would you mind
> keeping the cc-option, but moving the check outside of the `ifdef
> CONFIG_CC_IS_GCC` block? That way, we don't need to revisit the
> Makefile?

I was thinking that clang would want to name it differently to be
consistent with their own retpoline flags, something like:

  -mretpoline-cs-prefix

> (Tangential: I wonder why RETPOLINE_CFLAGS aren't defined in
> arch/x86/Makefile; they seem to be x86 specific at the moment).

Yeah, I think there was hoping that other archs would find it useful,
but so far x86 is the only one having grown them things. I can move them
I suppose. If ever another arch grows them we can reconsider.

> With the above link tags, and with or without moving this outside the
> gcc-specific guard:
> Acked-by: Nick Desaulniers <ndesaulniers@google.com>

Thanks, let me repost as two patches.

      reply	other threads:[~2021-11-19 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211118185421.GK174703@worktop.programming.kicks-ass.net>
2021-11-18 22:08 ` [PATCH] x86: Use -mindirect-branch-cs-prefix for RETPOLINE builds Nick Desaulniers
2021-11-19 15:11   ` Peter Zijlstra [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=YZe+nfVmA5wrIcv6@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=hjl.tools@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-toolchains@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=x86@kernel.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).