linux-kernel - Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0903231443090.3578@gandalf.stny.rr.com>
Date:	Mon, 23 Mar 2009 14:44:06 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace



On Sun, 22 Mar 2009, Ingo Molnar wrote:

> 
> one thing to note is:
> 
>  <EOI>  [<ffffffff802b78ad>] ? ftrace_likely_update+0x1f/0x27
>  [<ffffffff8022cf88>] ? prepare_ftrace_return+0x3c/0x158
>  [<ffffffff8022d070>] ? prepare_ftrace_return+0x124/0x158
>  [<ffffffff8020c776>] ? ftrace_graph_caller+0x46/0x6d
>  [<ffffffff802a2cd8>] ? jhash+0x9/0x1e6
>  [<ffffffff802a30d9>] ? get_tracepoint+0x30/0x7f
>  [<ffffffff8020c79d>] ? return_to_handler+0x0/0x73
>  [<ffffffff8020db1c>] call_softirq+0x1c/0x28
> 
> the branch profiler should be disabled inside ftrace ...

Actually, if the branch tracer is off (only profiling enabled) I actually 
used it to look at the conditions taken inside of ftrace. I prefer that it 
is not disabled. But obviously, we must disable it, if we do the branch 
tracing.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/