Skip to content

RFC tracing: event filtering

Tom Zanussi lkml 1 version In review

Get series with b4
b4 am 1237271002.8033.148.camel@charm-linux

Versions newest first

  1. v1 RFC Latest4 patches 9 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4tracing: add run-time field descriptions for event filteringkernel/trace/trace.h kernel/trace/trace_events.c kernel/trace/trace_events_stage_2.h +1 more+106 -100 replies
2/4tracing: add rb_event_discard() hackinclude/linux/ring_buffer.h kernel/trace/ring_buffer.c+58 -244 replies
3/4tracing: add per-event filteringkernel/trace/Makefile kernel/trace/trace.h kernel/trace/trace_events.c +2 more+430 -02 replies
4/4tracing: add per-subsystem filteringkernel/trace/trace.h kernel/trace/trace_events.c kernel/trace/trace_events_filter.c+175 -110 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC][PATCH 0/4] tracing: event filtering

Hi,

This patchset is a first attempt at adding filtering to the event-tracing infrastructure.

The filtering itself seems to work ok, as far as I've been able to test it, but I'm still battling with getting the ring-buffer to do what I want (discarding events, see patch 2) so am hoping someone more familiar with the ring buffer can point me in the right direction before I do any more work on it.

Another specific thing it would be good to get comments on would be how to allow the user to unambiguously specify a field name in a filter when there are duplicate field names for an event, as mentioned in patch 1.

Of course, any comments about the rest of the interface and code are also welcome...

Thanks,

Tom