From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: x86@kernel.org, brgerst@gmail.com, jiangshanlai@gmail.com,
Andrew.Cooper3@citrix.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86: Simplify Retpoline thunk
Date: Wed, 20 Apr 2022 17:51:16 +0200 [thread overview]
Message-ID: <20220420155116.GH2731@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220420152736.qzl3nikds6mq5nrr@treble>
On Wed, Apr 20, 2022 at 08:27:36AM -0700, Josh Poimboeuf wrote:
> On Tue, Apr 19, 2022 at 10:41:10PM +0200, Peter Zijlstra wrote:
> > Now that we rewrite all the indirect call sites, per commit:
> >
> > 750850090081 ("x86/alternative: Implement .retpoline_sites support")
> >
> > it doesn't make sense to have the retpoline thunks be an ALTERNATIVE_2
> > that still includes a 'naked' indirect jump.
> >
> > (this accidentally 'defunnels' i386 by going back to full retpolines)
>
> So mitigations=off no longer works on i386?
Also true I suppose... does anybody care? /me runs like heck.
I'd hate to make all this more complicated just because i386 tho :/
next prev parent reply other threads:[~2022-04-20 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 20:41 [PATCH 0/2] x86: A few random cleanups Peter Zijlstra
2022-04-19 20:41 ` [PATCH 1/2] x86: Simplify Retpoline thunk Peter Zijlstra
2022-04-20 15:27 ` Josh Poimboeuf
2022-04-20 15:51 ` Peter Zijlstra [this message]
2022-04-20 16:01 ` Josh Poimboeuf
2022-04-19 20:41 ` [PATCH 2/2] x86,entry: Use PUSH_AND_CLEAR_REGS for compat Peter Zijlstra
2022-04-20 3:21 ` Josh Poimboeuf
2022-04-20 7:07 ` Peter Zijlstra
2022-04-20 14:58 ` Josh Poimboeuf
2022-04-20 4:29 ` Lai Jiangshan
2022-04-20 14:26 ` Andy Lutomirski
2022-04-20 14:51 ` Peter Zijlstra
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=20220420155116.GH2731@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Andrew.Cooper3@citrix.com \
--cc=brgerst@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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