[PATCH v3 0/3] [PATCH v2 0/2] tracing/probes: allow no event name input when create group

From: Linyu Yuan
Date: Tue May 31 2022 - 02:29:30 EST


take kprobe event as example, when create a group of events,
p[:[GRP/]EVENT] [MOD:]KSYM[+OFFS]|KADDR [FETCHARGS],
according to this format, we must input EVENT name,

this change allow only GRP/ input, EVENT name auto generate from KSYM,
p[:[GRP/][EVENT]] [MOD:]KSYM[+OFFS]|KADDR [FETCHARGS]

siliar change apply to eprobe and uprobe.

V1: https://lore.kernel.org/lkml/1651397651-30454-1-git-send-email-quic_linyyuan@xxxxxxxxxxx/T/#m33b0665941d9caeeb118afa84db4016321cea9a6
V2: fix remove comment in V1 patch1,
remove v1 patch2 as it is NACK.
v3: (v2 link: https://lore.kernel.org/lkml/1653795294-19764-1-git-send-email-quic_linyyuan@xxxxxxxxxxx/)
add selftest cases for kprobe and eprobe event,
remove macro used in v1,v2,
change location to generate eprobe event name.

Linyu Yuan (3):
tracing: eprobe: remove duplicate is_good_name() operation
tracing: auto generate event name when create a group of events
selftests/ftrace: add test case for GRP/ only input

Documentation/trace/kprobetrace.rst | 8 +++----
Documentation/trace/uprobetracer.rst | 8 +++----
kernel/trace/trace.c | 8 +++----
kernel/trace/trace_dynevent.c | 2 +-
kernel/trace/trace_eprobe.c | 25 +++++++++++-----------
kernel/trace/trace_kprobe.c | 16 ++++++++------
kernel/trace/trace_probe.c | 6 ++++++
kernel/trace/trace_uprobe.c | 12 +++++++----
.../ftrace/test.d/dynevent/add_remove_eprobe.tc | 7 +++++-
.../ftrace/test.d/dynevent/add_remove_kprobe.tc | 7 +++++-
10 files changed, 61 insertions(+), 38 deletions(-)

--
2.7.4