lkml.org 
[lkml]   [1998]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Problem with 1G RAM
Date
> 
> the problem with this is that x86 CISC instructions are inherently more
> difficult to fix up runtime :(

In what sense? I mean the linker is able to resolve it, so why should
BTFIXUP not be able to do the same? I think there are just few i386
relocation types, far less than on sparc.
And BTFIXUP really works that way:
on Intel, you'd
#define PAGE_OFFSET (&__nonexistant_page_offset_object)
then partially link the kernel (you'll get a bunch of undefined relocations
to the __npoo). Then, you just record all the places where such undefined
relocation happens, in the linker script define
__nonexistant_page_offset_object to 0xC0000000 and link again.
At runtime you just relocate what you've recorded. I think there will be at
most two different reloc types for it, if not only one, so it will be really
easy.

Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.130 on a sparc64 machine (3958.37 BogoMips)
___________________________________________________________________

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

\
 
 \ /
  Last update: 2005-03-22 13:45    [W:2.098 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site