Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: [patch] clone_startup(), 2.5.31-A0 | Date | 13 Aug 2002 12:52:11 -0700 |
| |
Followup to: <15705.13490.713278.815154@napali.hpl.hp.com> By author: David Mosberger <davidm@napali.hpl.hp.com> In newsgroup: linux.dev.kernel > > The original clone() system call was misdesigned. Even if you chose > to ignore ia64, clone() cannot be used by portable applications to > specify a stack (think "stack-growth direction"). >
This is something that can be handled in userspace on most architectures. The rest (ia64) can pass all the information on to kernel space.
The clone() system call cannot be used by portable applications *AT ALL*, since it inherently needs a user-space assembly wrapper. It's just a matter of how you define the interface to the assembly wrapper.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |