Hello, Cyril. On Wed, Sep 12, 2012 at 08:40:58PM -0400, Cyril Chemparathy wrote: > You probably missed the lowmem bit from my response? > > This system has all of its memory outside the 4GB physical address > space. This includes lowmem, which is permanently mapped into the > kernel virtual address space as usual. Yeah, I understand that and as a short-term solution we maybe can add a check to verify that the goal and limits are under lowmem and fail with NULL if not, but it still is a broken interface and I'd rather not mess with it when memblock is already there. Converting to memblock usually isn't too much work although it expectedly involves some subtleties and fallouts for a while. Do you recall what the problem was with sparsemem and memblock? I don't think I'll directly work on arm but I'll be happy to help on memblock issues. Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>