All of lore.kernel.org
 help / color / mirror / Atom feed
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 03/10] x86/entry/32: Filter NT and speed up AC filtering in SYSENTER
Date: Wed, 2 Mar 2016 14:24:29 +0100	[thread overview]
Message-ID: <20160302132429.GI16954@pd.tnic> (raw)
In-Reply-To: <4679f3ffce8b74e96f13755375abf5e6f1f95f35.1456720860.git.luto@kernel.org>

On Sun, Feb 28, 2016 at 09:28:48PM -0800, Andy Lutomirski wrote:
> This makes the 32-bit code work just like the 64-bit code.  It should
> speed up syscalls on 32-bit kernels on Skylake by something like 20
> cycles (by analogy to the 64-bit compat case).
> 
> It also cleans up NT just like we do for the 64-bit case.
> 
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> ---
>  arch/x86/entry/entry_32.S | 23 ++++++++++++++++++++++-
>  1 file changed, 22 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/entry_32.S
> index ab710eee4308..263ebde6333f 100644
> --- a/arch/x86/entry/entry_32.S
> +++ b/arch/x86/entry/entry_32.S
> @@ -294,7 +294,6 @@ sysenter_past_esp:
>  	pushl	$__USER_DS		/* pt_regs->ss */
>  	pushl	%ebp			/* pt_regs->sp (stashed in bp) */
>  	pushfl				/* pt_regs->flags (except IF = 0) */
> -	ASM_CLAC			/* Clear AC after saving FLAGS */
>  	orl	$X86_EFLAGS_IF, (%esp)	/* Fix IF */
>  	pushl	$__USER_CS		/* pt_regs->cs */
>  	pushl	$0			/* pt_regs->ip = 0 (placeholder) */
> @@ -302,6 +301,23 @@ sysenter_past_esp:
>  	SAVE_ALL pt_regs_ax=$-ENOSYS	/* save rest */
>  
>  	/*
> +	 * Sysenter doesn't filter flags, so we need to clear NT and AC
> +	 * ourselves.  To save a few cycles, we can check whether
> +	 * either was set instead of doing an unconditional popfq.

Let's write insn names capitalized: SYSENTER, POPF, etc... I know,
entry_SYSENTER_compat() doesn't do it either but you could fix that up
in your 2/10 patch, since you're touching that place anyway...

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

  reply	other threads:[~2016-03-02 13:24 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
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 [this message]
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=20160302132429.GI16954@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.