public inbox for linux-kernel@vger.kernel.org
 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 v3 3/4] perf util: Flexible to set block info output formats
Date: Tue, 14 Jan 2020 08:57:36 +0800	[thread overview]
Message-ID: <6b42909a-5c3a-42b4-a67f-5c10f97b9e0d@linux.intel.com> (raw)
In-Reply-To: <20200113101037.GF35080@krava>



On 1/13/2020 6:10 PM, Jiri Olsa wrote:
> On Wed, Jan 08, 2020 at 07:03:53AM +0800, Jin Yao wrote:
> 
> SNIP
> 
>>   int report__browse_block_hists(struct block_hist *bh, float min_percent,
>>   			       struct evsel *evsel, struct perf_env *env,
>> -			       struct annotation_options *annotation_opts)
>> +			       struct annotation_options *annotation_opts,
>> +			       bool release)
>>   {
>>   	int ret;
>>   
>> @@ -451,13 +477,17 @@ int report__browse_block_hists(struct block_hist *bh, float min_percent,
>>   		symbol_conf.report_individual_block = true;
>>   		hists__fprintf(&bh->block_hists, true, 0, 0, min_percent,
>>   			       stdout, true);
>> -		hists__delete_entries(&bh->block_hists);
>> +		if (release)
>> +			hists__delete_entries(&bh->block_hists);
>> +
>>   		return 0;
>>   	case 1:
>>   		symbol_conf.report_individual_block = true;
>>   		ret = block_hists_tui_browse(bh, evsel, min_percent,
>>   					     env, annotation_opts);
>> -		hists__delete_entries(&bh->block_hists);
>> +		if (release)
>> +			hists__delete_entries(&bh->block_hists);
>> +
>>   		return ret;
>>   	default:
>>   		return -1;
>> diff --git a/tools/perf/util/block-info.h b/tools/perf/util/block-info.h
>> index bfa22c59195d..0bf01e3a423d 100644
>> --- a/tools/perf/util/block-info.h
>> +++ b/tools/perf/util/block-info.h
>> @@ -44,7 +44,8 @@ enum {
>>   struct block_report {
>>   	struct block_hist	hist;
>>   	u64			cycles;
>> -	struct block_fmt	fmts[PERF_HPP_REPORT__BLOCK_MAX_INDEX];
>> +	struct block_fmt	*fmts;
> 
> hum, couldn't you just keep the array and use it instead of allocating it?
> it will never be bigger than PERF_HPP_REPORT__BLOCK_MAX_INDEX, no?
> 
> we could get rid of that release code
> 

Yes, that makes sense. I will keep the array.

Thanks
Jin Yao

> 
> jirka
> 

  reply	other threads:[~2020-01-14  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 23:03 [PATCH v3 1/4] perf util: Move block_pair_cmp to block-info Jin Yao
2020-01-07 23:03 ` [PATCH v3 2/4] perf util: Validate map/dso/sym before comparing blocks Jin Yao
2020-01-07 23:03 ` [PATCH v3 3/4] perf util: Flexible to set block info output formats Jin Yao
2020-01-13 10:10   ` Jiri Olsa
2020-01-14  0:57     ` Jin, Yao [this message]
2020-01-07 23:03 ` [PATCH v3 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=6b42909a-5c3a-42b4-a67f-5c10f97b9e0d@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