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 -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
