Hi Steve, Since synthetic events can now be used separately from hist triggers, it makes sense to actually separate them into different options. It also makes sense in terms of file bloat - trace_events_hist.c was getting very large and this makes it smaller and easier to follow.
Thanks, Tom The following changes since commit 8e99cf91b99bb30e16727f10ad6828741c0e992f: tracing: Do not allocate buffer in trace_find_next_entry() in atomic (2020-04-03 11:30:50 -0400) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/separate-synth-v1 Tom Zanussi (2): tracing: Move synthetic events to a separate file selftests/ftrace: Distinguish between hist and synthetic event checks kernel/trace/Kconfig | 20 +- kernel/trace/Makefile | 1 + kernel/trace/trace_events_hist.c | 2082 ++--------------- kernel/trace/trace_events_synth.c | 1789 ++++++++++++++ kernel/trace/trace_synth.h | 36 + .../trigger-field-variable-support.tc | 5 + .../trigger-inter-event-combined-hist.tc | 5 + .../trigger-multi-actions-accept.tc | 5 + .../trigger-onmatch-action-hist.tc | 5 + .../trigger-onmatch-onmax-action-hist.tc | 5 + .../inter-event/trigger-onmax-action-hist.tc | 5 + .../trigger-snapshot-action-hist.tc | 5 + .../inter-event/trigger-trace-action-hist.tc | 5 + 13 files changed, 2028 insertions(+), 1940 deletions(-) create mode 100644 kernel/trace/trace_events_synth.c create mode 100644 kernel/trace/trace_synth.h -- 2.17.1
