[PATCHv3 0/2] creating non-section aligned lowmem mappings
Hi, I found problems when I reserved non-section aligned memory blocks by the device tree. The problem is that the memblock_set_current_limit() point to the first section aligned memblock in the first place (sanity_check_meminfo), but the memblock may be split into non-section aligned memblocks because the memblock_reserve() calls in arm_memblock_init(). *** BLURB HERE *** Min-Hua Chen (2): arm: fix non-section-aligned low memory mapping arm: use max_lowmem_limit in find_limit() arch/arm/mm/init.c |2 +- arch/arm/mm/mmu.c | 48 ++-- 2 files changed, 15 insertions(+), 35 deletions(-) -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCHv3 0/2] creating non-section aligned lowmem mappings
Hi, I found problems when I reserved non-section aligned memory blocks by the device tree. The problem is that the memblock_set_current_limit() point to the first section aligned memblock in the first place (sanity_check_meminfo), but the memblock may be split into non-section aligned memblocks because the memblock_reserve() calls in arm_memblock_init(). *** BLURB HERE *** Min-Hua Chen (2): arm: fix non-section-aligned low memory mapping arm: use max_lowmem_limit in find_limit() arch/arm/mm/init.c |2 +- arch/arm/mm/mmu.c | 48 ++-- 2 files changed, 15 insertions(+), 35 deletions(-) -- 1.7.10.4 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/