Peter Maydell 4ce6243dc6 linux-user: Clean up handling of clone() argument order ... Linux manages to have three separate orderings of the arguments to the clone() syscall on different architectures. In the kernel these are selected via CONFIG_CLONE_BACKWARDS and CONFIG_CLONE_BACKWARDS2. Clean up our implementation of this to use similar #define names rather than a TARGET_* ifdef ladder. This includes behaviour changes fixing bugs on cris, x86-64, m68k, openrisc and unicore32. cris had explicit but wrong handling; the others were just incorrectly using QEMU's default, which happened to be the equivalent of CONFIG_CLONE_BACKWARDS. (unicore32 appears to be broken in the mainline kernel in that it tries to use arg3 for both parent_tidptr and newtls simultaneously -- we don't attempt to emulate this bug...) Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>		2013-07-22 21:54:36 +03:00
..
syscall_nr.h
syscall.h	linux-user: Clean up handling of clone() argument order	2013-07-22 21:54:36 +03:00
target_cpu.h	linux-user: Move cpu_clone_regs() and cpu_set_tls() into linux-user	2013-07-09 21:20:28 +02:00
target_signal.h
termbits.h