Re: [PATCHv2 0/2] clone: Support passing tls argument via C rather than pt_regs magic

2015-05-12 Thread Ingo Molnar
* Josh Triplett wrote: > clone has some of the quirkiest syscall handling in the kernel, with > a pile of special cases, historical curiosities, and > architecture-specific calling conventions. In particular, clone > with CLONE_SETTLS accepts a parameter "tls" that the C entry point >

Re: [PATCHv2 0/2] clone: Support passing tls argument via C rather than pt_regs magic

2015-05-12 Thread Ingo Molnar
* Josh Triplett j...@joshtriplett.org wrote: clone has some of the quirkiest syscall handling in the kernel, with a pile of special cases, historical curiosities, and architecture-specific calling conventions. In particular, clone with CLONE_SETTLS accepts a parameter tls that the C

[PATCHv2 0/2] clone: Support passing tls argument via C rather than pt_regs magic

2015-05-11 Thread Josh Triplett
clone has some of the quirkiest syscall handling in the kernel, with a pile of special cases, historical curiosities, and architecture-specific calling conventions. In particular, clone with CLONE_SETTLS accepts a parameter "tls" that the C entry point completely ignores and some assembly entry

[PATCHv2 0/2] clone: Support passing tls argument via C rather than pt_regs magic

2015-05-11 Thread Josh Triplett
clone has some of the quirkiest syscall handling in the kernel, with a pile of special cases, historical curiosities, and architecture-specific calling conventions. In particular, clone with CLONE_SETTLS accepts a parameter tls that the C entry point completely ignores and some assembly entry