From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
"Rik van Riel" <riel@redhat.com>,
"Oleg Nesterov" <oleg@redhat.com>,
"Denys Vlasenko" <vda.linux@googlemail.com>,
"Borislav Petkov" <bp@alien8.de>,
"Kees Cook" <keescook@chromium.org>,
"Brian Gerst" <brgerst@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andy Lutomirski" <luto@kernel.org>
Subject: [RFC/PATCH v2 v2 0/6] x86_32: Migrate to new entry/exit paths
Date: Thu, 9 Jul 2015 19:17:28 -0700 [thread overview]
Message-ID: <cover.1436492057.git.luto@kernel.org> (raw)
This is a review version of the 32-bit asm-to-C migration. I think
it works, but it's not yet well enough tested. I'm a lot more
familiar with the 64-bit asm than the 32-bit asm.
The vm86 stuff especially needs much more careful testing. Brian,
since you're playing with vm86 now, can you take a look?
Changes from v1:
- Fix some nasty vm86 issues. v1 was a regression. v2 is an improvement
over the status quo AFAICT.
- Add patch 1, which is probably worthwhile on its own.
- Get rid of the temporary ud2 hack.
Andy Lutomirski (6):
x86/selftests, x86/vm86: Improve entry_from_vm86 selftest
x86/entry/32: Remove 32-bit syscall audit optimizations
x86/entry/32: Fix an incorrect comment for work_notifysig_v86
x86/entry/32: Remove unnecessary asm check for returns to kernel mode
x86/entry/32: Migrate to C exit path and rework vm86 exit hack
x86/entry: Remove do_notify_resume, syscall_trace_leave, and their TIF
masks
arch/x86/entry/common.c | 107 ++++++++++-----------
arch/x86/entry/entry_32.S | 130 +++----------------------
arch/x86/include/asm/ptrace.h | 1 -
arch/x86/include/asm/signal.h | 1 -
arch/x86/include/asm/thread_info.h | 18 +---
arch/x86/kernel/vm86_32.c | 6 +-
tools/testing/selftests/x86/entry_from_vm86.c | 132 ++++++++++++++++++++++++--
7 files changed, 191 insertions(+), 204 deletions(-)
--
2.4.3
next reply other threads:[~2015-07-10 2:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 2:17 Andy Lutomirski [this message]
2015-07-10 2:17 ` [RFC/PATCH v2 v2 1/6] x86/selftests, x86/vm86: Improve entry_from_vm86 selftest Andy Lutomirski
2015-07-13 19:33 ` Andy Lutomirski
2015-07-21 9:44 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-07-10 2:17 ` [RFC/PATCH v2 v2 2/6] x86/entry/32: Remove 32-bit syscall audit optimizations Andy Lutomirski
2015-07-10 2:17 ` [RFC/PATCH v2 v2 3/6] x86/entry/32: Fix an incorrect comment for work_notifysig_v86 Andy Lutomirski
2015-07-10 2:17 ` [RFC/PATCH v2 v2 4/6] x86/entry/32: Remove unnecessary asm check for returns to kernel mode Andy Lutomirski
2015-07-10 2:17 ` [RFC/PATCH v2 v2 5/6] x86/entry/32: Migrate to C exit path and rework vm86 exit hack Andy Lutomirski
2015-07-10 2:17 ` [RFC/PATCH v2 v2 6/6] x86/entry: Remove do_notify_resume, syscall_trace_leave, and their TIF masks Andy Lutomirski
2015-07-10 14:45 ` [RFC/PATCH v2 v2 0/6] x86_32: Migrate to new entry/exit paths Brian Gerst
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.1436492057.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=fweisbec@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.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 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).