linux-kernel - Re: arm: CONFIG_ARM_PATCH_PHYS

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] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.02.1212071343090.6589@xanadu.home>
Date:	Fri, 7 Dec 2012 13:54:05 -0500 (EST)
From:	Nicolas Pitre <nicolas.pitre@...aro.org>
To:	Gerlando Falauto <gerlando.falauto@...mile.com>
cc:	Sergei Trofimovich <slyich@...il.com>,
	Ian Campbell <ijc@...lion.org.uk>,
	Russell King <rmk+kernel@....linux.org.uk>,
	linux-kernel@...r.kernel.org, Will Deacon <will.deacon@....com>,
	Tony Lindgren <tony@...mide.com>
Subject: Re: arm: CONFIG_ARM_PATCH_PHYS_VIRT=y is broken on kirkwood

On Fri, 7 Dec 2012, Gerlando Falauto wrote:

> Hi everyone,
> 
> On 04/10/2012 08:12 PM, Sergei Trofimovich wrote:
> > On Mon, 09 Apr 2012 22:28:28 +0100
> > Ian Campbell<ijc@...lion.org.uk>  wrote:
> > 
> > > On Sun, 2012-04-08 at 11:59 +0300, Sergei Trofimovich wrote:
> > > > In order to make the box boot I had to set:
> > > >      CONFIG_EMBEDDED=y
> > > >      # CONFIG_ARM_PATCH_PHYS_VIRT is not set
> > > >     CONFIG_PHYS_OFFSET=0x0
> > > > 
> > > > Do you have an idea why it does not boot anymore by default?
> > > 
> > > There is a u-boot commit which fixes this issue:
> > > 
> > > commit 679530278d5a79d34e356ad2d452f4400953bfc2
> > > Author: Michael Walle<[michael@...le.cc]>
> > > Date:   Mon Feb 6 22:42:10 2012 +0530
> > > 
> > >      arm, arm-kirkwood: disable l2c before linux boot
> > > 
> > >      The decompressor expects the L2 cache to be disabled. This fixes
> > > booting
> > >      some kernels, which have CONFIG_ARM_PATCH_PHYS_VIRT enabled.
> > > 
> > >      Signed-off-by: Michael Walle<michael@...le.cc>
> > >      Acked-by: Prafulla Wadaskar<prafulla@...vell.com>
> > >      Cc: Albert ARIBAUD<albert.u.boot@...baud.net>
> > >      Cc: Prafulla Wadaskar<prafulla@...vell.com>
> > >      Cc: Wolfgang Denk<wd@...x.de>
> > 
> > Thank you, Ian. Updating u-boot helped!
> > 
> > Sorry for the noise.
> 
> I guess if updating u-boot is not an option, there's no other way around it
> than disabling CONFIG_ARM_PATCH_PHYS_VIRT altogether.
> 
> Could someone (Russell?) simply state what the consequences are of disabling
> such option? (Or, conversely, what its advantages are?)
> Only reference I found is the original commit, but I couldn't really
> understand what it does (or to what purpose), see at the bottom.

Disabling this option will not do you any harm.  It will prevent your 
kernel binary from being usable on another platform as the physical RAM 
address will then be hardcoded in the compiled kernel, but there are 
still other things that prevents such sharing in this case anyway.

One thing that this option allowed is to remove all the physical RAM 
offset information for most platform out of the source tree.  So to not 
have this option might mean that you might be prompted to provide it at 
kernel configuration time.

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