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
| ||
|
Date: Wed, 12 Sep 2012 15:56:24 -0500 From: Rob Herring <robherring2@...il.com> To: Nicolas Pitre <nicolas.pitre@...aro.org> CC: Cyril Chemparathy <cyril@...com>, devicetree-discuss@...ts.ozlabs.org, linux-arm-kernel@...ts.infradead.org, linux-c6x-dev@...ux-c6x.org, linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org, linux@...nrisc.net, linuxppc-dev@...ts.ozlabs.org, microblaze-uclinux@...e.uq.edu.au, x86@...nel.org, david.daney@...ium.com, benh@...nel.crashing.org, bigeasy@...utronix.de, grant.likely@...retlab.ca, paul.gortmaker@...driver.com, paulus@...ba.org, hpa@...or.com, m.szyprowski@...sung.com, jonas@...thpole.se, linux@....linux.org.uk, a-jacquiot@...com, mingo@...hat.com, suzuki@...ibm.com, mahesh@...ux.vnet.ibm.com, linus.walleij@...aro.org, arnd@...db.de, msalter@...hat.com, rob.herring@...xeda.com, tglx@...utronix.de, blogic@...nwrt.org, dhowells@...hat.com, monstr@...str.eu, ralf@...ux-mips.org, tj@...nel.org Subject: Re: [PATCH] of: specify initrd location using 64-bit On 09/12/2012 03:31 PM, Nicolas Pitre wrote: > On Wed, 12 Sep 2012, Rob Herring wrote: > >> On 09/12/2012 11:05 AM, Cyril Chemparathy wrote: >>> On some PAE architectures, the entire range of physical memory could reside >>> outside the 32-bit limit. These systems need the ability to specify the >>> initrd location using 64-bit numbers. >>> >>> This patch globally modifies the early_init_dt_setup_initrd_arch() function to >>> use 64-bit numbers instead of the current unsigned long. >> >> S-o-B? >> >>> --- >>> arch/arm/mm/init.c | 2 +- >>> arch/c6x/kernel/devicetree.c | 3 +-- >>> arch/microblaze/kernel/prom.c | 3 +-- >>> arch/mips/kernel/prom.c | 3 +-- >>> arch/openrisc/kernel/prom.c | 3 +-- >>> arch/powerpc/kernel/prom.c | 3 +-- >>> arch/x86/kernel/devicetree.c | 3 +-- >>> drivers/of/fdt.c | 10 ++++++---- >>> include/linux/of_fdt.h | 3 +-- >>> 9 files changed, 14 insertions(+), 19 deletions(-) >>> >>> diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c >>> index ad722f1..579792c 100644 >>> --- a/arch/arm/mm/init.c >>> +++ b/arch/arm/mm/init.c >>> @@ -76,7 +76,7 @@ static int __init parse_tag_initrd2(const struct tag *tag) >>> __tagtable(ATAG_INITRD2, parse_tag_initrd2); >>> >>> #ifdef CONFIG_OF_FLATTREE >>> -void __init early_init_dt_setup_initrd_arch(unsigned long start, unsigned long end) >>> +void __init early_init_dt_setup_initrd_arch(u64 start, u64 end) >> >> phys_initrd_start/size need to change too. Not sure about similar things >> on other arches. > > size ? phys_initrd_size. Arguably, we'll never have a >4GB initrd with a PAE system or perhaps run into other issues first (like space to decompress it), but technically the DTS could specify one. Rob -- 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