From owner-freebsd-arch Mon May 6 18: 5:54 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 5049337B401; Mon, 6 May 2002 18:05:49 -0700 (PDT) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g4715lO8170530; Mon, 6 May 2002 21:05:47 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <33534.1020505495@critter.freebsd.dk> References: <33534.1020505495@critter.freebsd.dk> Date: Mon, 6 May 2002 21:05:46 -0400 To: Poul-Henning Kamp , Robert Watson From: Garance A Drosihn Subject: Re: syscall changes to deal with 32->64 changes. Cc: arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 11:44 AM +0200 5/4/02, Poul-Henning Kamp wrote: >I think a realistic plan might look something like this: > >1. Change the in-kernel types to 64 bits > for each entity to change size: > a) rewrite syscall entries to translate sizes. > b) change size in kernel, but retain old size > in userland > >2. Add new syscall API > a) write syscalls implementations. > >3. Change userland over. > a) Add #ifdef NEWAPI all over the includes so people > can select which API to use. > b) Create new major-revv libc which uses new API > c) Leave people time to find bugs in ports etc. > d) Throw the switch for good. > >Earliest realistic dates would be 3c on july 1st and 3d >a month later. > >Is that too late for 5.0-R ? If that timetable is doable, then I think it's reasonable to do. The alternate question is that if we did NOT go with a new syscall vector, then how much work will it be to get these 32->64bit changes done before 5.0? I assume the variable would be something more distinctive than "NEWAPI"... At 3:41 AM -0400 5/4/02, Robert Watson wrote: >John Baldwin and I have thrown this idea around a number >of times, as we keep bumping into things that would change >the ABI. What things would those be? Might as well get them listed, and see how many of them (if any...) could be included in this new vector without hurting the timetable. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message