From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM
Date: Mon, 5 Aug 2013 11:47:52 -0400 [thread overview]
Message-ID: <51FFC928.8020603@ti.com> (raw)
In-Reply-To: <20130805153822.GD19631@mtj.dyndns.org>
On Monday 05 August 2013 11:38 AM, Tejun Heo wrote:
> Hello,
>
> On Mon, Aug 05, 2013 at 11:29:46AM -0400, Santosh Shilimkar wrote:
>> So looks like I am bit confused here. The current memblock_alloc()
>> API just returns the physical address which not mapped memory.
>
> The memory returned by memblock is mapped if the memory area being
> allocated can be mappable. To access, the address just needs to be
> converted to va.
>
>> Most of the bootmem users including core code expects the
>> mapped memory pointer which the code can directly operate on.
>> So the current memblock_alloc() isn't going to help. The nobootmem.c
>> has __alloc_memory_core_early() which is actually used by most of
>> the bootmem wrappers to achieve the same. So my assumption was
>> that we need an equivalent exported memblock API.
>>
>> What am I missing?
>
> Oh, you weren't. I was. I thought we already had full interface
> implemented. Yeah, it looks like we need to build something new
> around memblock / __alloc_memory_core_early().
>
Exactly. This is what actually I referred as the new API.
Regards,
Santosh
prev parent reply other threads:[~2013-08-05 15:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 1:01 [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM Santosh Shilimkar
2013-06-29 15:29 ` Tejun Heo
2013-06-29 17:21 ` Russell King - ARM Linux
2013-06-29 17:57 ` Tejun Heo
2013-06-29 18:23 ` H. Peter Anvin
2013-06-29 19:29 ` Yinghai Lu
2013-06-29 19:55 ` Russell King - ARM Linux
2013-06-29 20:08 ` Yinghai Lu
2013-07-01 14:10 ` Santosh Shilimkar
2013-07-25 22:33 ` Santosh Shilimkar
2013-07-25 22:36 ` Tejun Heo
2013-07-25 23:15 ` Santosh Shilimkar
2013-07-26 3:08 ` Tejun Heo
2013-08-02 21:06 ` Santosh Shilimkar
2013-08-05 15:01 ` Tejun Heo
2013-08-05 15:29 ` Santosh Shilimkar
2013-08-05 15:38 ` Tejun Heo
2013-08-05 15:47 ` Santosh Shilimkar [this message]
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=51FFC928.8020603@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).