linux-kernel - Re: [patch] bootmem: use MAX_DMA

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060729035523.GA29875@elte.hu>
Date:	Sat, 29 Jul 2006 05:55:23 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT


* Heiko Carstens <heiko.carstens@...ibm.com> wrote:

> Hm... how about this one then:
> 
> From: Heiko Carstens <heiko.carstens@...ibm.com>
> 
> Introduce ARCH_LOW_ADDRESS_LIMIT which can be set per architecture to
> override the 4GB default limit used by the bootmem allocater within
> __alloc_bootmem_low() and __alloc_bootmem_low_node().
> E.g. s390 needs a 2GB limit instead of 4GB.
> 
> Cc: Ingo Molnar <mingo@...e.hu>

Acked-by: Ingo Molnar <mingo@...e.hu>

(although you might get some flak about using an ARCH* define. I'm not 
sure what the current upstream policy is - using an #ifndef default 
value is the most compact hence sanest thing to do, still it's sometimes 
being frowned upon in favor of sprinkling the default value into every 
architecture's processor.h. Putting the value into a Kconfig and 
combining it with #ifndef might be better.)

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