From: Ingo Molnar <mingo@kernel.org>
To: Brian Gerst <brgerst@gmail.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Borislav Petkov" <bp@alien8.de>,
"H . Peter Anvin" <hpa@zytor.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Mika Penttilä" <mpenttil@redhat.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Uros Bizjak" <ubizjak@gmail.com>,
"Denys Vlasenko" <dvlasenk@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Josh Poimboeuf" <jpoimboe@redhat.com>
Subject: Re: [PATCH v2 0/6] x86: Clean up fast syscall return validation
Date: Thu, 5 Oct 2023 22:20:47 +0200 [thread overview]
Message-ID: <ZR8an4+JbkLS8/Ol@gmail.com> (raw)
In-Reply-To: <CAMzpN2j7qddPEUdD+ZX3dtyQkPq6e4gzwcu5szkZ2esh_8zm9g@mail.gmail.com>
* Brian Gerst <brgerst@gmail.com> wrote:
> Looking at the compiled output, the only suboptimal code appears to be
> the canonical address test, where the C code uses the CL register for
> the shifts instead of immediates.
>
> 180: e9 00 00 00 00 jmp 185 <do_syscall_64+0x85>
> 181: R_X86_64_PC32 .altinstr_aux-0x4
> 185: b9 07 00 00 00 mov $0x7,%ecx
> 18a: eb 05 jmp 191 <do_syscall_64+0x91>
> 18c: b9 10 00 00 00 mov $0x10,%ecx
> 191: 48 89 c2 mov %rax,%rdx
> 194: 48 d3 e2 shl %cl,%rdx
> 197: 48 d3 fa sar %cl,%rdx
> 19a: 48 39 d0 cmp %rdx,%rax
> 19d: 75 39 jne 1d8 <do_syscall_64+0xd8>
Yeah, it didn't look equivalent - so I guess we want a C equivalent for:
- ALTERNATIVE "shl $(64 - 48), %rcx; sar $(64 - 48), %rcx", \
- "shl $(64 - 57), %rcx; sar $(64 - 57), %rcx", X86_FEATURE_LA57
instead of the pgtable_l5_enabled() runtime test that
__is_canonical_address() uses?
Thanks,
Ingo
next prev parent reply other threads:[~2023-10-05 20:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 16:10 [PATCH v2 0/6] x86: Clean up fast syscall return validation Brian Gerst
2023-07-21 16:10 ` [PATCH v2 1/6] x86/entry/64: Remove obsolete comment on tracing vs. SYSRET Brian Gerst
2023-10-05 8:28 ` [tip: x86/entry] " tip-bot2 for Brian Gerst
2023-07-21 16:10 ` [PATCH v2 2/6] x86/entry/64: Convert SYSRET validation tests to C Brian Gerst
2023-07-23 9:53 ` Li, Xin3
2023-07-23 11:17 ` Brian Gerst
2023-07-21 16:10 ` [PATCH v2 3/6] x86/entry/compat: Combine return value test from syscall handler Brian Gerst
2023-10-05 8:28 ` [tip: x86/entry] " tip-bot2 for Brian Gerst
2023-07-21 16:10 ` [PATCH v2 4/6] x86/entry/32: Convert do_fast_syscall_32() to bool return type Brian Gerst
2023-10-05 8:28 ` [tip: x86/entry] " tip-bot2 for Brian Gerst
2023-07-21 16:10 ` [PATCH v2 5/6] x86/entry/32: Remove SEP test for SYSEXIT Brian Gerst
2023-10-05 8:28 ` [tip: x86/entry] " tip-bot2 for Brian Gerst
2023-07-21 16:10 ` [PATCH v2 6/6] x86/entry/32: Clean up syscall fast exit tests Brian Gerst
2023-10-05 8:22 ` [PATCH v2 0/6] x86: Clean up fast syscall return validation Ingo Molnar
2023-10-05 15:13 ` Brian Gerst
2023-10-05 20:20 ` Ingo Molnar [this message]
2023-10-06 18:59 ` H. Peter Anvin
2023-10-06 21:32 ` Brian Gerst
2023-10-07 9:42 ` Ingo Molnar
2023-10-06 23:58 ` H. Peter Anvin
2023-10-07 9:56 ` Uros Bizjak
2023-10-07 18:07 ` Linus Torvalds
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=ZR8an4+JbkLS8/Ol@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mpenttil@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.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).