From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andi Kleen <ak@suse.de>
Cc: len.brown@intel.com, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Improve acpi_dbg_level= documentation
Date: Wed, 18 Apr 2007 08:08:12 -0700 [thread overview]
Message-ID: <20070418080812.0f7f559a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200704181221.37897.ak@suse.de>
On Wed, 18 Apr 2007 12:21:37 +0200 Andi Kleen wrote:
>
> First it was documented twice.
acpi_dbg_layer and
acpi_dbg_level are different.
But the added text is Good.
> Since this is a fairly important option document it properly.
> I kept myself looking for this information again and again.
>
> In particular the individual bits are fairly important. And add some
> warnings.
>
> Signed-off-by: Andi Kleen <ak@suse.de>
>
> Index: linux/Documentation/kernel-parameters.txt
> ===================================================================
> --- linux.orig/Documentation/kernel-parameters.txt
> +++ linux/Documentation/kernel-parameters.txt
> @@ -187,13 +187,16 @@ and is between 256 and 4096 characters.
> 1: enable, 0: disable. It is useful for boot time
> debugging. After system has booted up, it can be set
> via /proc/acpi/debug_layer.
> -
> - acpi_dbg_level= [HW,ACPI]
> - Format: <int>
> - Each bit of the <int> indicates an ACPI debug level,
> - 1: enable, 0: disable. It is useful for boot time
> - debugging. After system has booted up, it can be set
> - via /proc/acpi/debug_level.
> + CONFIG_ACPI_DEBUG must be enabled for this to produce any output.
> + Available bits (add the numbers together) to enable debug output
> + for specific parts of the ACPI subsystem:
> + 1 utilities 2 hardware 4 events 8 tables
> + 0x10 namespace 0x20 parser 0x40 dispatcher
> + 0x80 executer 0x100 resources 0x200 debugger
> + 0x400 os services
> + The number can be in decimal or prefixed with 0x in hex.
> + Warning: Many of these options can produce a lot of
> + output and make your system unusable. Be very careful.
>
> acpi_fake_ecdt [HW,ACPI] Workaround failure due to BIOS lacking ECDT
>
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-18 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 10:21 [PATCH] Improve acpi_dbg_level= documentation Andi Kleen
2007-04-18 15:08 ` Randy Dunlap [this message]
2007-04-18 20:26 ` Len Brown
2007-04-18 22:35 ` Dave Jones
2007-04-19 17:35 ` Len Brown
2007-04-19 7:38 ` Zhang Rui
2007-04-19 15:04 ` Randy Dunlap
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=20070418080812.0f7f559a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=ak@suse.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.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