Date: Wed, 24 May 2006 02:05:33 -0500 From: "R. Tyler Ballance" <tyler@tamu.edu> To: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Kernel call stack for dummies. Message-ID: <EC9C1F8D-C609-49D7-ACA4-559415149BD6@tamu.edu>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've started the uphill battle to port FreeBSD's kernel to run "paravirtualized" (<--note the smart sounding vocabulary) on top of the L4/Iguana OS (Iguana is a very barebones OS developed by NICTA: http://www.ertos.nicta.com.au/software/kenge/iguana-project/latest/) On of the first steps is basically porting the lowest of low kernel calls such as those in sys/i386 sys/arm and sys/amd64 for example into sys/iguana to talk to iguana instead of actual hardware. One of the things I need to figure out is the order in which kernel calls are made on boot, so I can go through and reimplement them one by one (in order to spend as little time as possible going back and fixing other problems of mine), as suggested by Ben Leslie at NICTA. Is there a good overview of what's happening directly after boot in terms of the procedure in which functions are called right after the bootloader finishes it business? Cheers, - -R. Tyler Ballance -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEdAW/qO6nEJfroRsRAgMUAJ93K5wwRRXljCkgx8SaU0fdgN3l3gCgkuqA S/BC67a7O1KuQzvnsvZUAvc= =PQtC -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC9C1F8D-C609-49D7-ACA4-559415149BD6>