Messages in this thread | | | Date | Mon, 4 Aug 2008 14:18:56 -0300 | From | Arnaldo Carvalho de Melo <> | Subject | Re: [RFC] ftrace: support tracing functions in one module |
| |
Em Mon, Aug 04, 2008 at 12:28:12PM -0400, Steven Rostedt escreveu: > > On Mon, 4 Aug 2008, Arnaldo Carvalho de Melo wrote: > > > > > > Do you have the plan to support tracing functions in one module or in one kernel > > > address range? > > > > What about using: > > > > [acme@doppio pahole]$ nm --defined-only /usr/lib/debug/lib/modules/2.6.24.7-75.el5rt/kernel/drivers/net/tg3.ko.debug | grep ' t ' | cut -d' ' -f3 | head > > __tg3_set_coalesce > > __tg3_set_mac_addr > > __tg3_set_rx_mode > > _tw32_flush > > tg3_5700_link_polarity > > tg3_abort_hw > > tg3_alloc_rx_skb > > tg3_ape_driver_state_change > > tg3_bmcr_reset > > tg3_change_mtu > > [acme@doppio pahole]$ > > > > Feed this to /sys/kernel/debug/tracing/set_ftrace_filter and you should > > be set, no? > > > > Ok, you need to have the kernel-debuginfo package installed, and I guess > > we can get away with that, but for now, isn't that enough? > > > Or simply (again for tg3 : > > > # awk '/\[tg3\]/ { print $3 }' /proc/kallsyms \ > > /debug/tracing/set_ftrace_filter
For the drivers that do proper namespacing, yes, that should be enough in most cases :)
- Arnaldo
| |