public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Disable slow duplicate object tracking in ACPI_DEBUG
Date: Thu, 11 Aug 2005 04:29:52 +0200	[thread overview]
Message-ID: <20050811022952.GG8974@wotan.suse.de> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B30044D213E-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.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

  parent reply	other threads:[~2005-08-11  2:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11  2:14 [PATCH] Disable slow duplicate object tracking in ACPI_DEBUG Brown, Len
     [not found] ` <F7DC2337C7631D4386A2DF6E8FB22B30044D213E-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-08-11  2:29   ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-10 11:32 Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050811022952.GG8974@wotan.suse.de \
    --to=ak-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox