From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Oleg Nesterov <oleg@redhat.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH 02/10] x86/entry/compat: In SYSENTER, sink AC clearing below the existing FLAGS test
Date: Mon, 29 Feb 2016 21:39:41 +0100 [thread overview]
Message-ID: <20160229203941.GG3724@pd.tnic> (raw)
In-Reply-To: <e1af93fa282997469fdc692b81d5cf908d9c57fb.1456720860.git.luto@kernel.org>
On Sun, Feb 28, 2016 at 09:28:47PM -0800, Andy Lutomirski wrote:
> CLAC is slow, and the SYSENTER code already has an unlikely path
> that runs if unusual flags are set. Drop the CLAC and instead rely
> on the unlikely path to clear AC.
>
> This seems to save ~24 cycles on my Skylake laptop. (Hey, Intel,
> make this faster please!)
>
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> ---
> arch/x86/entry/entry_64_compat.S | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/entry/entry_64_compat.S b/arch/x86/entry/entry_64_compat.S
> index 89bcb4979e7a..7c8e72da7654 100644
> --- a/arch/x86/entry/entry_64_compat.S
> +++ b/arch/x86/entry/entry_64_compat.S
> @@ -66,8 +66,6 @@ ENTRY(entry_SYSENTER_compat)
> */
> pushfq /* pt_regs->flags (except IF = 0) */
> orl $X86_EFLAGS_IF, (%rsp) /* Fix saved flags */
> - ASM_CLAC /* Clear AC after saving FLAGS */
> -
> pushq $__USER32_CS /* pt_regs->cs */
> xorq %r8,%r8
> pushq %r8 /* pt_regs->ip = 0 (placeholder) */
> @@ -90,9 +88,9 @@ ENTRY(entry_SYSENTER_compat)
> cld
>
> /*
> - * Sysenter doesn't filter flags, so we need to clear NT
> + * Sysenter doesn't filter flags, so we need to clear NT and AC
> * ourselves. To save a few cycles, we can check whether
> - * NT was set instead of doing an unconditional popfq.
> + * either was set instead of doing an unconditional popfq.
> * This needs to happen before enabling interrupts so that
> * we don't get preempted with NT set.
> *
> @@ -102,7 +100,7 @@ ENTRY(entry_SYSENTER_compat)
> * we're keeping that code behind a branch which will predict as
> * not-taken and therefore its instructions won't be fetched.
> */
> - testl $X86_EFLAGS_NT, EFLAGS(%rsp)
> + testl $X86_EFLAGS_NT|X86_EFLAGS_AC, EFLAGS(%rsp)
> jnz .Lsysenter_fix_flags
> .Lsysenter_flags_fixed:
Do I see it correctly that with this change, that .Lsysenter_fix_flags:
is going to be visited each time on SMAP machines and then we can get
rid of it? The reason for it was not to pollute I$ as the comment says
but that happening now anyway...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-02-29 20:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 5:28 [PATCH 00/10] x86: Various SYSENTER/SYSEXIT/#DB fixes and cleanups Andy Lutomirski
2016-02-29 5:28 ` [PATCH 01/10] selftests/x86: In syscall_nt, test NT|TF as well Andy Lutomirski
2016-03-02 12:59 ` Borislav Petkov
2016-03-02 14:01 ` One Thousand Gnomes
2016-03-02 14:28 ` Borislav Petkov
2016-03-02 19:03 ` Andy Lutomirski
2016-03-02 19:30 ` Borislav Petkov
2016-02-29 5:28 ` [PATCH 02/10] x86/entry/compat: In SYSENTER, sink AC clearing below the existing FLAGS test Andy Lutomirski
2016-02-29 20:39 ` Borislav Petkov [this message]
2016-02-29 20:45 ` Andy Lutomirski
2016-02-29 22:09 ` Borislav Petkov
2016-02-29 22:33 ` Brian Gerst
2016-02-29 22:37 ` Borislav Petkov
2016-02-29 5:28 ` [PATCH 03/10] x86/entry/32: Filter NT and speed up AC filtering in SYSENTER Andy Lutomirski
2016-03-02 13:24 ` Borislav Petkov
2016-02-29 5:28 ` [PATCH 04/10] x86/entry/32: Restore FLAGS on SYSEXIT Andy Lutomirski
2016-02-29 5:28 ` [PATCH 05/10] x86/traps: Clear TIF_BLOCKSTEP on all debug exceptions Andy Lutomirski
2016-02-29 5:28 ` [PATCH 06/10] x86/traps: Clear DR6 early in do_debug and improve the comment Andy Lutomirski
2016-02-29 5:28 ` [PATCH 07/10] x86/entry: Vastly simplify SYSENTER TF handling Andy Lutomirski
2016-02-29 5:28 ` [PATCH 08/10] x86/entry: Only allocate space for SYSENTER_stack if needed Andy Lutomirski
2016-02-29 5:28 ` [PATCH 09/10] x86/entry/32: Simplify and fix up the SYSENTER stack #DB/NMI fixup Andy Lutomirski
2016-02-29 5:28 ` [PATCH 10/10] x86/entry/32: Add and check a stack canary for the SYSENTER stack Andy Lutomirski
2016-02-29 18:55 ` [PATCH 00/10] x86: Various SYSENTER/SYSEXIT/#DB fixes and cleanups Andy Lutomirski
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=20160229203941.GG3724@pd.tnic \
--to=bp@alien8.de \
--cc=andrew.cooper3@citrix.com \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.