mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: acme@kernel.org, irogers@google.com, peterz@infradead.org,
	mingo@kernel.org, linux-kernel@vger.kernel.org,
	adrian.hunter@intel.com, ak@linux.intel.com, eranian@google.com
Subject: Re: [PATCH 6/9] perf report: Display the branch counter histogram
Date: Wed, 7 Aug 2024 07:57:38 -0400	[thread overview]
Message-ID: <bfc6c316-99c5-4115-b8f1-83890d7adf38@linux.intel.com> (raw)
In-Reply-To: <CAM9d7cgE=cDyeOyXrRZt53vKD=FRSqQRMz8=f=bGT-gzm2jjkg@mail.gmail.com>

Hi Namhyung,

On 2024-08-06 7:29 p.m., Namhyung Kim wrote:
>>>>            57.55%            2.5M        0.00%           3             |A   |-   |                 ...
>>>>            25.27%            1.1M        0.00%           2             |AA  |-   |                 ...
>>>>            15.61%          667.2K        0.00%           1             |A   |-   |                 ...
>>>>             0.16%            6.9K        0.81%         575             |A   |-   |                 ...
>>>>             0.16%            6.8K        1.38%         977             |AA  |-   |                 ...
>>>>             0.16%            6.8K        0.04%          28             |AA  |B   |                 ...
>>>>             0.15%            6.6K        1.33%         946             |A   |-   |                 ...
>>>>             0.11%            4.5K        0.06%          46             |AAA+|-   |                 ...
>>>>             0.10%            4.4K        0.88%         624             |A   |-   |                 ...
>>>>             0.09%            3.7K        0.74%         524             |AAA+|B   |                 ...
>>> I think this format assumes short width and might not work
>>> well when it has more events with bigger width.  Maybe
>>> A=<n>, B=<n> ?
>> The purpose of "AAA" is to print a histogram here which can give the end
>> user a straightforward image of the distribution. The A=<n> may not be
>> that obvious.
> I understand your point.  But I think we need to provide an easily
> parse-able format at least for CSV output.

I guess we may use a similar method of perf script in patch 8.

By default, the histogram will be output.
If an user want a number, -v should be used.

$perf report --total-cycles --stdio -v

# Sampled Cycles%  Sampled Cycles  Avg Cycles%  Avg Cycles
   Branch Counter                    >
# ...............  ..............  ...........  ..........
..............................  ..................>
#
            4.61%          116.4K        0.00%          91
        A=3+,B=1                     >
            4.28%          108.0K        0.00%          26
        A=1 ,B=1                     >
            3.42%           86.4K        0.00%          81
        A=3+,B=1                     >
            2.84%           71.6K        0.00%          50
        A=3+,B=-                     >
            2.65%           66.8K        0.00%         178
        A=3+,B=1          [__lock_acq>
            2.26%           57.1K        0.00%          44
        A=2 ,B=-                     >

Without -v,
$perf report --total-cycles --stdio

# Sampled Cycles%  Sampled Cycles  Avg Cycles%  Avg Cycles
   Branch Counter                    >
# ...............  ..............  ...........  ..........
..............................  ..................>
#
            4.61%          116.4K        0.00%          91
      |AAA+|B+  |                    >
            4.28%          108.0K        0.00%          26
      |A   |B   |                    >
            3.42%           86.4K        0.00%          81
      |AAA+|B+  |                    >
            2.84%           71.6K        0.00%          50
      |AAA+|-   |                    >
            2.65%           66.8K        0.00%         178
      |AAA+|B+  |         [__lock_acq>
            2.26%           57.1K        0.00%          44
      |AA  |-   |                    >

What do you think?

Thanks,
Kan

  parent reply	other threads:[~2024-08-07 11:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 20:03 [PATCH 0/9] Support branch counters in block annotation kan.liang
2024-07-03 20:03 ` [PATCH 1/9] perf report: Fix --total-cycles --stdio output error kan.liang
2024-08-02 20:25   ` Namhyung Kim
2024-07-03 20:03 ` [PATCH 2/9] perf report: Remove the first overflow check for branch counters kan.liang
2024-08-02 20:26   ` Namhyung Kim
2024-07-03 20:03 ` [PATCH 3/9] perf evlist: Save branch counters information kan.liang
2024-07-03 20:03 ` [PATCH 4/9] perf annotate: Save branch counters for each block kan.liang
2024-07-03 20:03 ` [PATCH 5/9] perf evsel: Assign abbr name for the branch counter events kan.liang
2024-08-03  0:14   ` Namhyung Kim
2024-08-06 14:11     ` Liang, Kan
2024-07-03 20:03 ` [PATCH 6/9] perf report: Display the branch counter histogram kan.liang
2024-08-03  0:18   ` Namhyung Kim
2024-08-06 14:39     ` Liang, Kan
2024-08-06 23:29       ` Namhyung Kim
2024-08-07  3:22         ` Andi Kleen
2024-08-07 11:57         ` Liang, Kan [this message]
2024-07-03 20:03 ` [PATCH 7/9] perf annotate: " kan.liang
2024-08-02 21:09   ` Andi Kleen
2024-08-06 14:42     ` Liang, Kan
2024-08-06 21:37       ` Liang, Kan
2024-08-06 23:02         ` Andi Kleen
2024-07-03 20:03 ` [PATCH 8/9] perf script: Add branch counters kan.liang
2024-07-03 20:03 ` [PATCH 9/9] perf test: Add new test cases for the branch counter feature kan.liang
2024-07-31 15:05 ` [PATCH 0/9] Support branch counters in block annotation Arnaldo Carvalho de Melo
2024-07-31 15:31   ` Liang, Kan
2024-07-31 17:00     ` 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=bfc6c316-99c5-4115-b8f1-83890d7adf38@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --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

all inboxes | Powered by JetHome®