From owner-freebsd-current@FreeBSD.ORG Sat Jul 26 01:24:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E783F37B401 for ; Sat, 26 Jul 2003 01:24:55 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36A2143F93 for ; Sat, 26 Jul 2003 01:24:55 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6Q8OEwO038446; Sat, 26 Jul 2003 01:24:14 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6Q8ODuw007538; Sat, 26 Jul 2003 01:24:13 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h6Q8ODWY007537; Sat, 26 Jul 2003 01:24:13 -0700 (PDT) (envelope-from marcel) Date: Sat, 26 Jul 2003 01:24:13 -0700 From: Marcel Moolenaar To: Terry Lambert Message-ID: <20030726082413.GB7470@dhcp01.pn.xcllnt.net> References: <3F2228ED.59F5739E@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F2228ED.59F5739E@mindspring.com> User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org cc: Shawn cc: Julian Elischer Subject: Re: fuword(), suword(), etc. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 08:24:56 -0000 On Sat, Jul 26, 2003 at 12:08:29AM -0700, Terry Lambert wrote: > > In answer to your question, my answer is still: > > "How do you intend to deal with 32 and 64 bit address spaces > on the same machine, if all you have is one function for the > copyin and one for the copyout?". > > Or is there no intent to allow IA32 binaries to run on IA64, > never ever ever? What does that have to do with anything? Adding fuptr()/suptr() has no consequences for supporting or not supporting different memory models with different pointer sizes. The functions are defined to operate on native (kernel PoV) pointers. Any non- native (kernel PoV) ABI has a non-native ABI handler that does all the mapping, converting and copying bits from userland to kernel and vice versa. And I can't believe I actually wasted my time telling you this when you only have to use your head instead of your keyboard. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net