From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DwBfN-0004Dm-Fl
	for qemu-devel@nongnu.org; Sat, 23 Jul 2005 00:31:13 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DwBfH-0004An-CS
	for qemu-devel@nongnu.org; Sat, 23 Jul 2005 00:31:10 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DwBfG-000483-Uh
	for qemu-devel@nongnu.org; Sat, 23 Jul 2005 00:31:07 -0400
Received: from [128.8.10.164] (helo=po2.wam.umd.edu)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DwBZt-0005pN-Lc
	for qemu-devel@nongnu.org; Sat, 23 Jul 2005 00:25:33 -0400
Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180])
	by po2.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j6N4FDZ3000224
	for <qemu-devel@nongnu.org>; Sat, 23 Jul 2005 00:15:13 -0400 (EDT)
Date: Sat, 23 Jul 2005 00:15:12 -0400
From: "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] Anyone familiar with the slirp code?
Message-ID: <20050723041512.GA18936@jbrown.mylinuxbox.org>
References: <20050722220547.GA18141@jbrown.mylinuxbox.org>
	<7B584610-FB03-11D9-A63F-003065C7D858@mandriva.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7B584610-FB03-11D9-A63F-003065C7D858@mandriva.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Sat, Jul 23, 2005 at 12:53:55AM +0200, Gwenole Beauchesne wrote:
> Le samedi, 23 jul 2005, ? 00:05 Europe/Paris, Jim C. Brown a ?crit :
> 
> >On Fri, Jul 22, 2005 at 08:45:16PM +0200, Gwenole Beauchesne wrote:
> >>AFAICS, slirp code in qemu cvs and other projects works on x86_64.
> >
> >Nope.
> My testing limited to 32-bit 
> Ubuntu Live as guest on 64-bit Mandriva Linux 2005 and downloading 
> files from FTP performed very well.

Well, I remember someone having issues with slirp and WinXP on an AMD64 host
a few months ago, but you're right that seems to be fixed now.

> 
> Then please provide a clear testcase.

Well, x86_64 on x86_64. But, rereading the emails, that doesn't cover this case,
which is x86 on x86_64.

> A more complete solution than used in current CVS can use 
> qemu_{malloc,realloc,*}() instead with special provisions to returning 
> memory with addresses that fit under 32-bit. qemu already does this but 
> only for (deprecated) qemu-fast at this time.
> 

Still not a very good substitute for fixing the slirp code to handle 64bit
values properly imho.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.