linux/arch/xtensa/kernel/process.c, branch v4.5

xtensa: Use generic idle loop

2013-04-08T15:39:29Z

Signed-off-by: Thomas Gleixner Cc: Linus Torvalds Cc: Rusty Russell Cc: Paul McKenney Cc: Peter Zijlstra Reviewed-by: Srivatsa S. Bhat Cc: Magnus Damm Acked-by: Chris Zankel Link: http://lkml.kernel.org/r/20130321215235.546600507@linutronix.de Signed-off-by: Thomas Gleixner

xtensa: add support for TLS

2013-02-24T03:35:57Z

The Xtensa architecture provides a global register called THREADPTR for the purpose of Thread Local Storage (TLS) support. This allows us to use a fairly simple implementation, keeping the thread pointer in the regset and simply saving and restoring it upon entering/exiting the from user space. Signed-off-by: Chris Zankel

xtensa: clean up files to make them code-style compliant

2012-12-19T05:10:25Z

Remove heading and trailing spaces, trim trailing lines, and wrap lines that are longer than 80 characters. Signed-off-by: Chris Zankel

flagday: don't pass regs to copy_thread()

2012-11-29T04:43:42Z

Signed-off-by: Al Viro

xtensa: switch to generic clone()

2012-11-29T04:43:41Z

Signed-off-by: Al Viro

xtensa: switch to generic sys_execve()

2012-10-25T22:00:44Z

Signed-off-by: Max Filippov Signed-off-by: Chris Zankel

xtensa: switch to generic kernel_thread()

2012-10-25T22:00:03Z

Signed-off-by: Max Filippov Signed-off-by: Chris Zankel

xtensa: reset windowbase/windowstart when cloning the VM

2012-10-25T21:53:36Z

When we copy a user thread with CLONE_VM, we also have to reset windowbase and windowstart to start a pristine stack frame. Otherwise, overflows can happen using the address 0 as the stack pointer. Also add a special case for vfork, which continues on the parent stack until it calls execve. Because this could be a call8, we need to spill the stack pointer of the previus frame (if still 'live' in the register file). Signed-off-by: Chris Zankel

xtensa: minor compiler warning fix

2012-10-19T17:24:20Z

Fix two compiler warnings complaining about truncating a value on a 64-bit host, and about declaring an unused variable that is only used for a specific configuration. Signed-off-by: Chris Zankel

xtensa: copy_thread with CLONE_VM must not copy live parent AR windows

2012-10-16T04:42:27Z

When doing a fork (new VM), the new task has a mirror image of the parent's stack, so keeps the same live register windows etc. However when doing a clone with CLONE_VM, keeping the same VM (eg. when creating a new thread), the child starts afresh on a new stack -- it cannot share any part of the parent stack. It especially cannot have the same live AR windows as the parent, otherwise it will overwrite the parent stack on overflow, likely causing corruption. (and so it did...) Effectively, the register windows need to be spilled. Turns out it's much easier to simply not copy parent register windows when CLONE_VM is set. Signed-off-by: Marc Gauthier Signed-off-by: Max Filippov Signed-off-by: Chris Zankel