> What you want really is a 64-bit kernel. On a 64-bit kernel even for
> processes running in 32-bit address spaces (o32, N32) the processor
> will run with the UX bit enabled. o32 userspace still lives in the
> assumption that registers are 32-bit so only those bits will
> be restored
> in function calls etc. N32 (where userspace isn't ready for
> prime time
> yet) does guarantee that. And N64 (userspace similarly not ready for
> prime time) obviously is fully 64-bit everything.
What is the page table space impact of a 64 bit kernel on an architecture like
the Sibyte with discontiguous physical address spaces? Do you still waste 36
MB of page table space on the "hole", or does it even double because the page
table entries are bigger for the wider addresses? Or do the issues become
irrelevant with the larger address space?