From owner-freebsd-smp Fri Sep 13 12:00:25 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08840 for smp-outgoing; Fri, 13 Sep 1996 12:00:25 -0700 (PDT) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA08832 for ; Fri, 13 Sep 1996 12:00:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id NAA26181; Fri, 13 Sep 1996 13:00:17 -0600 Message-Id: <199609131900.NAA26181@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: freebsd-smp@freebsd.org cc: peter@spinner.dialix.com Subject: writing new apic_startup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Sep 1996 13:00:16 -0600 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm starting to re-code apic_startup() armed with the knowqledge we've gained the last several days. One of the things I want to do is use real timing loops. Is there a kernel facility available at the point apic_startup() is called (middle of init386() in machdep.c) that will give me blocking delays in the order of 10 usec to 10 msec? Failing that does anyone see any reason why I shouldn't use the APIC timer? Is it currently used on the boot CPU for anything else? -- Steve Passe | powered by smp@csn.net | FreeBSD