From: Josh Triplett <josh@joshtriplett.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/4] tracing,x86_64 - function/graph trace without mcount/-pg/framepointer
Date: Mon, 7 Feb 2011 13:22:22 -0800 [thread overview]
Message-ID: <20110207212220.GA30070@feather> (raw)
On Fri, Jun 23, 2000 at 10:56:55AM +0000, Steven Rostedt wrote:
> On Thu, 2011-02-03 at 16:42 +0100, Jiri Olsa wrote:
> > hi,
> >
> > I recently saw the direct jump probing made for kprobes
> > and tried to use it inside the trace framework.
> >
> > The global idea is patching the function entry with direct
> > jump to the trace code, instead of using pregenerated gcc
> > profile code.
>
> Interesting, but ideally, it would be nice if gcc provided a better
> "mcount" mechanism. One that calls mcount (or whatever new name it would
> have) before it does anything with the stack.
GCC 4.6 may help here. According to
http://gcc.gnu.org/gcc-4.6/changes.html:
"Support for emitting profiler counter calls before function prologues.
This is enabled via a new command-line option -mfentry."
Looks like that option might only support x86 (32-bit and 64-bit) at the
moment, but it still seems like an improvement over the current
mechanism to work around GCC's placement of mcount.
- Josh Triplett
next reply other threads:[~2011-02-07 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 21:22 Josh Triplett [this message]
2011-02-07 21:32 ` [RFC 0/4] tracing,x86_64 - function/graph trace without mcount/-pg/framepointer Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 15:42 Jiri Olsa
2011-02-03 16:33 ` Steven Rostedt
2011-02-03 17:35 ` Frederic Weisbecker
2011-02-03 19:00 ` Steven Rostedt
2011-02-04 6:03 ` Masami Hiramatsu
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=20110207212220.GA30070@feather \
--to=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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.