From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] value of "__attribute__((no_instrument_function))"??
Date: Fri, 19 Jan 2007 19:03:39 +0000 [thread overview]
Message-ID: <20070119190339.GC22466@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701190258510.20218@CPE00045a9c397f-CM001225dbafb6>
On 19.01.2007 [03:09:07 -0500], Robert P. J. Day wrote:
>
> i just noticed that there are a *very* small number of routines in
> the source tree tagged with the attribute of "no_instrument_function".
>
> $ grep -rw no_instrument_function .
> ./net/rxrpc/main.c:__attribute__((no_instrument_function));
> ./net/rxrpc/main.c:__attribute__((no_instrument_function));
> ./fs/afs/main.c:__attribute__((no_instrument_function));
> ./fs/afs/main.c:__attribute__((no_instrument_function));
>
> from the gcc manual:
>
> "If -finstrument-functions is given, profiling function calls will be
> generated at entry and exit of most user-compiled functions. Functions
> with this attribute will not be so instrumented."
>
> that *seems* like a useful attribute so the obvious question is --
> why is it not used more widely? that seems kind of odd. (in fact,
> the functions with these attributes are all commented out within an
> "#if 0" so they make no difference, anyway.)
It seems like a useful attribute to *disable* instrumentation in the
kernel? Why?
Thanks,
Nish
--
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-01-19 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 8:09 [KJ] value of "__attribute__((no_instrument_function))"?? Robert P. J. Day
2007-01-19 19:03 ` Nishanth Aravamudan [this message]
2007-01-19 19:58 ` Robert P. J. Day
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=20070119190339.GC22466@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.