From owner-freebsd-hackers Thu Feb 1 13:20: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C542537B491 for ; Thu, 1 Feb 2001 13:19:40 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f11LDf356681; Thu, 1 Feb 2001 13:13:41 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 01 Feb 2001 13:19:24 -0800 (PST) From: John Baldwin To: Doug White Subject: Re: Suboptimal mmap of devices on i86 Cc: freebsd-hackers@FreeBSD.org, Drew Eckhardt , Matt Dillon Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-Feb-01 Doug White wrote: > On Mon, 29 Jan 2001, John Baldwin wrote: > >> Then only rename it in 4.x We can do an API change for 5.0. We'll be >> renaming syscall2() back to syscall() in 5.0 for example. We don't >> want to end up with syscall47() someday in FreeBSD 67.2. :-P > > And what happens to apps using the previous syscall(2) interface? They > die horribly? That's not acceptable. Huh? syscall2() is an internal kernel function. The only thing that might call it is a kernel module, and we won't support 4.x KLD's on 5.0. Period. It was renamed to syscall2() to cause old KLD's to fail to load with a symbol lookup problem back when teh MPSAFE flag was first added to x86 syscalls. The only thing that changing it back to syscall() in -current does is cause any 6 month old 5.0-current KLD's that happen to call syscall() to call it wrong. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message