From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: CONFIG_ACPI_DEBUG cost Date: Fri, 29 Oct 2004 08:20:24 +0200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20041029062024.GA6223@wotan.suse.de> References: <1099029802.143.226.camel@d845pe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1099029802.143.226.camel@d845pe> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Len Brown Cc: ACPI Developers List-Id: linux-acpi@vger.kernel.org On Fri, Oct 29, 2004 at 02:03:23AM -0400, Brown, Len wrote: > The static size of the built-in part of ACPI nearly doubles with > CONFIG_ACPI_DEBUG=y. > > Thinking we should have a less heavyweight DEBUG build option for use by > production kernels -- any volunteers to look into it? The function names in the call tracing are redundant at least. Maybe the debug function could just pass the address and use kallsym_lookup() for the output. I don't know how much it would save though. -Andi ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/