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@xxxxxxxxxx> > AuthorDate: Wed, 16 Mar 2011 17:17:08 -0700 > Committer: Ingo Molnar <mingo@xxxxxxx> > 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@xxxxxxxxxx> > Cc: Steven Rostedt <rostedt@xxxxxxxxxxx> > LKML-Reference: <alpine.DEB.2.00.1103161716320.11407@xxxxxxxxxxxxxxxxxxxxxxxxx> > Signed-off-by: Ingo Molnar <mingo@xxxxxxx> > --- > 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. > -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html