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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 26 Nov 2017 13:18:13 +0000 From: Russell King - ARM Linux <linux@...linux.org.uk> To: Peng Fan <peng.fan@....com> Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, van.freenix@...il.com, Mark Rutland <mark.rutland@....com>, Thomas Gleixner <tglx@...utronix.de>, Chris Brandt <chris.brandt@...esas.com>, Will Deacon <will.deacon@....com> Subject: Re: [PATCH] arm: l2c: unlock ways when in non-secure mode On Sun, Nov 26, 2017 at 08:25:30PM +0800, Peng Fan wrote: > To boot Linux in Non-secure mode with l2x0, the l2x0 controller > is enabled in secure mode and ways locked to make it seems L2 cache > disabled during linux boot process. So during l2x0 initialization, > need to unlock the ways to make l2x0 could cache data/inst. Why was this chosen instead of doing what everyone else does? -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up According to speedtest.net: 8.21Mbps down 510kbps up
Powered by blists - more mailing lists