On Thu, Jun 3, 2010 at 9:56 AM, David Given <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I am confused about how the implementation of vfork for non-MMU devices > works. It's late, but I'm pretty sure it *can't* work, and would like to > know if anyone has any non-MMU devices where init starts properly.
Hi David, It does work, we ran without the MMU for a while without issue. I've also booted the arm and i386 ports both with and without the mmu and everything started up ok. At one stage I could have discussed this with you in great detail but my memory of non-MMU operation is fading. I can refresh my memory on this if you would like to discuss details, but fundamentally the structure guarantees only the child or parent is running at any one time and the setjump / longjump restores the context. The calls into the proc and exec servers also do a lot of the heavy lifting behind the scenes. The proc server may actually copy and restore the stack if my memory serves me correctly. Andrew ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Prex-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/prex-devel
