From: Santosh Shilimkar
Date: Mon Aug 05 2013 - 11:30:48 EST

On Monday 05 August 2013 11:01 AM, Tejun Heo wrote:
> Hello,
> On Fri, Aug 02, 2013 at 05:06:02PM -0400, Santosh Shilimkar wrote:
>> Looking at the situation, how about proceeding with patch updating
>> the bootmem API signatures to use phys_addr_t which can unblock me
>> to get my machine working.
> I'm not sure about that. No matter how you play it, it'll end up
> duplicating memblock interface.
fair enough.

>> Introduction of new API, conversions of core kernel code and then
> What new API are we talking about? Wasn't the plan to convert core
> kernel code to use memblock and let bootmem emulate bootmem API?
> There's no new API.
So looks like I am bit confused here. The current memblock_alloc()
API just returns the physical address which not mapped memory.
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?

>> arches moving away from bootmem is going to take significant time
> And arches moving away from bootmem doesn't have to happen now.
I agree. The core code conversion is more of an issue.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at