On Fri, 12 Apr 2019 16:38:05 +0300 Tzvetomir Stoyanov <tstoyanov@xxxxxxxxxx> wrote: > +DESCRIPTION > +----------- > +Filters can be attached to traced events. They are useful for picking out only > +the desired information, and not to flood the ring buffer with needless events. Actually, these filters have nothing to do with the ring buffer. They are helper functions to let the tools filter out various events when outputting them. There are filters that limit what goes into the ring buffer, but that's in the kernel, it's not related to these. -- Steve > +Each event can be filtered based on its parameters, described in the event's > +format file. This set of functions can be used to create, delete, modify and > +attach event filters. > + > +The _tep_filter_alloc()_ function creates a new event filter. The _tep_ argument > +is the trace event parser context. > + > +The _tep_filter_free()_ function frees an event filter and all resources that it > +had used. > + > +The _tep_filter_reset()_ function removes all rules from an event filter and > +resets it. > + > +The _tep_filter_add_filter_str()_ function adds a new rule to the _filter_. The > +_filter_str_ argument is the filter string, that contains the rule. > + > +The _tep_event_filtered()_ function checks if the event with _event_id_ has > +_filter_. > + > +The _tep_filter_remove_event()_ function removes a _filter_ for an event with > +_event_id_. > + > +The _tep_filter_match()_ function tests if a _record_ matches given _filter_. > + > +The _tep_filter_copy()_ function copies a _source_ filter into a _dest_ filter. > + > +The _tep_filter_compare()_ function compares two filers - _filter1_ and _filter2_. > + > +The _tep_filter_make_string()_ function constructs a string, displaying > +the _filter_ contents for given _event_id_. > + > +The _tep_filter_strerror()_ function copies the _filter_ error buffer into the > +given _buf_ with the size _buflen_. If the error buffer is empty, in the _buf_ > +is copied a string, describing the error _err_. > +
|