linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>,
	Thomas Gleixner <tglx@linutronix.de>, X86 ML <x86@kernel.org>,
	Ingo Molnar <mingo@redhat.com>
Cc: Sebastian Lackner <sebastian@fds-team.de>,
	Anish Bhatt <anish@chelsio.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Chuck Ebbert <cebbert.lkml@gmail.com>
Subject: Re: [PATCH v3 0/2] x86_64,entry: Clear NT on entry and speed up switch_to
Date: Wed, 01 Oct 2014 11:34:10 -0700	[thread overview]
Message-ID: <542C4922.408@zytor.com> (raw)
In-Reply-To: <cover.1412187233.git.luto@amacapital.net>

On 10/01/2014 11:28 AM, Andy Lutomirski wrote:
> Anish Bhatt noticed that user programs can set RFLAGS.NT before
> syscall or sysenter, and the kernel entry code doesn't filter out
> NT.  This causes kernel C code and, depending on thread flags, the
> exit slow path to run with NT set.
> 
> The former is a little bit scary (imagine calling into EFI with NT
> set), and the latter will fail with #GP and send a spurious SIGSEGV.
> 
> One answer would be "don't do that".  But the kernel can do better
> here.
> 
> These patches filter NT on all kernel entries.  For syscall (both
> bitnesses), this is free.  For sysenter, it seems to cost very
> little (less than my ability to measure, although I didn't try that
> hard).  Patch 2, which isn't tagged for -stable, speeds up context
> switches by avoiding saving and restoring flags, so this series
> should be a decent overall performance win.
> 
> See: https://bugs.winehq.org/show_bug.cgi?id=33275
> 
> Note to bikeshedders: I have no desire to go crazy micro-optimizing
> the sysenter path. :) This version seems to be good enough (and
> should be a performance *increase* for most workloads).
> 

The motivation for this in -stable is the Wine issue, right?  Could you
please add that to the patch description for the 1/2 patch?

Thanks,

	-hpa


      parent reply	other threads:[~2014-10-01 18:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 18:28 [PATCH v3 0/2] x86_64,entry: Clear NT on entry and speed up switch_to Andy Lutomirski
2014-10-01 18:28 ` [PATCH v3 1/2] x86_64,entry: Filter RFLAGS.NT on entry from userspace Andy Lutomirski
2014-10-01 18:28 ` [PATCH v3 2/2] x86_64: Don't save flags on context switch Andy Lutomirski
2014-10-01 18:35   ` H. Peter Anvin
2014-10-01 18:44     ` Andy Lutomirski
2014-10-20 18:52   ` Andy Lutomirski
2014-10-28 11:14   ` [tip:x86/asm] sched/x86_64: " tip-bot for Andy Lutomirski
2014-11-03 21:11     ` Andy Lutomirski
2014-11-03 21:47       ` Oleg Nesterov
2014-11-03 21:58         ` Oleg Nesterov
2014-11-03 22:37           ` Andy Lutomirski
2014-11-03 22:57             ` Oleg Nesterov
2014-11-03 23:02               ` Andy Lutomirski
2014-11-03 23:10                 ` Oleg Nesterov
2014-11-04 23:09             ` Oleg Nesterov
2014-11-03 22:17       ` H. Peter Anvin
2014-10-01 18:34 ` H. Peter Anvin [this message]

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=542C4922.408@zytor.com \
    --to=hpa@zytor.com \
    --cc=anish@chelsio.com \
    --cc=cebbert.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=sebastian@fds-team.de \
    --cc=tglx@linutronix.de \
    --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).