From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: CONFIG_ACPI_DEBUG cost
Date: Sun, 31 Oct 2004 19:48:23 +0100 [thread overview]
Message-ID: <20041031184823.GA5578@elf.ucw.cz> (raw)
In-Reply-To: <1099029802.143.226.camel@d845pe>
Hi!
> 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?
Its worse than that, it looks very ugly in the sources. See for
example return_VALUE() macro...
I think acpi debugging crap^H^H^H^Hstuff should be simply removed in
favor of people running kgdb or something like that. ["If you want to
print all names of functions being entered, you should probably be
using debugger in the first place"]
When debugging acpi I end up doing printk's anyway because those
built-in macros produce just too much of output...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-10-31 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 6:03 CONFIG_ACPI_DEBUG cost Len Brown
2004-10-29 6:20 ` Andi Kleen
2004-10-31 18:48 ` Pavel Machek [this message]
[not found] ` <20041031184823.GA5578-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-02 16:46 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 16:27 Moore, Robert
[not found] ` <37F890616C995246BE76B3E6B2DBE0550276521D-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-10-29 23:24 ` Andi Kleen
2004-10-29 23:28 Moore, Robert
[not found] <37F890616C995246BE76B3E6B2DBE0550276533A@orsmsx403.amr.corp.intel.com>
[not found] ` <37F890616C995246BE76B3E6B2DBE0550276533A-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-11-05 7:54 ` Len Brown
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=20041031184823.GA5578@elf.ucw.cz \
--to=pavel-+zi9xunit7i@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