From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 07:06:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F61816A423 for ; Wed, 24 May 2006 07:06:12 +0000 (UTC) (envelope-from tyler@tamu.edu) Received: from smtp-relay.tamu.edu (smtp-relay.tamu.edu [165.91.22.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A27243D4C for ; Wed, 24 May 2006 07:06:02 +0000 (GMT) (envelope-from tyler@tamu.edu) Received: from [192.168.250.100] (24-240-208-83.dhcp.sprn.tx.charter.com [24.240.208.83]) (authenticated bits=0) by smtp-relay.tamu.edu (8.13.6/8.13.3/oc) with ESMTP id k4O76EfY096542 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Wed, 24 May 2006 02:06:27 -0500 (CDT) (envelope-from tyler@tamu.edu) Mime-Version: 1.0 (Apple Message framework v750) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: FreeBSD Hackers From: "R. Tyler Ballance" Date: Wed, 24 May 2006 02:05:33 -0500 X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.750) Received-SPF: pass (smtp-relay.tamu.edu: 24.240.208.83 is authenticated by a trusted mechanism) Subject: Kernel call stack for dummies. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 07:06:19 -0000 -----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-----