From: Paul Brook <paul@codesourcery.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Riku Voipio <riku.voipio@iki.fi>,
Richard Henderson <rth@twiddle.net>,
"dvaleev@suse.com" <dvaleev@suse.com>,
Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] PPC: Fix linker scripts on ppc hosts
Date: Wed, 14 Dec 2011 12:04:45 +0000 [thread overview]
Message-ID: <201112141204.45646.paul@codesourcery.com> (raw)
In-Reply-To: <CAFEAcA_e4AGwMqzWqiim=Z82ABkPjXUyakiza1D9Zi0CS+YiCQ@mail.gmail.com>
> The proper solution would be to rewrite mmap.c to be smarter (perhaps
> by looking at /proc/self/maps and reserving a lot of space with PROT_NONE
> mappings at startup and then managing it itself), but so far nobody's
> done that
Yes they have. That's what -R does.
We used to try and parse /proc/self/maps. This caused more problems than it
solved. It doesn't cover things like mmap_min_addr, and you have to re-parse
it before every allocation in case the host libc allocated something new in
between.
Paul
next prev parent reply other threads:[~2011-12-14 12:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 21:36 [Qemu-devel] [PATCH] PPC: Fix linker scripts on ppc hosts Alexander Graf
2011-12-13 0:55 ` Richard Henderson
2011-12-13 1:05 ` Alexander Graf
2011-12-13 6:19 ` Paul Brook
2011-12-13 7:45 ` Alexander Graf
2011-12-13 16:31 ` Paul Brook
2011-12-13 21:59 ` Alexander Graf
2011-12-14 0:30 ` Paul Brook
2011-12-14 1:43 ` Alexander Graf
2011-12-14 2:24 ` Paul Brook
2011-12-20 16:17 ` Peter Maydell
2011-12-20 16:29 ` Alexander Graf
2011-12-20 16:33 ` Peter Maydell
2011-12-20 16:43 ` Alexander Graf
2011-12-14 8:53 ` Peter Maydell
2011-12-14 12:04 ` Paul Brook [this message]
2011-12-14 12:21 ` Peter Maydell
2011-12-14 17:34 ` Paul Brook
2011-12-13 8:13 ` Peter Maydell
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=201112141204.45646.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=agraf@suse.de \
--cc=dvaleev@suse.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=rth@twiddle.net \
/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.