From owner-freebsd-smp Mon Aug 30 23: 9:43 1999 Delivered-To: freebsd-smp@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 0565F15108 for ; Mon, 30 Aug 1999 23:09:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA02907; Mon, 30 Aug 1999 23:03:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908310603.XAA02907@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Neil Bradley" Cc: smp@freebsd.org Subject: Re: BIOS calls on SMP systems In-reply-to: Your message of "Mon, 30 Aug 1999 23:02:47 PDT." <02d601bef376$74434a10$076291c6@Engineering.retrocade.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Aug 1999 23:03:13 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Ok, so the baseline answer is "only the BSP can reliably call the BIOS". > > Correct - but with a "depends" attached to it. What interrupt services are > you calling? At the moment, the PnP, APM and SMB BIOS APIs. We will probably end up calling the PCI BIOS. > > Correct there? If so, I have some interesting tunneling work to do... > > Yes, but it depends upon what services you want to call in the BIOS. ON > second thought, even doing 32 bit PCI function calls won't be safe because > of the access to 0xcf8/0xcfc for configuration access. > > In other words, I wouldn't use the AP's to call BIOS services. Ok, thanks. More fun. 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message