On 24.07.2010 21:00, matthew green wrote: >> On 24.07.2010 17:54, Matthias Drochner wrote: >>> >>> c...@cubidou.net said: >>>> Kernel modules, on the other hand... >>> >>> Hmm, didn't think of that. (using them myself only for testing) >>> >>>> a gaping ABI incompatibility is completely unacceptable >>> >>> There are two ways to fix this without the 64-bit-paddr overhead, >>> a short-term and a long-term one. >>> The short-term fix would be to use another module load path. >>> This is close to calling it a different port, but it would >>> not affect userland. >> >> "i386pae" and "i386"? Huh... then we will get i386xenpae, i386xen, and >> so on? > > FWIW, having a different module load path and choosing the right set > of modules is an incoming feature but i have no time line for it. > > i plan for it to be useful for ppc oea vs. 4xx, sparc32 vs sparc64 > in 32 bitmode, and there was someone else wanting it too.
IMHO, it makes sense for these platforms. But here, i386 and PAE are so close in concept that it feels like a quirk (at least to me). -- Jean-Yves Migeon jeanyves.mig...@free.fr
