| 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
| ||
|
Message-ID: <1347551937.10751.80.camel@gandalf.local.home> Date: Thu, 13 Sep 2012 11:58:57 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Frederic Weisbecker <fweisbec@...il.com> Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Andi Kleen <ak@...ux.intel.com> Subject: Re: [PATCH 1/7] perf: Enable function tracing for perf core On Sat, 2012-09-08 at 15:06 +0200, Frederic Weisbecker wrote: > 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. As I believe the patch set is being held off due to whether or not to function trace perf, I'll rebase without it, and push the result again. I'll add this to the queue of patches I have to trace the event functions as well, as they seem to do the same things. -- 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/
Powered by blists - more mailing lists