GitLab

It comes in handy to be able to enable a set of related tracepoints
for specific tracing purposes.

The -e option can now take an optional parameter specifying a
pre-defined group of related tracepoints to enable, so far:

irq = pipeline_entry, pipeline_exit, handler_entry, handler_exit
timer = tracepoints related to timer event handling with latmus (used in
chasing latency in the timer handling path)
evl = all core tracepoints
all = all tracepoints ftrace knows about

-eall is identical to -f.

-E<tracepoint_file> enables the tracepoints mentioned in the
 user-provided <file>.

-t can be passed to dry-run the enable command, getting the list of
 ftrace settings which would have been set without this option when
 enabling the trace.
Signed-off-by: Philippe Gerum <rpm@xenomai.org>

Signed-off-by: Philippe Gerum <rpm@xenomai.org>

Do build them unconditionally though.
Signed-off-by: Philippe Gerum <rpm@xenomai.org>

We did produce the depfiles, but no target would depend on it. Oh,
well.
Signed-off-by: Philippe Gerum <rpm@xenomai.org>

Instead of requiring all commands to be located at $libexec, simply do
a search path look up for evl-<command_name> via execvp().

Allow rebuilding the tree while retaining the initial build settings,
i.e.:

-C <srcdir> O= ARCH= CROSS_COMPILE= UAPI= and DESTDIR=

Signed-off-by: Philippe Gerum <rpm@xenomai.org>

Script helpers to the evl command are installed in $prefix/libexec. By
convention, source scripts are suffixed by ".evl" to identify them
unambiguously. They are copied to $libexec/evl-<script>.
Signed-off-by: Philippe Gerum <rpm@xenomai.org>

Signed-off-by: Philippe Gerum <rpm@xenomai.org>

Signed-off-by: Philippe Gerum <rpm@xenomai.org>