Date: Thu, 01 Feb 2001 13:19:24 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-hackers@FreeBSD.org, Drew Eckhardt <drew@PoohSticks.ORG>, Matt Dillon <dillon@earth.backplane.com> Subject: Re: Suboptimal mmap of devices on i86 Message-ID: <XFMail.010201131924.jhb@FreeBSD.org> In-Reply-To: <Pine.BSF.4.21.0102011242120.853-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010201131924.jhb>