[lkml]   [2012]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Initialize max_pfn_mapped as initial ident mapping size for x86_64
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.


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

 \ /
  Last update: 2012-03-06 08:03    [W:0.036 / U:2.068 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site