| 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: <4A2144FA.6080508@redhat.com> Date: Sat, 30 May 2009 10:38:50 -0400 From: Masami Hiramatsu <mhiramat@...hat.com> To: Christoph Hellwig <hch@...radead.org> CC: Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>, lkml <linux-kernel@...r.kernel.org>, systemtap <systemtap@...rces.redhat.com>, kvm <kvm@...r.kernel.org>, DLE <dle-develop@...ts.sourceforge.net>, Ananth N Mavinakayanahalli <ananth@...ibm.com>, Frederic Weisbecker <fweisbec@...il.com>, Tom Zanussi <tzanussi@...il.com> Subject: Re: [PATCH -tip v8 7/7] tracing: add kprobe-based event tracer Christoph Hellwig wrote: > On Thu, May 28, 2009 at 08:03:53PM -0400, Masami Hiramatsu wrote: >> Add kprobes-based event tracer on ftrace. > > Wouldn't it make more sense to call this the dynamic event tracer? > > The use of kprobes is more an implementation detail than something > the user cares about. Hmm, I don't think so, because other tracers (e.g. hw breakpoint tracer) can also add their events dynamically by trace_add/remove_event_call. It's more flexible than this tracer includes those events. Thank you, -- Masami Hiramatsu Software Engineer Hitachi Computer Products (America) Inc. Software Solutions Division e-mail: mhiramat@...hat.com -- 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