Hi Andy,
The last patchset did not compile on i386. Please ignore it. This one
should be better. Instead of removing KERNEL_STACK_OFFSET, it is now
used consistently on both i386 and x86_64.
Boot tested using qemu (using klibc for userspace)
- x86_64, 32-bit userspace, core2duo (sysenter32)
- x86_64, 32-bit userspace, phenom (syscall32)
- x86_64, 32-bit userspace, vdso=0 (int 0x80)
- x86_64, 64-bit userspace
- i386, pentium3 (sysenter)
- i386, athlon (syscall)
- i386, vdso=0 (int 0x80)
They were tested on top of 22f2aa4a0361707a5cfb1de9d45260b39965dead
(x86/entry-devel in your tree) and this kernel is now running on my
laptop.
Greetings,
Alexander
Alexander van Heukelum (4):
x86_64: cleanup THREAD_INFO(reg,offset) macro
x86_64: embrace KERNEL_STACK_OFFSET
i386: clean up KERNEL_STACK_OFFSET
x86_64, entry: Create IRET-compatible stack frame at syscall entry
arch/x86/ia32/ia32entry.S | 33 ++++++++--------
arch/x86/include/asm/calling.h | 1 +
arch/x86/include/asm/processor.h | 43 ++++++++-------------
arch/x86/include/asm/thread_info.h | 17 +++++++-
arch/x86/kernel/entry_32.S | 5 ++-
arch/x86/kernel/entry_64.S | 79 +++++++++++---------------------------
arch/x86/kernel/process_64.c | 5 +--
7 files changed, 75 insertions(+), 108 deletions(-)
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
