[PATCH 00/12] x86: Rewrite 64-bit syscall code

From: Andy Lutomirski
Date: Mon Dec 07 2015 - 16:51:48 EST


This is kind of like the 32-bit and compat code, except that I
preserved the fast path this time. I was unable to measure any
significant performance change on my laptop in the fast path.

What do you all think?

Andy Lutomirski (12):
selftests/x86: Extend Makefile to allow 64-bit only tests
selftests/x86: Add check_initial_reg_state
x86/syscalls: Refactor syscalltbl.sh
x86/syscalls: Remove __SYSCALL_COMMON and __SYSCALL_X32
x86/syscalls: Move compat syscall entry handling into syscalltbl.sh
x86/syscalls: Add syscall entry qualifiers
x86/entry/64: Always run ptregs-using syscalls on the slow path
x86/entry/64: Call all native slow-path syscalls with full pt-regs
x86/entry/64: Stop using int_ret_from_sys_call in ret_from_fork
x86/entry/64: Migrate the 64-bit syscall slow path to C
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 | 80 +++----
arch/x86/entry/entry_32.S | 8 +-
arch/x86/entry/entry_64.S | 245 ++++++---------------
arch/x86/entry/entry_64_compat.S | 2 +-
arch/x86/entry/syscall_32.c | 10 +-
arch/x86/entry/syscall_64.c | 30 ++-
arch/x86/entry/syscalls/syscall_64.tbl | 18 +-
arch/x86/entry/syscalls/syscalltbl.sh | 58 ++++-
arch/x86/include/asm/thread_info.h | 5 +-
arch/x86/kernel/asm-offsets_32.c | 2 +-
arch/x86/kernel/asm-offsets_64.c | 10 +-
arch/x86/kernel/traps.c | 2 +-
arch/x86/um/sys_call_table_32.c | 4 +-
arch/x86/um/sys_call_table_64.c | 7 +-
arch/x86/um/user-offsets.c | 6 +-
tools/testing/selftests/x86/Makefile | 13 +-
.../selftests/x86/check_initial_reg_state.c | 108 +++++++++
17 files changed, 330 insertions(+), 278 deletions(-)
create mode 100644 tools/testing/selftests/x86/check_initial_reg_state.c

--
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/