H. Peter Anvin
hpa at zytor.com
Wed Apr 13 15:11:25 PDT 2011
On 04/13/2011 02:59 PM, Yinghai Lu wrote:
> On 04/13/2011 02:50 PM, Joerg Roedel wrote:
>> On Wed, Apr 13, 2011 at 01:48:48PM -0700, Yinghai Lu wrote:
>>> - addr = memblock_find_in_range(0, 1ULL<<32, aper_size, 512ULL<<20);
>>> + addr = memblock_find_in_range(0, 1ULL<<32, aper_size, 512ULL<<21);
>> Btw, while looking at this code I wondered why the 512M goal is enforced
>> by the alignment. Start could be set to 512M instead and the alignment
>> can be aper_size as it should. Any reason for such a big alignment?
> when using bootmem, try to use big alignment (512M ), so we could avoid take ram range below 512M.
Yes, his question was why on Earth are you using 0 as start if that is
On top of that, where the hell does the magic 512 MiB come from? It
looks like it is either completly ad hoc, or it has something to do with
where the kexec kernel was allocated once upon a time.
More information about the dri-devel