From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf header: Fix pipe mode header dumping
Date: Thu, 3 Jul 2025 11:21:34 -0700 [thread overview]
Message-ID: <aGbKLj6ZQxlVrXAA@google.com> (raw)
In-Reply-To: <20250703042000.2740640-1-irogers@google.com>
On Wed, Jul 02, 2025 at 09:20:00PM -0700, Ian Rogers wrote:
> The pipe mode header dumping was accidentally removed when tracing of
> header feature events in pipe mode was added.
>
> Minor spelling tweak to header test failure message.
>
> Fixes: 61051f9a8452 ("perf header: In pipe mode dump features without --header/-I")
> Signed-off-by: Ian Rogers <irogers@google.com>
Yep, this makes the header test succeed.
Tested-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
> ---
> tools/perf/tests/shell/header.sh | 2 +-
> tools/perf/util/header.c | 15 ++++++++++++++-
> 2 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/tests/shell/header.sh b/tools/perf/tests/shell/header.sh
> index 412263de6ed7..e1628ac0a614 100755
> --- a/tools/perf/tests/shell/header.sh
> +++ b/tools/perf/tests/shell/header.sh
> @@ -42,7 +42,7 @@ check_header_output() {
> do
> if ! grep -q -E "$i" "${script_output}"
> then
> - echo "Failed to find expect $i in output"
> + echo "Failed to find expected $i in output"
> err=1
> fi
> done
> diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> index 487f663ed2de..53d54fbda10d 100644
> --- a/tools/perf/util/header.c
> +++ b/tools/perf/util/header.c
> @@ -4343,6 +4343,7 @@ int perf_event__process_feature(struct perf_session *session,
> int type = fe->header.type;
> u64 feat = fe->feat_id;
> int ret = 0;
> + bool print = dump_trace;
>
> if (type < 0 || type >= PERF_RECORD_HEADER_MAX) {
> pr_warning("invalid record type %d in pipe-mode\n", type);
> @@ -4362,8 +4363,20 @@ int perf_event__process_feature(struct perf_session *session,
> goto out;
> }
>
> - if (dump_trace) {
> + if (session->tool->show_feat_hdr) {
> + if (!feat_ops[feat].full_only ||
> + session->tool->show_feat_hdr >= SHOW_FEAT_HEADER_FULL_INFO) {
> + print = true;
> + } else {
> + fprintf(stdout, "# %s info available, use -I to display\n",
> + feat_ops[feat].name);
> + }
> + }
> +
> + if (dump_trace)
> printf(", ");
> +
> + if (print) {
> if (feat_ops[feat].print)
> feat_ops[feat].print(&ff, stdout);
> else
> --
> 2.50.0.727.gbf7dc18ff4-goog
>
next prev parent reply other threads:[~2025-07-03 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 4:20 [PATCH v1] perf header: Fix pipe mode header dumping Ian Rogers
2025-07-03 18:21 ` Namhyung Kim [this message]
2025-07-04 17:55 ` Namhyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aGbKLj6ZQxlVrXAA@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).