From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: "Moore, Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: CONFIG_ACPI_DEBUG cost
Date: Sat, 30 Oct 2004 01:24:37 +0200 [thread overview]
Message-ID: <20041029232437.GF31914@wotan.suse.de> (raw)
In-Reply-To: <37F890616C995246BE76B3E6B2DBE0550276521D-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Fri, Oct 29, 2004 at 09:27:47AM -0700, Moore, Robert wrote:
> The function names are certainly expensive, but why "redundant"? They
> are used for more than just a call stack trace.
Because the kernel has them already in the kallsyms symbol table
when KALLSYMS is enabled, which it usually is now.
My proposal was to pass around addresses and then just look them
up before you output.
-Andi
-------------------------------------------------------
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-29 23:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 16:27 CONFIG_ACPI_DEBUG cost Moore, Robert
[not found] ` <37F890616C995246BE76B3E6B2DBE0550276521D-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-10-29 23:24 ` Andi Kleen [this message]
[not found] <37F890616C995246BE76B3E6B2DBE0550276533A@orsmsx403.amr.corp.intel.com>
[not found] ` <37F890616C995246BE76B3E6B2DBE0550276533A-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-11-05 7:54 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 23:28 Moore, Robert
2004-10-29 6:03 Len Brown
2004-10-29 6:20 ` Andi Kleen
2004-10-31 18:48 ` Pavel Machek
[not found] ` <20041031184823.GA5578-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-11-02 16:46 ` Bjorn Helgaas
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=20041029232437.GF31914@wotan.suse.de \
--to=ak-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=robert.moore-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