From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 29 Aug 2012 13:42:58 +1000 From: David Gibson To: madper Subject: Re: The MAX high_addr for `mmap` on PPC64 Message-ID: <20120829034258.GF5723@truffula.fritz.box> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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