From: Thayne Harbaugh <thayne@c2.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, discuss@x86-64.org
Subject: Re: [PATCH] Inconsistent mmap()/mremap() flags
Date: Tue, 02 Oct 2007 01:06:12 -0600 [thread overview]
Message-ID: <1191308772.5200.66.camel@phantasm.home.enterpriseandprosperity.com> (raw)
In-Reply-To: <20071002051526.GA29615@one.firstfloor.org>
On Tue, 2007-10-02 at 07:15 +0200, Andi Kleen wrote:
> On Mon, Oct 01, 2007 at 08:57:10PM -0600, Thayne Harbaugh wrote:
> For mmap you can emulate it by passing a low hint != 0 (e.g. getpagesize())
> in address but without MAP_FIXED and checking if the result is not beyond
> your range.
Cool. That's a much better solution for multiple reasons - like you
mention, MAP_32BIT is only 2GB as well as it's only available on x86_64.
> > > Given for mremap() it is not that easy because there is no "hint" argument
> > > without MREMAP_FIXED; but unless someone really needs it i would prefer
> > > to not propagate the hack. If it's really needed it's probably better
> > > to implement a start search hint for mremap()
> >
> > It came up for user-mode Qemu for the case of emulating 32bit archs on
> > x86_64 using mmap. At the moment it calls mmap with MAP_32BIT and then
>
> That would limit the 32bit architectures to 2GB; but their real limit
> is 4GB. Losing half of the address space definitely would make users unhappy
> (e.g. at least normal Linux kernels wouldn't run at all)
Keeping a kernel happy isn't necessary since it's user-space emulation
rather than full emulation. It is, however, useful to have 4GB rather
than 2GB.
> Does qemu actually need mremap() ? It would surprise me because
> a lot of other OS don't implement it.
Qemu has two modes: full hardware emulation and user-mode emulation.
User-mode emulation translates the user-mode code and then remaps the
system calls directly into the native kernel (that way all the kernel
and all the I/O runs natively and faster). As far as mremap(), I'm
trying to get a 32bit arm mremap() emulated syscall mapped onto a 64bit
x86_64 mremap().
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-10-02 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 5:46 [PATCH] Inconsistent mmap()/mremap() flags Thayne Harbaugh
2007-10-01 11:13 ` Andi Kleen
2007-10-02 2:57 ` Thayne Harbaugh
2007-10-02 5:15 ` Andi Kleen
2007-10-02 7:06 ` Thayne Harbaugh [this message]
2007-10-02 12:19 ` Hugh Dickins
2007-10-02 13:45 ` [discuss] " Andi Kleen
2007-10-02 14:16 ` Hugh Dickins
2007-10-02 15:21 ` Thayne Harbaugh
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=1191308772.5200.66.camel@phantasm.home.enterpriseandprosperity.com \
--to=thayne@c2.net \
--cc=andi@firstfloor.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).