| 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: <alpine.DEB.1.10.0808031042440.30870@gandalf.stny.rr.com> Date: Sun, 3 Aug 2008 10:45:06 -0400 (EDT) From: Steven Rostedt <rostedt@...dmis.org> To: Ming Lei <tom.leiming@...il.com> cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...ux-foundation.org>, Steven Rostedt <srostedt@...hat.com> Subject: Re: [RFC] ftrace: support tracing functions in one module On Sun, 3 Aug 2008, Ming Lei wrote: > Hi, > > IMO, ftrace is a very good tools, which can monitor almost all > functions calling > in the running kernel. The traced result is very complete and intact. > But it seems > too large to grasp the interested content. For example, one may only > have interest in > functions calling in usbcore.ko, but he must trace all the functions > calling in the > kernel, so the tracing result is too large to use it. > > Could you add the support of tracing functions in one module only to ftrace? Look at the set_ftrace_filter in ftrace.txt. You can pick and choose which functions to trace. All the functions that can be traced is in available_filter_functions in the debugfs/tracing directory. Note, the functions must execute at least once before they can be recorded. -- 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