From owner-acpi-jp@jp.FreeBSD.org Sat Jul 13 03:17:44 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g6CIHio27517;
	Sat, 13 Jul 2002 03:17:44 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from pallas.or.intel.com (pallas.or.intel.com [134.134.214.21])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g6CIHen27511;
	Sat, 13 Jul 2002 03:17:40 +0900 (JST)
	(envelope-from robert.moore@intel.com)
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by pallas.or.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.42 2002/05/23 22:21:11 root Exp $) with SMTP id g6CIHV712757;
	Fri, 12 Jul 2002 18:17:32 GMT
Received: from orsmsx26.jf.intel.com ([192.168.65.26])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2002071211175503412
 ; Fri, 12 Jul 2002 11:17:55 -0700
Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <3Y0LA2V8>; Fri, 12 Jul 2002 11:17:31 -0700
Message-ID: <B9ECACBD6885D5119ADC00508B68C1EA0D19B63D@orsmsx107.jf.intel.com>
From: "Moore, Robert" <robert.moore@intel.com>
To: "'acpi-jp@jp.FreeBSD.org'" <acpi-jp@jp.FreeBSD.org>,
   Mitsuru IWASAKI
	 <iwasaki@jp.FreeBSD.org>
Cc: "Grover, Andrew" <andrew.grover@intel.com>
Date: Fri, 12 Jul 2002 11:17:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+020713
X-Sequence: acpi-jp 1677
Subject: [acpi-jp 1677] RE: Intel's acpi
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: robert.moore@intel.com


The ACPI Global Lock is a hardware mutex between the ACPI BIOS and the OS.
It cannot be "simulated" with a kernel mutex.

Bob


-----Original Message-----
From: John Baldwin [mailto:jhb@freebsd.org]
Sent: Friday, July 12, 2002 11:09 AM
To: Mitsuru IWASAKI
Cc: andrew.grover@intel.com; acpi-jp@jp.FreeBSD.org
Subject: [acpi-jp 1676] RE: Intel's acpi



On 12-Jul-2002 Mitsuru IWASAKI wrote:
> Hi,
> 
>> > From: Mitsuru IWASAKI [mailto:iwasaki@jp.FreeBSD.org] 
>> > I thought the same thing.  Could you integrate attached diffs and
>> > files into your next snapshot?
>> 
>> No, because I don't think arch-specific headers should be included from
>> acenv.h, but rather from the OS-specific header (e.g. freebsd.h).
>> 
>> Yes it's true, we currently do have both WIN32 and WIN64-specific headers
>> included directly, but I'd like to see us consolidate those, I think.
> 
> Ah, I thought ACPI CA is going that way like having WIN32 and
> WIN64-specific headers.
> *BSD systems have the framework for this purpose.  In arch-specific
> header directory, we can have arch-specific headers and arch-independent
> source files can include them, like;
> 
>#include <machine/acpica_machdep.h>
> 
> i.e. in acfreebsd.h includes sys/i386/include/acpica_machdep.h or
> sys/ia64/include/acpica_machdep.h depending on its machine architecture.
> 
> Sample code attached.  Could you review them?

Why use assembly macros for the ACPI global lock.  Why not just use
a kernel mutex?

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
