Messages in this thread | | | Date | Tue, 13 Aug 2002 13:57:34 -0700 | From | "H. Peter Anvin" <> | Subject | Re: [patch] clone_startup(), 2.5.31-A0 |
| |
David Mosberger wrote: >>>>>>On Tue, 13 Aug 2002 13:27:02 -0700, "H. Peter Anvin" <hpa@zytor.com> said: >>>>> > > >> I was, however, the flaws that you complained of had nothing to > >> do with the syscall -- it's all in the syscall wrapper (which is > >> required for clone(), like it or not.) > > The issue is not whether a wrapper is needed or not. > > My point is that it is cleaner to always describe stack areas as > memory areas (e.g., as a base/size pair). Note that this is > effectively what's happening in the platform-independent part of the > kernel today. >
Right, but all the stack handling is a matter of the wrapper. sys_clone doesn't affect the stack at all.
-hpa
- 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/
| |