mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com,
	Linux-kernel@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v4 3/4] perf util: Flexible to set block info output formats
Date: Mon, 27 Jan 2020 20:31:23 +0800	[thread overview]
Message-ID: <23bec83b-b55d-8e9f-5b74-f58f0cd4a618@linux.intel.com> (raw)
In-Reply-To: <6c35864b-e396-6865-12a9-2fd001b0f567@linux.intel.com>



On 1/20/2020 11:00 PM, Jin, Yao wrote:
> 
> 
> On 1/20/2020 5:47 PM, Jiri Olsa wrote:
>> On Thu, Jan 16, 2020 at 03:29:03AM +0800, Jin Yao wrote:
>>
>> SNIP
>>
>>> +                   block_hpps, nr_hpps);
>>> -    perf_hpp_list__register_sort_field(&bh->block_list,
>>> -        &block_fmts[PERF_HPP_REPORT__BLOCK_TOTAL_CYCLES_PCT].fmt);
>>> +    /* Sort by the first fmt */
>>> +    perf_hpp_list__register_sort_field(&bh->block_list, 
>>> &block_fmts[0].fmt);
>>>   }
>>> -static void process_block_report(struct hists *hists,
>>> -                 struct block_report *block_report,
>>> -                 u64 total_cycles)
>>> +static int process_block_report(struct hists *hists,
>>> +                struct block_report *block_report,
>>> +                u64 total_cycles, int *block_hpps,
>>> +                int nr_hpps)
>>>   {
>>>       struct rb_node *next = rb_first_cached(&hists->entries);
>>>       struct block_hist *bh = &block_report->hist;
>>>       struct hist_entry *he;
>>> -    init_block_hist(bh, block_report->fmts);
>>> +    if (nr_hpps > PERF_HPP_REPORT__BLOCK_MAX_INDEX)
>>
>> hum, should be '>=' above.. ?
>>
>> jirka
>>
> 
> '=' should be OK.
> 
> enum {
>      PERF_HPP_REPORT__BLOCK_TOTAL_CYCLES_PCT,
>      PERF_HPP_REPORT__BLOCK_LBR_CYCLES,
>      PERF_HPP_REPORT__BLOCK_CYCLES_PCT,
>      PERF_HPP_REPORT__BLOCK_AVG_CYCLES,
>      PERF_HPP_REPORT__BLOCK_RANGE,
>      PERF_HPP_REPORT__BLOCK_DSO,
>      PERF_HPP_REPORT__BLOCK_MAX_INDEX
> };
> 
> PERF_HPP_REPORT__BLOCK_MAX_INDEX is 6.
> 
> If nr_hpps is 6, for example, block_hpps[] is,
> 
>          int block_hpps[6] = {
>              PERF_HPP_REPORT__BLOCK_TOTAL_CYCLES_PCT,
>              PERF_HPP_REPORT__BLOCK_LBR_CYCLES,
>              PERF_HPP_REPORT__BLOCK_CYCLES_PCT,
>              PERF_HPP_REPORT__BLOCK_AVG_CYCLES,
>              PERF_HPP_REPORT__BLOCK_RANGE,
>              PERF_HPP_REPORT__BLOCK_DSO,
>          };
> 
>          block_info__create_report(session->evlist,
>                        rep->total_cycles,
>                                            block_hpps, 6,
>                                            &rep->nr_block_reports);
> 
> That should be legal.
> 
> Thanks
> Jin Yao

Hi Jiri,

Does this explanation make sense?

Thanks
Jin Yao

  reply	other threads:[~2020-01-27 12:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 19:29 [PATCH v4 1/4] perf util: Move block_pair_cmp to block-info Jin Yao
2020-01-15 19:29 ` [PATCH v4 2/4] perf util: Validate map/dso/sym before comparing blocks Jin Yao
2020-01-15 19:29 ` [PATCH v4 3/4] perf util: Flexible to set block info output formats Jin Yao
2020-01-20  9:47   ` Jiri Olsa
2020-01-20 14:50     ` Jin, Yao
2020-01-20  9:47   ` Jiri Olsa
2020-01-20 15:00     ` Jin, Yao
2020-01-27 12:31       ` Jin, Yao [this message]
2020-01-28  9:21         ` Jiri Olsa
2020-01-28 10:27           ` Jin, Yao
2020-01-15 19:29 ` [PATCH v4 4/4] perf util: Support color ops to print block percents in color Jin Yao

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=23bec83b-b55d-8e9f-5b74-f58f0cd4a618@linux.intel.com \
    --to=yao.jin@linux.intel.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@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

all inboxes | Powered by JetHome®