From: Cyril Chemparathy <cyril@ti.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, davem@davemloft.net,
eric.dumazet@gmail.com, hannes@cmpxchg.org,
shangw@linux.vnet.ibm.com, vitalya@ti.com
Subject: Re: [PATCH] mm: bootmem: use phys_addr_t for physical addresses
Date: Wed, 12 Sep 2012 20:08:30 -0400 [thread overview]
Message-ID: <505123FE.2090305@ti.com> (raw)
In-Reply-To: <20120912203920.GU7677@google.com>
Hi Tejun,
On 9/12/2012 4:39 PM, Tejun Heo wrote:
> Hello,
>
> On Wed, Sep 12, 2012 at 12:06:48PM -0400, Cyril Chemparathy wrote:
>> static void * __init alloc_bootmem_core(unsigned long size,
>> unsigned long align,
>> - unsigned long goal,
>> - unsigned long limit)
>> + phys_addr_t goal,
>> + phys_addr_t limit)
>
> So, a function which takes phys_addr_t for goal and limit but returns
> void * doesn't make much sense unless the function creates directly
> addressable mapping somewhere.
>
On the 32-bit PAE platform in question, physical memory is located
outside the 4GB range. Therefore phys_to_virt takes a 64-bit physical
address and returns a 32-bit kernel mapped lowmem pointer.
> The right thing to do would be converting to nobootmem (ie. memblock)
> and use the memblock interface. Have no idea at all whether that
> would be a realistic short-term solution for arm.
>
I must plead ignorance and let wiser souls chime in on ARM architecture
plans w.r.t. nobootmem. As far as I can tell, the only thing that
blocks us from using nobootmem at present is the need for sparsemem on
some platforms.
--
Thanks
- Cyril
--
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:[~2012-09-13 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 16:06 [PATCH] mm: bootmem: use phys_addr_t for physical addresses Cyril Chemparathy
2012-09-12 20:39 ` Tejun Heo
2012-09-13 0:08 ` Cyril Chemparathy [this message]
2012-09-13 0:34 ` Tejun Heo
2012-09-13 0:40 ` Cyril Chemparathy
2012-09-13 19:32 ` Tejun Heo
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=505123FE.2090305@ti.com \
--to=cyril@ti.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shangw@linux.vnet.ibm.com \
--cc=tj@kernel.org \
--cc=vitalya@ti.com \
/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).