From owner-freebsd-arch Wed May 8 8:50:29 2002 Delivered-To: freebsd-arch@freebsd.org Received: from phoenix.dmnstech.net (phoenix.dmnstech.net [194.19.34.94]) by hub.freebsd.org (Postfix) with SMTP id 4272B37B41D; Wed, 8 May 2002 08:50:04 -0700 (PDT) Received: (from eivind@localhost) by phoenix.dmnstech.net (8.12.2/8.11.6) id g48FnmIC031647; Wed, 8 May 2002 17:49:48 +0200 (CEST) (envelope-from eivind) Date: Wed, 8 May 2002 17:49:48 +0200 From: Eivind Eklund To: Robert Watson Cc: John Baldwin , Matthew Dillon , arch@FreeBSD.ORG, Poul-Henning Kamp Subject: Re: syscall changes to deal with 32->64 changes. Message-ID: <20020508174948.B28633@phoenix.dmnstech.net> References: <20020507185119.C11452@phoenix.dmnstech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rwatson@FreeBSD.ORG on Tue, May 07, 2002 at 01:53:35PM -0400 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, May 07, 2002 at 01:53:35PM -0400, Robert Watson wrote: > > On Tue, 7 May 2002, Eivind Eklund wrote: > > > Somewhere between 0 and 3.5 we should have an > > > > X) Write a list of proposed changes to the syscalls by just going > > through the syscalls list and adding proposed changes, based on public > > discussion. > > > > I think the right thing to do might be to just make a copy of > > syscalls.master and let people commit suggested improvements, and then > > post it to arch for discussion after a while (e.g, 3 weeks.) > > Probably close to the right strategy -- unfortunately most of the more > interesting changes are in the supporting structs (struct stat, struct > ipcperm, ...), which does complicate things. Also, many of the changes > have to do with changing a type -- ino_t, or the like, rather than > changing the arguments to the system call. This breaks the ABI, but > maintains source-level compatibility as visible in syscalls.master :-). I was thinking of adding the suggested improvements as comments between the lines in the copy of syscalls.master, just using it as a red thread to make sure we examine a number of the relevant issues, and get a structured document out. And even the conversions you mention would end up being relevant there, as we would add comments on which syscalls would need a converting frontend to gain backwards compatibility. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message