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/