[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..
Linus Torvalds wrote:
> On Thu, 7 Aug 2008, H. Peter Anvin wrote:
>> The only way I can see around that, though, is to move the 1:1 mapping base up
>> by 2/4 MB (for PAE/no PAE, respectively) and put the fixmap area there. Kind
>> of sucks, but would be doable.
> So if the address isn't fixed, you'll end up with an indirect pointer, and
> it would likely be much better to just use a fixed direct pointer that is
> not at the top.
> And anything that is within the top 31 bits of the address space should
> generate the same good code, since the fixed offset is always going to be
> a 32-bit thing anyway. So moving the FIXMAP area down by 4MB sounds like a
> fine thing to do with no real downside, if it then means that we don't
> need to move the FIXMAP area at all.
> Hmm? Am I missing something?

Just moving it down by 4 MB doesn't help, since the VMI guys want as
much as 64 MB, which is half the standard vmalloc area and hence too
much address space lost. We can't put it at the bottom of the vmalloc
area, since that boundary is not fixed, either.

The one remaining fixed boundary in the machine is the kernel-userspace
boundary. Hence moving the 1:1 area up by one PDE unit and sticking the
fixmap area in that region.


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