| 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: <20081106094558.50d94bcc@infradead.org> Date: Thu, 6 Nov 2008 09:45:58 -0800 From: Arjan van de Ven <arjan@...radead.org> To: Steven Rostedt <rostedt@...dmis.org> Cc: Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org, mingo@...e.hu, alan@...hat.com Subject: Re: [PATCH] ftrace: add an fsync tracer On Thu, 6 Nov 2008 10:34:50 -0500 (EST) Steven Rostedt <rostedt@...dmis.org> wrote: > > What I would like is a single "event tracer" that does all of this. > But add the ability to start and stop different events. We could start > with this tracer, and then add more events to this tracer. Have a > separate file to show which events are available. > > This will keep the 'available_tracers' file small, but it would be > fine if the 'events' file grew large. well 2 ounces versus one liter ;) what is the real need is 1) Have a trace point in the source 2) Associate a "formatting function" with that point (which basically transforms the trace parameters to, say, a string) 3) A way to turn the trace point on/off. right now this is what the fsync tracer does, because it's the only way to do such a thing. I don't care how to otherwise do it .... -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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