Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 13 Aug 2002 16:54:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 13 Aug 2002 16:54:07 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:27401 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 13 Aug 2002 16:54:07 -0400 Message-ID: <3D5972BE.3020300@zytor.com> Date: Tue, 13 Aug 2002 13:57:34 -0700 From: "H. Peter Anvin" Organization: Zytor Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020703 X-Accept-Language: en, sv MIME-Version: 1.0 To: davidm@hpl.hp.com CC: linux-kernel@vger.kernel.org Subject: Re: [patch] clone_startup(), 2.5.31-A0 References: <20020813160924.GA3821@codepoet.org> <20020813171138.A12546@infradead.org> <15705.13490.713278.815154@napali.hpl.hp.com> <15705.27073.997831.983519@napali.hpl.hp.com> <3D596B96.4000305@zytor.com> <15705.29059.306202.720523@napali.hpl.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 943 Lines: 27 David Mosberger wrote: >>>>>>On Tue, 13 Aug 2002 13:27:02 -0700, "H. Peter Anvin" 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/