[lkml]   [2008]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH]Fix broken VMI in 2.6.27-rc..
Zachary Amsden wrote:
>> Okay, you lost me about halfway through that... could you perhaps
>> describe the problem from the beginning, exactly what you're trying to do?
> A kernel compiled with VMI enabled may run on a non-VMI platform. If
> that is the case, the fixmap should not be relocated. If however, a VMI
> ROM is found, we need to hijack up to 64-MB of linear address space from
> the top of memory down. This means moving the fixmap down by the same
> amount.

I take it there are no alternatives other than putting this at the end
of memory?

> Right now the code is structured in such a way that it wants to know how
> much physical memory there is, so it can register a mapping table for
> mapping linear addresses in the lowmem area to physical addresses. This
> causes the code to depend on max_low_pfn being initialized, which
> accounts for the current placement.
> But it also must be called before anything that creates the fixmap,
> because the same code which registers the linear address mapping also
> reserves high memory above the fixmap.
> My point is 1) these could be two separate calls, or 2) the lowmem
> mapping table need not depend on max_low_pfn at all, it is safe to
> create an extra large mapping which covers all possible lowmem instead
> of the physical ram that is actually available.

Realistically speaking, any (virtual) machine which does *not* have a
full complement of lowmem (i.e. less than 896 MB in the common case)
will not suffer significatly from losing a few megabytes of address space.


 \ /
  Last update: 2008-08-07 23:55    [W:0.080 / U:0.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site