perf trace: Mark which syscall arguments go from user space to kernel space
authorArnaldo Carvalho de Melo <acme@redhat.com>
Mon, 9 Sep 2024 19:29:44 +0000 (16:29 -0300)
committerArnaldo Carvalho de Melo <acme@redhat.com>
Mon, 9 Sep 2024 22:23:03 +0000 (19:23 -0300)
commit2f2e439ba56f45b9d8aff300b39fa0bfa49ec2d8
treec7923c6cebbfef6332021999fe7c51896038a840
parentc90a88d33a23a8b3c58ee0e1d18d7392244b9b03
perf trace: Mark which syscall arguments go from user space to kernel space

We need to know where to collect it in the BPF augmenters, if in the
sys_enter hook or in the sys_exit hook.

Start with the SCA_FILENAME one, that is just from user to kernel space.

The alternative, better, but takes a bit more time than I have now, is
to use the __user information that is already in the syscall args and
encoded in BTF via a tag, do it later.

Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Howard Chu <howardchu95@gmail.com>
Cc: Ian Rogers <irogers@google.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
tools/perf/builtin-trace.c