From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, pjt@google.com, mbenes@suze.cz, jgross@suse.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 6/6] objtool,x86: Rewrite retpoline thunk calls
Date: Fri, 19 Feb 2021 15:55:30 -0600 [thread overview]
Message-ID: <20210219215530.ivzzv3oavhuip6un@treble> (raw)
In-Reply-To: <20210219210535.492733466@infradead.org>
On Fri, Feb 19, 2021 at 09:43:06PM +0100, Peter Zijlstra wrote:
> Arguably it would be simpler to do the other way around, but
> unfortunately alternatives don't work that way, we cannot say:
>
> ALTERNATIVE "call __x86_indirect_thunk_\reg",
> "call *%reg", ~X86_FEATURE_RETPOLINE
>
> That is, there is no negative form of alternatives.
X86_FEATURE_NO_RETPOLINE?
--
Josh
next prev parent reply other threads:[~2021-02-19 22:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 20:43 [RFC][PATCH 0/6] objtool: Optimize !retpoline Peter Zijlstra
2021-02-19 20:43 ` [RFC][PATCH 1/6] objtool: Correctly handle retpoline thunk calls Peter Zijlstra
2021-02-19 20:43 ` [RFC][PATCH 2/6] objtool: Fix static_call list generation Peter Zijlstra
2021-02-19 20:43 ` [RFC][PATCH 3/6] objtool: Rework rebuild_reloc logic Peter Zijlstra
2021-02-19 20:43 ` [RFC][PATCH 4/6] objtool: Add elf_create_undef_symbol() Peter Zijlstra
2021-02-19 20:43 ` [RFC][PATCH 5/6] objtool: Allow archs to rewrite retpolines Peter Zijlstra
2021-02-19 20:43 ` [RFC][PATCH 6/6] objtool,x86: Rewrite retpoline thunk calls Peter Zijlstra
2021-02-19 21:55 ` Josh Poimboeuf [this message]
2021-02-19 22:01 ` Peter Zijlstra
2021-02-20 0:39 ` Borislav Petkov
2021-02-20 16:48 ` Peter Zijlstra
2021-02-20 17:41 ` Borislav Petkov
2021-02-20 22:28 ` Peter Zijlstra
2021-02-20 22:51 ` Peter Zijlstra
2021-02-21 9:54 ` Borislav Petkov
2021-02-20 22:32 ` Peter Zijlstra
2021-02-21 5:45 ` Jürgen Groß
2021-02-21 9:44 ` Borislav Petkov
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=20210219215530.ivzzv3oavhuip6un@treble \
--to=jpoimboe@redhat.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suze.cz \
--cc=peterz@infradead.org \
--cc=pjt@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).