linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, "Borislav Petkov" <bp@alien8.de>,
	"Brian Gerst" <brgerst@gmail.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Andy Lutomirski" <luto@kernel.org>
Subject: [PATCH 0/2] x86/entry: Do context tracking with IRQs off (finally!)
Date: Sun,  6 Mar 2016 18:30:05 -0800	[thread overview]
Message-ID: <cover.1457317513.git.luto@kernel.org> (raw)

This provides no direct benefit by itself, but it finally lets us
apply some of the speedups that Paolo and possible Rik independently
wrote: we won't need an irqsave/irqrestore pair in the context
tracking code.

It should also let us remove the last callers of exception_enter in
x86 kernels, but that removal should probably wait until I carefully
re-read the page fault code.

Andy Lutomirski (2):
  x86/entry/32: Change INT80 to be an interrupt gate
  x86/entry: Do enter_from_user_mode with IRQs off

 arch/x86/entry/common.c            | 54 ++++++++++++--------------------------
 arch/x86/entry/entry_32.S          |  8 +++---
 arch/x86/entry/entry_64_compat.S   |  2 +-
 arch/x86/include/asm/thread_info.h |  5 +++-
 arch/x86/kernel/traps.c            |  2 +-
 5 files changed, 27 insertions(+), 44 deletions(-)

-- 
2.5.0

             reply	other threads:[~2016-03-07  2:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07  2:30 Andy Lutomirski [this message]
2016-03-07  2:30 ` [PATCH 1/2] x86/entry/32: Change INT80 to be an interrupt gate Andy Lutomirski
2016-03-07  2:30 ` [PATCH 2/2] x86/entry: Do enter_from_user_mode with IRQs off Andy Lutomirski
2016-03-08 13:46   ` Borislav Petkov
2016-03-08 17:25     ` 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=cover.1457317513.git.luto@kernel.org \
    --to=luto@kernel.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).