From: David Gibson <david@gibson.dropbear.id.au>
To: madper <cxie@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: The MAX high_addr for `mmap` on PPC64
Date: Wed, 29 Aug 2012 13:42:58 +1000 [thread overview]
Message-ID: <20120829034258.GF5723@truffula.fritz.box> (raw)
In-Reply-To: <op.wjr9i6t4xxpu98@localhost.localdomain>
On Wed, Aug 29, 2012 at 11:34:08AM +0800, madper wrote:
> Hi every one,
> I use the ltp (Linux-Test-Project) and run it on both ppc64 and x86_64.
> There is a code like follows in
> `ltp/testcase/kernel/mem/hugetbl/hugemmap/hugemmap03.c`:
> `code`
> #define HIGH_ADDR (void *)(0x1000000000000)
> /* Attempt to mmap into highmem addr, should get ENOMEM */
> addr = mmap(HIGH_ADDR, map_sz, PROT_READ,
> MAP_SHARED | MAP_FIXED, fildes, 0);
> `code ends`
> It return ENOMEM on x86_64 as well as we expected. But return
> EINVAL on ppc64. So I want to know the MAX high addr for PPC64.
That's a pretty bogus test, since the max address is not specified
strictly. It's currently 4T on ppc64, but patches that are in the
works will change it to 16T.
Also I'm not convinced that "highmem addr" has any meaning in the
context of userspace addresses.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-08-29 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 3:34 The MAX high_addr for `mmap` on PPC64 madper
2012-08-29 3:42 ` David Gibson [this message]
2012-08-29 3:57 ` madper
2012-08-29 23:39 ` David Gibson
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=20120829034258.GF5723@truffula.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=cxie@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.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).