From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH] Disable slow duplicate object tracking in ACPI_DEBUG Date: Thu, 11 Aug 2005 04:29:52 +0200 Message-ID: <20050811022952.GG8974@wotan.suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Brown, Len" Cc: Andi Kleen , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Wed, Aug 10, 2005 at 10:14:43PM -0400, Brown, Len wrote: > Maybe it is time to figure out why SLES has ACPI_DEBUG enabled. > If it is certain warnings and error messages, then perhaps > we should enable those but not all the other misc debug > and paranoia checks that come with ACPI_DEBUG? SLES doesn't have ACPI_DEBUG enabled. ACPI_DEBUG is just sometimes enabled in the betas because it makes it easier to track down ACPI bugs - mostly because of the tracing options which can be then used without recompiling the kernel (which BTW seem to also cause considerable overhead. One current case is a system where kacpid takes about 1.7% of CPU and most of that seems to be just tracing functions) ACPI_DEBUG_LITE was intended to be a subset that has only the needed stuff enabled, but somehow that didn't take off. -Andi ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf