> >Kernel space in BeOS is > >0x00000000-0x80000000, user space is above 0x80000000. > > How awful... doesn't that make vm86 impossible ? Hmm, from our perspective the Linux memory map is awful ;-) It duplicates the Windows one :) I would be interested to know whether it makes virtualization impossible. I would say that it does not - as far as I understand, the guest is not supposed to *ever* see the host addresses. Nothing prevents plex86 from making the guest believe that 0x90000000 is actually 0x1000000... Opinions are welcome. In fact, a checklist of OS features that plex86 requires so far would be much welcome. Any volunteer ? > >Yes, this is reversed from Windows/Linux. Kinda killed the > >BeWine project, in fact ;-) > > Yes it would, I guess ;) > Haven't the BeWine developers asked Be to change this ? (of course, that > would give problems with existing binaries...) Well, reversing your memory map isn't exactly a trivial operation ;-) The binaries could always be run-time remapped, in theory. But I'm sure a few things depend on the memory map somewhere... Cheers, --Jonathan
