From: Richard Henderson <rth@twiddle.net>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Alexander Graf <agraf@suse.de>, Riku Voipio <riku.voipio@iki.fi>,
Paul Brook <paul@codesourcery.com>,
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 07:27:54 -0700 [thread overview]
Message-ID: <4FD751EA.2070501@twiddle.net> (raw)
In-Reply-To: <4FD74E32.7000705@suse.de>
On 2012-06-12 07:12, Andreas Färber wrote:
> This looks fishy to me... why should the kernel use a bigger address
> space than hardware? For arm on x86_64 such a workaround was not
> necessary iirc.
I can tell you what I observe. That with a certain sequence of
allocations the x86_64 kernel will quit accepting an address "near"
(1<<38) as a hint for where to allocate memory and begin returning
an addresses near (1<<48). Further, the logic in find_mmap_vma tries
about 5 times (with different hints) to get a target-page-aligned
address at a lower address, all of which fail: the kernel continues
to return the (1<<48) address. At which point one wonders why we
should keep refusing the (1<<48) address when the target is in fact
64-bit capable.
I believe the host vs target page size difference plays a part in
this, which is why you wouldn't see this on arm.
All of the other targets with page size larger than 4k are 64 bit,
and set TARGET_VIRT_ADDR_SPACE_BITS to 64. So Alpha was unique in
being an 8k page size with T_B_A_S_B < 48, and so probably unique
in being able to tickle this problem.
r~
next prev parent reply other threads:[~2012-06-12 14:28 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 [this message]
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
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=4FD751EA.2070501@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 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.