x86/asm/entry: Untangle 'ia32_sysenter_target' into two entry points: entry_SYSENTER_...
authorIngo Molnar <mingo@kernel.org>
Mon, 8 Jun 2015 06:33:56 +0000 (08:33 +0200)
committerIngo Molnar <mingo@kernel.org>
Mon, 8 Jun 2015 06:47:46 +0000 (08:47 +0200)
commit4c8cd0c50d0b1559727bf0ec7ff27caeba2dfe09
treebd477ba39b3ee39b9f6ecf64bfc74a602fa27d60
parent2cd23553b488589f287457b7396470f5e3c40698
x86/asm/entry: Untangle 'ia32_sysenter_target' into two entry points: entry_SYSENTER_32 and entry_SYSENTER_compat

So the SYSENTER instruction is pretty quirky and it has different behavior
depending on bitness and CPU maker.

Yet we create a false sense of coherency by naming it 'ia32_sysenter_target'
in both of the cases.

Split the name into its two uses:

ia32_sysenter_target (32)    -> entry_SYSENTER_32
ia32_sysenter_target (64)    -> entry_SYSENTER_compat

As per the generic naming scheme for x86 system call entry points:

entry_MNEMONIC_qualifier

where 'qualifier' is one of _32, _64 or _compat.

Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
arch/x86/entry/entry_32.S
arch/x86/entry/entry_64_compat.S
arch/x86/include/asm/proto.h
arch/x86/kernel/cpu/common.c
arch/x86/xen/xen-asm_64.S