qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Alexander Graf <agraf@suse.de>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Riku Voipio" <riku.voipio@iki.fi>,
	"Paul Brook" <paul@codesourcery.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/9] alpha-linux-user: Work around hosted mmap allocation problems
Date: Tue, 12 Jun 2012 08:27:14 -0700	[thread overview]
Message-ID: <4FD75FD2.4010606@twiddle.net> (raw)
In-Reply-To: <20EB8069-00A3-496E-B4B0-67BC58A67B6E@suse.de>

On 2012-06-12 08:11, Alexander Graf wrote:
> 32G is way too much. Do you have to preallocate such a big address
> space? Usually 1G should be good enough for most programs, no?

The default start to .text is 6G for alpha executables, so anything
less than that + reasonable room will fail for obvious reasons.

One would think that e.g. 8G would be good enough, giving 2G above
the executable for brk and shared library mapping, but... failure.
Alternately, there's some other problem with -R that needs to be
investigated.

That said, problems with ld.so erroring out with ENOMEM went away
with this patch, so...


r~

  reply	other threads:[~2012-06-12 15:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 22:24 [Qemu-devel] [PATCH v3 0/9] {alpha-}linux user improvements Richard Henderson
2012-06-07 22:24 ` [Qemu-devel] [PATCH 1/9] alpha-linux-user: Fix signal handling Richard Henderson
2012-06-22 14:10   ` Peter Maydell
2012-06-07 22:24 ` [Qemu-devel] [PATCH 2/9] alpha-linux-user: Work around hosted mmap allocation problems Richard Henderson
2012-06-12 14:12   ` Andreas Färber
2012-06-12 14:27     ` Richard Henderson
2012-06-12 14:53       ` Alexander Graf
2012-06-12 14:57         ` Richard Henderson
2012-06-12 15:11           ` Alexander Graf
2012-06-12 15:27             ` Richard Henderson [this message]
2012-06-07 22:24 ` [Qemu-devel] [PATCH 3/9] alpha-linux-user: Handle TARGET_SSI_IEEE_RAISE_EXCEPTION properly Richard Henderson
2012-06-07 22:24 ` [Qemu-devel] [PATCH 4/9] linux-user: Handle O_SYNC, O_NOATIME, O_CLOEXEC, O_PATH Richard Henderson
2012-06-22 14:15   ` Peter Maydell
2012-06-07 22:24 ` [Qemu-devel] [PATCH 5/9] linux-user: Allocate the right amount of space for non-fixed file maps Richard Henderson
2012-06-07 22:24 ` [Qemu-devel] [PATCH 6/9] linux-user: Translate pipe2 flags; add to strace Richard Henderson
2012-06-22 14:18   ` Peter Maydell
2012-06-07 22:24 ` [Qemu-devel] [PATCH 7/9] alpha-linux-user: Fix a3 error return with v0 error bypass Richard Henderson
2012-06-07 22:24 ` [Qemu-devel] [PATCH 8/9] alpha-linux-user: Properly handle the non-rt sigprocmask syscall Richard Henderson
2012-06-22 14:27   ` Peter Maydell
2012-06-07 22:24 ` [Qemu-devel] [PATCH 9/9] alpha-linux-user: Fix the getpriority syscall Richard Henderson
2012-06-12 13:48 ` [Qemu-devel] [PATCH v3 0/9] {alpha-}linux user improvements Richard Henderson

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=4FD75FD2.4010606@twiddle.net \
    --to=rth@twiddle.net \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=paul@codesourcery.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).