Re: [PATCH] Initialize max_pfn_mapped as initial ident mapping sizefor x86_64

[H. Peter Anvin]

On 03/05/2012 10:27 PM, Yinghai Lu wrote:
> 
>>
>> The early mapping range we can fix, and probably should.  Mapping the
>> first 4 GiB is not a lot of memory and makes a much more sensible
>> starting point.
> 
> do you mean map the 4G in head_64.S?
> 

Yes.  It would be better to design the mapping system so that it would
incrementally map everything we need (with page tables allocated out of
the memory already mapped), but that isn't a trivial exercise,
especially with the need to avoid the initramfs, kernel image and
command line and other data elements.

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/