From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/7] perf: Enable function tracing for perf core
Date: Sat, 8 Sep 2012 15:06:50 +0200 [thread overview]
Message-ID: <20120908130646.GA2122@somewhere.redhat.com> (raw)
In-Reply-To: <20120908115640.032328533@goodmis.org>
On Sat, Sep 08, 2012 at 07:55:16AM -0400, Steven Rostedt wrote:
> According to Steven R. there is no reason left to not support
> function tracing for the perf core. This makes it easier to debug
> perf.
>
> Don't remove -pg for the x86 and generic perf core.
Actually, perf can use function tracing. A good reason for disabling
function tracing in perf is to avoid the overhead of recursive function
tracing, even though we are protected against tracing re-entrancy, this
still result in some overhead.
next prev parent reply other threads:[~2012-09-08 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 11:55 [PATCH 0/7] [GIT PULL][v3.7] tracing: Updates and fixes (for 3.7 queue) Steven Rostedt
2012-09-08 11:55 ` [PATCH 1/7] perf: Enable function tracing for perf core Steven Rostedt
2012-09-08 13:06 ` Frederic Weisbecker [this message]
2012-09-10 14:43 ` Steven Rostedt
2012-09-13 15:58 ` Steven Rostedt
2012-09-08 14:15 ` Namhyung Kim
2012-09-10 14:40 ` Steven Rostedt
2012-09-08 11:55 ` [PATCH 2/7] tracing: Skip printing "OK" if failed to disable event Steven Rostedt
2012-09-08 11:55 ` [PATCH 3/7] trace: Stop compiling in trace_clock unconditionally Steven Rostedt
2012-09-08 11:55 ` [PATCH 4/7] ftrace/x86: Adjust x86 regs.ip as like as x86-64 Steven Rostedt
2012-09-08 11:55 ` [PATCH 5/7] kprobes/x86: Fix kprobes to collectly handle IP on ftrace Steven Rostedt
2012-09-08 11:55 ` [PATCH 6/7] ftrace/x86-64: Allow to change RIP in handlers Steven Rostedt
2012-09-08 11:55 ` [PATCH 7/7] kprobes/x86: Fix to support jprobes on ftrace-based kprobe Steven Rostedt
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=20120908130646.GA2122@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome