qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Anyone familiar with the slirp code?
Date: Sat, 23 Jul 2005 00:15:12 -0400	[thread overview]
Message-ID: <20050723041512.GA18936@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <7B584610-FB03-11D9-A63F-003065C7D858@mandriva.com>

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.

  reply	other threads:[~2005-07-23  4:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22 15:51 [Qemu-devel] Anyone familiar with the slirp code? Paul LeoNerd Evans
2005-07-22 16:47 ` John R. Hogerhuis
2005-07-22 18:14   ` Paul LeoNerd Evans
2005-07-22 18:45 ` Gwenole Beauchesne
2005-07-22 22:05   ` Jim C. Brown
2005-07-22 22:53     ` Gwenole Beauchesne
2005-07-23  4:15       ` Jim C. Brown [this message]
2005-07-24 18:09         ` Adrian Smarzewski
2005-07-22 22:29 ` Josh Metzler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050723041512.GA18936@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).