From owner-acpi-jp@jp.freebsd.org  Wed Oct 18 10:13:59 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id KAA06495;
	Wed, 18 Oct 2000 10:13:59 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.osd.bsdi.com (termroom.bsdcon.org [206.55.247.2])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id KAA06490
	for <acpi-jp@jp.freebsd.org>; Wed, 18 Oct 2000 10:13:58 +0900 (JST)
	(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9I1GPh01412
	for <acpi-jp@jp.freebsd.org>; Tue, 17 Oct 2000 18:16:26 -0700 (PDT)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200010180116.e9I1GPh01412@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Wed, 18 Oct 2000 09:39:11 +0900."
             <200010180039.JAA16213@shidahara1.planet.sci.kobe-u.ac.jp> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 17 Oct 2000 18:16:25 -0700
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 881
Subject: [acpi-jp 881] Re: ACPI code update... 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> >> >One thing I had wondered; does the ACPICA code correctly re-evaluate DATA 
> >> >every time, or does it cache the result?  (And is there a useful set of 
> >> >debugging flags I can turn on to watch the evaluation of this code in 
> >> >order to find out what it's really doing?)
> >> >
> >> I  noticed that they use too few 'volatile' keyword.They only use it 
> >> in assembler instruction.I  think REGION memory access always need it.
> >
> >The REGION stuff still uses the external access functions in 
> >OsdHardware.c though, right?  Is it going to optimise across calls to 
> >these functions?
> 
> Have you written some code for bus memory read/write function not I/O or PCI
> configuration register in this ACPI stuff?
> 
> I think they use AcpiOsMapMemory(in OsdMemory.c) then access 
> the pointer by referencing the pointer returned from the function.
> (in AcpiAmlSystemMemorySpaceHandler()@amregion.c) We don't use 
> bus_space_(read|write)* stuff to access memory.

Hmm.  This function is so large and bulky that I can't imagine that the 
compiler could possibly optimise things to the point where that matters.
(But thanks for pointing it out).

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


