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: Tue, 6 Oct 2015 16:10:36 +0200 From: Christophe Leroy <christophe.leroy@....fr> To: Scott Wood <scottwood@...escale.com> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>, Paul Mackerras <paulus@...ba.org>, Michael Ellerman <mpe@...erman.id.au>, linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org Subject: Re: [PATCH v2 11/25] powerpc/8xx: map 16M RAM at startup Le 29/09/2015 01:58, Scott Wood a écrit : > On Tue, Sep 22, 2015 at 06:50:50PM +0200, Christophe Leroy wrote: >> On recent kernels, with some debug options like for instance >> CONFIG_LOCKDEP, the BSS requires more than 8M memory, allthough >> the kernel code fits in the first 8M. >> Today, it is necessary to activate CONFIG_PIN_TLB to get more than 8M >> at startup, allthough pinning TLB is not necessary for that. >> >> This patch adds a second 8M page to the initial mapping in order to >> have 16M mapped regardless of CONFIG_PIN_TLB, like several other >> 32 bits PPC (40x, 601, ...) >> >> Signed-off-by: Christophe Leroy <christophe.leroy@....fr> >> --- > Is the assumption that nobody is still running 8xx systems with only 8 > MiB RAM on current kernels? > > No, setup_initial_memory_limit() limits the memory to the minimum between 16M and the real memory size, so if a platform has only 8M, it will still be limited to 8M even with 16M mapped. Christophe -- 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