[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250607061238.161756-1-irogers@google.com>
Date: Fri, 6 Jun 2025 23:12:34 -0700
From: Ian Rogers <irogers@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>, Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>,
Ian Rogers <irogers@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, James Clark <james.clark@...aro.org>,
Zhongqiu Han <quic_zhonhan@...cinc.com>, Yicong Yang <yangyicong@...ilicon.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org
Subject: [PATCH v1 0/4] Pipe mode header dumping and minor space saving
Pipe mode has no header and emits the data as if it were events. The
dumping of features was controlled by the --header/-I options which
makes little sense when they are events, normally traced when
dump_trace is true. Switch to making pipe feature events also be
traced with detail when other events are.
The attr event in pipe mode had no dumping, wire this up and use the
existing perf_event_attr fprintf support.
The header's bpf_prog_info or bpf_btf may be empty when written. If
they are empty just skip writing them to save space.
Ian Rogers (4):
perf header: In pipe mode dump features without --header/-I
perf header: Allow tracing of attr events
perf header: Display message if BPF/BTF info is empty
perf header: Don't write empty BPF/BTF info
tools/perf/util/header.c | 46 ++++++++++++++++++++++++++--------------
tools/perf/util/header.h | 1 +
2 files changed, 31 insertions(+), 16 deletions(-)
--
2.50.0.rc0.604.gd4ff7b7c86-goog
Powered by blists - more mailing lists