Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754136Ab3HEPim (ORCPT ); Mon, 5 Aug 2013 11:38:42 -0400 Received: from mail-qe0-f49.google.com ([209.85.128.49]:37475 "EHLO mail-qe0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753106Ab3HEPij (ORCPT ); Mon, 5 Aug 2013 11:38:39 -0400 Date: Mon, 5 Aug 2013 11:38:22 -0400 From: Tejun Heo To: Santosh Shilimkar Cc: Yinghai Lu , Russell King - ARM Linux , linux-arm-kernel@lists.infradead.org, Linux Kernel Mailing List , Catalin Marinas , Will Deacon , Nicolas Pitre , Ingo Molnar , Andrew Morton , "H. Peter Anvin" , Benjamin Herrenschmidt , Paul Mackerras , "David S. Miller" , "sparclinux@vger.kernel.org" , Sam Ravnborg , linux-arch@vger.kernel.org Subject: Re: [PATCH] WIP: HACK: LPAE, BOOTMEM and NO_BOOTMEM Message-ID: <20130805153822.GD19631@mtj.dyndns.org> References: <20130629195549.GE3353@n2100.arm.linux.org.uk> <51D18DBA.6090608@ti.com> <51F1A7AA.8080700@ti.com> <20130725223658.GJ26107@mtj.dyndns.org> <51F1B17F.30902@ti.com> <20130726030812.GB30195@mtj.dyndns.org> <51FC1F3A.8090201@ti.com> <20130805150127.GC19631@mtj.dyndns.org> <51FFC4EA.40908@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51FFC4EA.40908@ti.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1211 Lines: 32 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(). Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/