All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6412] linux-user: add qemu_realloc() implementation to unbreak the build ( Gerd Hoffman)
Date: Fri, 23 Jan 2009 18:52:34 +0000	[thread overview]
Message-ID: <200901231852.35416.paul@codesourcery.com> (raw)
In-Reply-To: <4979F1E3.2050701@codemonkey.ws>

> > Is it really the correct fix?  The original error comes from the fact
> > we compile qemu_iovec_* in cutils.c.  Do we really need these
> > iovec functions for user-mode?
>
> I think the better question is, why isn't linux-user sharing
> qemu_malloc/qemu_realloc implementations with the system emulation?

Because userspace emulation has special requirements, and need to keep track 
of address space usage. You can't just blindly use malloc/mmap.

Paul

      parent reply	other threads:[~2009-01-23 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 15:02 [Qemu-devel] [6412] linux-user: add qemu_realloc() implementation to unbreak the build ( Gerd Hoffman) Anthony Liguori
2009-01-23 15:38 ` Laurent Desnogues
2009-01-23 16:35   ` Anthony Liguori
2009-01-23 17:15     ` Laurent Desnogues
2009-01-23 18:52     ` Paul Brook [this message]

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=200901231852.35416.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.