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, 08 Feb 2012 14:30:02 +0100
From:	Marek Szyprowski <m.szyprowski@...sung.com>
To:	monstr@...str.eu,
	'Russell King - ARM Linux' <linux@....linux.org.uk>
Cc:	'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

Hello,

On Wednesday, February 08, 2012 2:21 PM Michal Simek wrote:

> Russell King - ARM Linux wrote:
> > On Wed, Feb 08, 2012 at 01:27:58PM +0100, Michal Simek wrote:
> >> Hi,
> >>
> >> I would like to setup CMA space at the beginning of ram because
> >> I want to use remoteproc to run code on the second cpu which has to
> >> use addresses 0x0 - 32MB.
> >>
> >> I have changed textofs in arch/arm/Makefile but there is not possible
> >> to setup all values which I would like to use.
> >
> > What a broken setup.  Placing the kernel outside of the 16MB window
> > effectively prevents you from using modules.  Why do people come up
> > with stupid things like this.  Please stop.  Put such things at the
> > end of RAM instead and save the rest of the ARM community from this
> > madness.
> 
> First of all I have found how to do it (by CONFIG_PHYS_OFFSET) so the problem is in QEMU.
> Currently experimenting how to convince CMA to allocate that memory for my purpose.

I'm not sure if CMA is the right allocation api for this purpose. You should
better use memblock allocator to grab specific address ranges for your custom 
setup. Alternatively you can compile Linux kernel to start physical memory 
at 16MiB and access the 0-16MiB range with ioremap for example.

(snipped)

Best regards
-- 
Marek Szyprowski
Samsung Poland R&D Center


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ