linux-kernel - Re: [PATCHv4 2/2] arm: Get rid of meminfo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 12 Mar 2014 15:09:53 +0200
From:	Grygorii Strashko <grygorii.strashko@...com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Laura Abbott <lauraa@...eaurora.org>
CC:	David Brown <davidb@...eaurora.org>,
	Daniel Walker <dwalker@...o99.com>,
	Jason Cooper <jason@...edaemon.net>,
	Andrew Lunn <andrew@...n.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Eric Miao <eric.y.miao@...il.com>,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	Ben Dooks <ben-linux@...ff.org>,
	Kukjin Kim <kgene.kim@...sung.com>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
	Leif Lindholm <leif.lindholm@...aro.org>,
	Catalin Marinas <catalin.marinas@....com>,
	Rob Herring <robherring2@...il.com>,
	Ard Biesheuvel <ard.biesheuvel@...aro.org>,
	Will Deacon <will.deacon@....com>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Santosh Shilimkar <santosh.shilimkar@...com>,
	<linux-mm@...ck.org>, Andrew Morton <akpm@...ux-foundation.org>,
	Courtney Cavin <courtney.cavin@...ymobile.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCHv4 2/2] arm: Get rid of meminfo

Hi Russell,

On 03/12/2014 10:54 AM, Russell King - ARM Linux wrote:
> On Tue, Feb 18, 2014 at 02:15:33PM -0800, Laura Abbott wrote:
>> memblock is now fully integrated into the kernel and is the prefered
>> method for tracking memory. Rather than reinvent the wheel with
>> meminfo, migrate to using memblock directly instead of meminfo as
>> an intermediate.
>>
>> Acked-by: Jason Cooper <jason@...edaemon.net>
>> Acked-by: Catalin Marinas <catalin.marinas@....com>
>> Acked-by: Santosh Shilimkar <santosh.shilimkar@...com>
>> Acked-by: Kukjin Kim <kgene.kim@...sung.com>
>> Tested-by: Marek Szyprowski <m.szyprowski@...sung.com>
>> Tested-by: Leif Lindholm <leif.lindholm@...aro.org>
>> Signed-off-by: Laura Abbott <lauraa@...eaurora.org>
>
> Laura,
>
> This patch causes a bunch of platforms to no longer boot - imx6solo with
> 1GB of RAM boots, imx6q with 2GB of RAM doesn't.  Versatile Express doesn't.
>
> The early printk messages don't reveal anything too interesting:
>
> Booting Linux on physical CPU 0x0
> Linux version 3.14.0-rc6+ (rmk@...-PC.arm.linux.org.uk) (gcc version 4.6.4 (GCC) ) #630 SMP Wed Mar 12 01:13:36 GMT 2014
> CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
> CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
> Machine model: SolidRun Cubox-i Dual/Quad
> cma: CMA: reserved 64 MiB at 8c000000
> Memory policy: Data cache writealloc
> <hang>
>
> vs.
>
> Booting Linux on physical CPU 0x0
> Linux version 3.14.0-rc6+ (rmk@...-PC.arm.linux.org.uk) (gcc version 4.6.4 (GCC) ) #631 SMP Wed Mar 12 01:15:37 GMT 2014
> CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
> CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
> Machine model: SolidRun Cubox-i Dual/Quad
> cma: CMA: reserved 64 MiB at 3b800000
> Memory policy: Data cache writealloc
> On node 0 totalpages: 524288
> free_area_init_node: node 0, pgdat c09d0240, node_mem_map ea7d8000
>    Normal zone: 1520 pages used for memmap
>    Normal zone: 0 pages reserved
>    Normal zone: 194560 pages, LIFO batch:31
>    HighMem zone: 2576 pages used for memmap
>    HighMem zone: 329728 pages, LIFO batch:31
> ...
>
> The only obvious difference is the address of that CMA reservation,
> CMA shouldn't make a difference here - but I suspect that other
> allocations which need to be in lowmem probably aren't.
>

Could it be possible to enable memblock debug by adding "memblock=debug" 
in cmdline?

Regards,
-grygorii


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/