From: Steven Rostedt <rostedt@goodmis.org>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, rientjes@google.com, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/urgent] trace, documentation: Fix branch profiling location in debugfs
Date: Thu, 17 Mar 2011 10:30:41 -0400 [thread overview]
Message-ID: <1300372241.16880.119.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <tip-13e5befaddcf8d542ae45610b552105490a0010b@git.kernel.org>
On Thu, 2011-03-17 at 11:04 +0000, tip-bot for David Rientjes wrote:
> Commit-ID: 13e5befaddcf8d542ae45610b552105490a0010b
> Gitweb: http://git.kernel.org/tip/13e5befaddcf8d542ae45610b552105490a0010b
> Author: David Rientjes <rientjes@google.com>
> AuthorDate: Wed, 16 Mar 2011 17:17:08 -0700
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Thu, 17 Mar 2011 09:10:45 +0100
Heh, I added this on top of the jump label patches that I'm testing.
I'll just remove it ;)
-- Steve
>
> trace, documentation: Fix branch profiling location in debugfs
>
> The debugfs interface for branch profiling is through
>
> /sys/kernel/debug/tracing/trace_stat/branch_annotated
> /sys/kernel/debug/tracing/trace_stat/branch_all
>
> so update the Kconfig accordingly.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> LKML-Reference: <alpine.DEB.2.00.1103161716320.11407@chino.kir.corp.google.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> kernel/trace/Kconfig | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index 14674dc..61d7d59f 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -275,7 +275,7 @@ config PROFILE_ANNOTATED_BRANCHES
> This tracer profiles all the the likely and unlikely macros
> in the kernel. It will display the results in:
>
> - /sys/kernel/debug/tracing/profile_annotated_branch
> + /sys/kernel/debug/tracing/trace_stat/branch_annotated
>
> Note: this will add a significant overhead; only turn this
> on if you need to profile the system's use of these macros.
> @@ -288,7 +288,7 @@ config PROFILE_ALL_BRANCHES
> taken in the kernel is recorded whether it hit or miss.
> The results will be displayed in:
>
> - /sys/kernel/debug/tracing/profile_branch
> + /sys/kernel/debug/tracing/trace_stat/branch_all
>
> This option also enables the likely/unlikely profiler.
>
prev parent reply other threads:[~2011-03-17 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 0:17 [patch] trace: fix " David Rientjes
2011-03-17 11:04 ` [tip:perf/urgent] trace, documentation: Fix " tip-bot for David Rientjes
2011-03-17 14:30 ` Steven Rostedt [this message]
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=1300372241.16880.119.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®