From owner-freebsd-acpi@FreeBSD.ORG Tue May 5 20:56:35 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 5B6A51065673; Tue, 5 May 2009 20:56:35 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 5 May 2009 16:56:25 -0400 User-Agent: KMail/1.6.2 References: <49F8B859.7060908@umn.edu> <200905051609.38689.jkim@FreeBSD.org> <4A00A042.20806@FreeBSD.org> In-Reply-To: <4A00A042.20806@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200905051656.27439.jkim@FreeBSD.org> Cc: freebsd-acpi@freebsd.org, Alan Amesbury , Andriy Gapon Subject: Re: Garbled output from kgdb? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 20:56:35 -0000 On Tuesday 05 May 2009 04:23 pm, John Baldwin wrote: > Jung-uk Kim wrote: > > On Tuesday 05 May 2009 12:51 pm, Andriy Gapon wrote: > >> BTW, this issue seems to be fixed in Jung-uk's acpi patches for > >> newer acpica imports, but it is not fixed both in stable/7 and > >> head. > > > > Yes, it was fixed in my patchsets long ago, which uses spin lock > > for AcpiOsAcquireLock(). :-) > > I'm not sure all ACPI locks need to be spin locks, but any locks > used by the idle code must be spin locks. There are several types of ACPI locks internally and externally. The AcpiOs{Create,Acquire,Release}Lock() is just one of them, which is a spin lock and it is mostly used for interrupt handlers, e.g., GPE and HW. I have to say there were a lot of confusions between ACPI developers because it was not well-documented. In fact, I personally had to exchange lengthy e-mails with Intel engineers to understand the meaning of these myself. Now Intel has documented everything you need to know about ACPI-CA for OS developers: http://git.moblin.org/cgit.cgi/acpica/tree/documents > Regardless, are you going to import a newer ACPI-CA and commit your > patches soon? It sounds like several things are fixed in the > outstanding patches by now including both this and the problem with > the Alias() operator. Unfortunately, I don't have much time to work on it recently. Couple of developers volunteered to do the actual import work although I haven't heard from them in a while. :-( Jung-uk Kim