| 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: <c62985530811270751o3593e409ia35d7060120fbc90@mail.gmail.com> Date: Thu, 27 Nov 2008 16:51:06 +0100 From: "Frédéric Weisbecker" <fweisbec@...il.com> To: "Steven Rostedt" <rostedt@...dmis.org> Cc: "Ingo Molnar" <mingo@...e.hu>, "Tim Bird" <tim.bird@...sony.com>, "Linux Kernel" <linux-kernel@...r.kernel.org>, "Peter Zijlstra" <a.p.zijlstra@...llo.nl> Subject: Re: [PATCH] tracing/function-branch-tracer: enhancements for the trace output 2008/11/27 Steven Rostedt <rostedt@...dmis.org>: > No, please keep the CPU # first. If anything, you will want to separate > out the CPUs first. Otherwise you will see things all mixed up. So perhaps between CPU and time? I don't really like it after the time, not so easy to find.... > Hmm, I could also add a per cpu files. > > debugfs/tracing/buffers/cpu0 > debugfs/tracing/buffers/cpu1 > debugfs/tracing/buffers/cpu2 > debugfs/tracing/buffers/cpu3 That would be useful indeed, as the ftrace_trace_pid on this tracer. But I wonder about the cost of double function tracing in this case. Your idea of a tgid;pid would be nice (with tgid || pid). > That would print out the trace for a single CPU. > > BTW, I'm really not here. I'm on holiday eating turkeys. -- 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