From owner-freebsd-smp Mon Apr 21 11:54:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA06670 for smp-outgoing; Mon, 21 Apr 1997 11:54:29 -0700 (PDT) Received: from uruk.org (root@ns.uruk.org [198.145.95.253]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA06661 for ; Mon, 21 Apr 1997 11:54:25 -0700 (PDT) Received: from uruk.org [127.0.0.1] (erich) by uruk.org with esmtp (Exim 0.53 #1) id E0wJNMB-0007ay-00; Mon, 21 Apr 1997 10:58:27 -0700 To: Steve Passe cc: freebsd-smp@freefall.freebsd.org Subject: Writing APIC document In-reply-to: Your message of "Mon, 21 Apr 1997 12:15:29 MDT." <199704211815.MAA11952@Ilsa.StevesCafe.com> Date: Mon, 21 Apr 1997 10:58:27 -0700 From: Erich Boleyn Message-Id: Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Passe wrote: > One of my top priorities now is to write a whitepaper for the webpage > describe the current (and possible future) inplimentation of the APIC > code, along with all the WHYs of the design. it's fairly arcane, and > even the author (meaning me) forgets why some of the wierder stuff > is in there. (remember all the 'fun' we had getting the AP startup > IPIs working? talk about code that makes no sense at all!!!) I'm working on a similar doc, but it is specifically about the APIC "architecture" (ahem), the important differences and similarities in the implementations, and how they are used in the Intel MP Spec. -- Erich Stefan Boleyn \_ E-mail (preferred): Mad Genius wanna-be, CyberMuffin \__ (finger me for other stats) Web: http://www.uruk.org/~erich/ Motto: "I'll live forever or die trying"