linux-kernel - Re: CMA on arm from zero address

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, 8 Feb 2012 13:26:22 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Michal Simek <monstr@...str.eu>
Cc:	Marek Szyprowski <m.szyprowski@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Ohad Ben-Cohen <ohad@...ery.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: CMA on arm from zero address

On Wed, Feb 08, 2012 at 02:21:26PM +0100, Michal Simek wrote:
> First of all I have found how to do it (by CONFIG_PHYS_OFFSET) so the
> problem is in QEMU.

So you're basically not telling the kernel about the first 32MB of memory.

> Currently experimenting how to convince CMA to allocate that memory for
> my purpose.

Which means it won't be part of the kernels normal memory map, and so
won't be in the page pool.  So CMA won't be able to help.

Instead, just ignore the first 32MB of RAM, and map it like any other
peripheral to gain access to it.  You might need to use ioremap_wc()
to avoid treating the memory as a 'device type' in ARMv6+.
--
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/