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 v1 2/3] perf stat: Support coresum event qualifier
Date: Sat, 16 Mar 2019 07:08:07 +0800 [thread overview]
Message-ID: <b2ba589e-d01a-18a1-57cc-3a6626961114@linux.intel.com> (raw)
In-Reply-To: <20190315133453.GB5200@krava>
On 3/15/2019 9:34 PM, Jiri Olsa wrote:
> On Sat, Mar 16, 2019 at 12:04:15AM +0800, Jin Yao wrote:
>
> SNIP
>
>> +static void print_counter_aggrdata(struct perf_stat_config *config,
>> + struct perf_evsel *counter, int s,
>> + char *prefix, bool metric_only,
>> + bool *first)
>> +{
>> + struct aggr_data ad;
>> + FILE *output = config->output;
>> + u64 ena, run, val;
>> + int id, nr;
>> + double uval;
>> +
>> + ad.id = id = config->aggr_map->map[s];
>> + ad.val = ad.ena = ad.run = 0;
>> + ad.nr = 0;
>> + if (!collect_data(config, counter, aggr_cb, &ad))
>> + return;
>> +
>> + nr = ad.nr;
>> + ena = ad.ena;
>> + run = ad.run;
>> + val = ad.val;
>> + if (*first && metric_only) {
>> + *first = false;
>> + aggr_printout(config, counter, id, nr);
>> + }
>> + if (prefix && !metric_only)
>> + fprintf(output, "%s", prefix);
>> +
>> + uval = val * counter->scale;
>> + printout(config, id, nr, counter, uval, prefix,
>> + run, ena, 1.0, &rt_stat);
>> + if (!metric_only)
>> + fputc('\n', output);
>> +}
>
> plese put the factoring out of print_counter_aggrdata function
> into separate patch
>
> thanks,
> jirka
>
>
OK!
Thanks
Jin Yao
>> +
>> static void print_aggr(struct perf_stat_config *config,
>> struct perf_evlist *evlist,
>> char *prefix)
>> @@ -606,9 +649,7 @@ static void print_aggr(struct perf_stat_config *config,
>> bool metric_only = config->metric_only;
>> FILE *output = config->output;
>> struct perf_evsel *counter;
>> - int s, id, nr;
>> - double uval;
>> - u64 ena, run, val;
>> + int s;
>> bool first;
>>
>> if (!(config->aggr_map || config->aggr_get_id))
>> @@ -621,36 +662,16 @@ static void print_aggr(struct perf_stat_config *config,
>> * Without each counter has its own line.
>> */
>> for (s = 0; s < config->aggr_map->nr; s++) {
>> - struct aggr_data ad;
>> if (prefix && metric_only)
>> fprintf(output, "%s", prefix);
>>
>> - ad.id = id = config->aggr_map->map[s];
>> first = true;
>> evlist__for_each_entry(evlist, counter) {
>> if (is_duration_time(counter))
>> continue;
>> -
>> - ad.val = ad.ena = ad.run = 0;
>> - ad.nr = 0;
>> - if (!collect_data(config, counter, aggr_cb, &ad))
>> - continue;
>> - nr = ad.nr;
>> - ena = ad.ena;
>> - run = ad.run;
>> - val = ad.val;
>> - if (first && metric_only) {
>> - first = false;
>> - aggr_printout(config, counter, id, nr);
>> - }
>> - if (prefix && !metric_only)
>> - fprintf(output, "%s", prefix);
>> -
>> - uval = val * counter->scale;
>> - printout(config, id, nr, counter, uval, prefix,
>> - run, ena, 1.0, &rt_stat);
>> - if (!metric_only)
>> - fputc('\n', output);
>> + print_counter_aggrdata(config, counter, s,
>> + prefix, metric_only,
>> + &first);
>
> SNIP
>
next prev parent reply other threads:[~2019-03-15 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 16:04 [PATCH v1 0/3] perf: Support a new coresum event qualifier Jin Yao
2019-03-15 13:34 ` Jiri Olsa
2019-03-15 23:07 ` Jin, Yao
2019-03-15 23:26 ` Andi Kleen
2019-03-15 23:31 ` Jin, Yao
2019-03-15 16:04 ` [PATCH v1 1/3] perf: Add a " Jin Yao
2019-03-15 16:04 ` [PATCH v1 2/3] perf stat: Support " Jin Yao
2019-03-15 13:34 ` Jiri Olsa
2019-03-15 23:08 ` Jin, Yao [this message]
2019-03-15 16:04 ` [PATCH v1 3/3] perf test: Add a simple test for term coresum 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=b2ba589e-d01a-18a1-57cc-3a6626961114@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