linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: weilin.wang@intel.com
Cc: Ian Rogers <irogers@google.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.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,
	 Perry Taylor <perry.taylor@intel.com>,
	Samantha Alt <samantha.alt@intel.com>,
	 Caleb Biggers <caleb.biggers@intel.com>
Subject: Re: [RFC PATCH v7 5/6] perf stat: Add retire latency print functions to print out at the very end of print out
Date: Mon, 22 Apr 2024 13:02:04 -0700	[thread overview]
Message-ID: <CAM9d7cjUkGFfbdWSxzs5tkLHdctjux1jGV0P_J9YsGP3QmWNOw@mail.gmail.com> (raw)
In-Reply-To: <CAM9d7ciKUYAdu97O3p5VRYGjXwvOv+4kgERXKM6mjr6OUbRQZA@mail.gmail.com>

On Mon, Apr 22, 2024 at 12:55 PM Namhyung Kim <namhyung@kernel.org> wrote:
>
> On Tue, Apr 2, 2024 at 2:46 PM <weilin.wang@intel.com> wrote:
> >
> > From: Weilin Wang <weilin.wang@intel.com>
> >
> > Add print out functions so that users could read retire latency values.
> >
> > Example output:
> >
> >  Performance counter stats for 'system wide':
> >
> >             25,717      MEM_INST_RETIRED.SPLIT_STORES    #      2.2 %  tma_split_stores
> >         28,365,080      CPU_CLK_UNHALTED.THREAD
> >              24.00      MEM_INST_RETIRED.SPLIT_STORES:p  #       96        4
> >
> >        2.054365083 seconds time elapsed
> >
> > This output of retire latency data is in format:
> >  <val> <event-name> # <sum> <count>.
>
> Nop, please follow the perf stat output format.  It'd be
>
>   <sum> <event-name> # ...
>
> Hmm.. maybe you don't need this at all as it'll have the event
> anyway (probably without the 'p' modifier like in the example
> above).
>
> Then I think you can just add a metric value saying the average
> latency in the comment area.
>
>   Performance counter stats for 'system wide':
>
>              25,717      MEM_INST_RETIRED.SPLIT_STORES    #      2.2 %
>  tma_split_stores
>                                                                      #
>      24.0  average latency

Sorry for the line wrapping.  They should be in the same line.

Thanks,
Namhyung

  reply	other threads:[~2024-04-22 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 21:44 [RFC PATCH v7 0/6] TPEBS counting mode support weilin.wang
2024-04-02 21:44 ` [RFC PATCH v7 1/6] perf stat: Parse and find tpebs events when parsing metrics to prepare for perf record sampling weilin.wang
2024-04-22 19:13   ` Namhyung Kim
2024-04-02 21:44 ` [RFC PATCH v7 2/6] perf data: Allow to use given fd in data->file.fd weilin.wang
2024-04-02 21:44 ` [RFC PATCH v7 3/6] perf stat: Fork and launch perf record when perf stat needs to get retire latency value for a metric weilin.wang
2024-04-22 19:45   ` Namhyung Kim
2024-04-02 21:44 ` [RFC PATCH v7 4/6] perf stat: Add retire latency values into the expr_parse_ctx to prepare for final metric calculation weilin.wang
2024-04-02 21:44 ` [RFC PATCH v7 5/6] perf stat: Add retire latency print functions to print out at the very end of print out weilin.wang
2024-04-22 19:55   ` Namhyung Kim
2024-04-22 20:02     ` Namhyung Kim [this message]
2024-04-02 21:44 ` [RFC PATCH v7 6/6] perf vendor events intel: Add MTL metric json files weilin.wang
2024-04-22 19:10 ` [RFC PATCH v7 0/6] TPEBS counting mode support Namhyung Kim
2024-04-23 16:58   ` Wang, Weilin

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=CAM9d7cjUkGFfbdWSxzs5tkLHdctjux1jGV0P_J9YsGP3QmWNOw@mail.gmail.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=caleb.biggers@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=mingo@redhat.com \
    --cc=perry.taylor@intel.com \
    --cc=peterz@infradead.org \
    --cc=samantha.alt@intel.com \
    --cc=weilin.wang@intel.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).