linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	James Clark <james.clark@linaro.org>,
	Zhongqiu Han <quic_zhonhan@quicinc.com>,
	Yicong Yang <yangyicong@hisilicon.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH v1 0/4] Pipe mode header dumping and minor space saving
Date: Tue, 24 Jun 2025 12:11:19 -0700	[thread overview]
Message-ID: <aFr4VwxaAi5u5U2F@google.com> (raw)
In-Reply-To: <20250607061238.161756-1-irogers@google.com>

On Fri, Jun 06, 2025 at 11:12:34PM -0700, Ian Rogers wrote:
> 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.

I'm not sure I'm following.  Are you saying the pipe mode doesn't
support features with --header/-I option?

It seems to work for me.

  $ git show
  commit be59dba332e1e8edd3e88d991ba0e4795ae2bcb2 (HEAD -> perf-testing)
  Author: Ian Rogers <irogers@google.com>
  Date:   Tue Jun 17 15:33:56 2025 -0700
  
      libperf evsel: Add missed puts and asserts
      
      A missed evsel__close before evsel__delete was the source of leaking
      perf events due to a hybrid test. Add asserts in debug builds so that
      this shouldn't happen in the future. Add puts missing on the cpu map
      and thread maps.
      
      Signed-off-by: Ian Rogers <irogers@google.com>
      Link: https://lore.kernel.org/r/20250617223356.2752099-4-irogers@google.com
      Signed-off-by: Namhyung Kim <namhyung@kernel.org>
  
  $ ./perf version
  perf version 6.16.rc3.gbe59dba332e1
  
  $ ./perf record -o- true | ./perf report -i- --header-only
  # ========
  # captured on    : Tue Jun 24 12:06:38 2025
  # header version : 1
  # data offset    : 0
  # data size      : 0
  # feat offset    : 0
  # ========
  #
  # hostname : bangji
  # os release : 6.12.20-1rodete1-amd64
  # perf version : 6.16.rc3.gbe59dba332e1
  # arch : x86_64
  # nrcpus online : 4
  # nrcpus avail : 8
  # cpudesc : 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  # cpuid : GenuineIntel,6,140,1
  # total memory : 32566540 kB
  # cmdline : /home/namhyung/project/linux/tools/perf/perf record -o- true 
  # event : name = cycles:P, , id = { 369, 370, 371, 372 }, type = 0 (PERF_TYPE_HARDWARE), ...
  # CPU_TOPOLOGY info available, use -I to display
  # NUMA_TOPOLOGY info available, use -I to display
  # pmu mappings: cpu = 4, breakpoint = 5, cstate_core = 22, cstate_pkg = 23, hwmon_acpitz = 4294901760, ...
  # time of first sample : 0.000000
  # time of last sample : 0.000000
  # sample duration :      0.000 ms
  # MEM_TOPOLOGY info available, use -I to display
  # cpu pmu capabilities: branches=32, max_precise=3, pmu_name=icelake
  # intel_pt pmu capabilities: topa_multiple_entries=1, psb_cyc=1, single_range_output=1, ...
  
> 
> 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.

These look good to me.

Thanks,
Namhyung

> 
> 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
> 

  parent reply	other threads:[~2025-06-24 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  6:12 [PATCH v1 0/4] Pipe mode header dumping and minor space saving Ian Rogers
2025-06-07  6:12 ` [PATCH v1 1/4] perf header: In pipe mode dump features without --header/-I Ian Rogers
2025-06-07  6:12 ` [PATCH v1 2/4] perf header: Allow tracing of attr events Ian Rogers
2025-06-07  6:12 ` [PATCH v1 3/4] perf header: Display message if BPF/BTF info is empty Ian Rogers
2025-06-07  6:12 ` [PATCH v1 4/4] perf header: Don't write empty BPF/BTF info Ian Rogers
2025-06-24 19:11 ` Namhyung Kim [this message]
2025-06-24 20:15   ` [PATCH v1 0/4] Pipe mode header dumping and minor space saving Ian Rogers
2025-06-25 17:40     ` Namhyung Kim
2025-06-26 17:41 ` 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=aFr4VwxaAi5u5U2F@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --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 \
    --cc=quic_zhonhan@quicinc.com \
    --cc=yangyicong@hisilicon.com \
    /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).