From: Andy Lutomirski <luto@amacapital.net>
To: "H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
x86@kernel.org, Borislav Petkov <bp@alien8.de>
Cc: Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH 0/2] x86_64: LRET to userspace
Date: Wed, 23 Jul 2014 08:34:10 -0700 [thread overview]
Message-ID: <cover.1406129131.git.luto@amacapital.net> (raw)
This series is based on tip/perf/urgent. It should apply to any
recent kernel, but my test case [1] will OOPS without the fix in
tip/perf/urgent.
The first patch or something like it is needed for 3.16, regardless
of any lret hackery -- I think it's making its way toward a pull
request this week, but I haven't seen it land in -tip yet.
I'm repeating it here because the LRET stuff won't work on paravirt,
and patch 1 puts the machinery for that in place.
tl;dr Read patch 2. To test, apply patch 1 and consider basing on
tip/perf/urgent.
[1] sigreturn_32 from https://gitorious.org/linux-test-utils/linux-clock-tests/
Andy Lutomirski (2):
x86_64,entry,xen: Do not invoke espfix64 on Xen
x86_64,entry: Use lret to return to userspace when possible
arch/x86/include/asm/irqflags.h | 3 +-
arch/x86/include/asm/paravirt.h | 4 ++
arch/x86/include/asm/traps.h | 6 ++
arch/x86/kernel/cpu/mcheck/mce.c | 2 +
arch/x86/kernel/entry_64.S | 121 ++++++++++++++++++++++++++++++------
arch/x86/kernel/nmi.c | 21 +++++++
arch/x86/kernel/paravirt_patch_64.c | 2 -
7 files changed, 136 insertions(+), 23 deletions(-)
--
1.9.3
next reply other threads:[~2014-07-23 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 15:34 Andy Lutomirski [this message]
2014-07-23 15:34 ` [PATCH 1/2] x86_64,entry,xen: Do not invoke espfix64 on Xen Andy Lutomirski
2014-07-28 22:33 ` [tip:x86/urgent] x86_64/entry/xen: " tip-bot for Andy Lutomirski
2014-07-29 3:39 ` Andy Lutomirski
2014-07-29 3:47 ` H. Peter Anvin
2014-07-23 15:34 ` [PATCH 2/2] x86_64,entry: Use lret to return to userspace when possible 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.1406129131.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.