From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, tony.luck@intel.com, pjt@google.com,
linux-kernel@vger.kernel.org, r.marek@assembler.cz,
jpoimboe@redhat.com, jikos@kernel.org, andrew.cooper3@citrix.com
Subject: Re: [RFC][PATCH 2/2] x86/retpoline: Compress retpolines
Date: Mon, 22 Feb 2021 12:27:36 +0100 [thread overview]
Message-ID: <YDOVKBHDC3ish9k/@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210219071439.GA26778@zn.tnic>
On Fri, Feb 19, 2021 at 08:14:39AM +0100, Borislav Petkov wrote:
> On Thu, Feb 18, 2021 at 05:59:40PM +0100, Peter Zijlstra wrote:
> > By using int3 as a speculation fence instead of lfence, we can shrink
> > the longest alternative to just 15 bytes:
> >
> > 0: e8 05 00 00 00 callq a <.altinstr_replacement+0xa>
> > 5: f3 90 pause
> > 7: cc int3
> > 8: eb fb jmp 5 <.altinstr_replacement+0x5>
> > a: 48 89 04 24 mov %rax,(%rsp)
> > e: c3 retq
> >
> > This means we can change the alignment from 32 to 16 bytes and get 4
> > retpolines per cacheline, $I win.
>
> You mean I$ :)
Typin' so hard.
> In any case, for both:
>
> Reviewed-by: Borislav Petkov <bp@suse.de>
Thanks, except I've been told there is a performance implication. But
since all that happened in sekrit, none of that is recorded :/
I was hoping for some people (Tony, Paul) to respond with more data.
Also, Andrew said that if we ditch the lfence we could also ditch the
pause.
So people, please speak up, and if possible share any data you still
might have from back when retpolines were developed such that we can
have it on record.
next prev parent reply other threads:[~2021-02-22 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 16:59 [RFC][PATCH 0/2] x86/retpoline: Retpoline on a diet Peter Zijlstra
2021-02-18 16:59 ` [RFC][PATCH 1/2] x86/retpoline: Simplify retpolines Peter Zijlstra
2021-02-22 11:36 ` Peter Zijlstra
2021-02-18 16:59 ` [RFC][PATCH 2/2] x86/retpoline: Compress retpolines Peter Zijlstra
2021-02-19 7:14 ` Borislav Petkov
2021-02-22 11:27 ` Peter Zijlstra [this message]
2021-02-18 18:46 ` [RFC PATCH] x86/retpolines: Prevent speculation after RET Borislav Petkov
2021-02-18 19:02 ` Peter Zijlstra
2021-02-18 19:11 ` Borislav Petkov
2021-02-19 8:15 ` Peter Zijlstra
2021-02-19 12:08 ` Andrew Cooper
2021-02-19 9:28 ` David Laight
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=YDOVKBHDC3ish9k/@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjt@google.com \
--cc=r.marek@assembler.cz \
--cc=tony.luck@intel.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
Powered by JetHome