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] perf diff: Report noisy for cycles diff
Date: Tue, 13 Aug 2019 08:49:30 +0800 [thread overview]
Message-ID: <28ce9bd0-dbbf-9e27-d40d-dafb0667a3b8@linux.intel.com> (raw)
In-Reply-To: <20190812083549.GB11752@krava>
On 8/12/2019 4:35 PM, Jiri Olsa wrote:
> On Sat, Aug 10, 2019 at 07:30:29AM +0800, Jin Yao wrote:
>
> SNIP
>
>> +
>> + init_stats(&pair->diff.stats);
>> + init_spark_values(pair->diff.svals, NUM_SPARKS);
>> +
>> + for (int i = 0; i < pair->block_info->num; i++) {
>> + u64 val;
>> +
>> + if (i >= he->block_info->num || i >= NUM_SPARKS)
>> + break;
>> +
>> + val = labs(pair->block_info->cycles_spark[i] -
>> + he->block_info->cycles_spark[i]);
>> +
>> + update_spark_value(pair->diff.svals, NUM_SPARKS,
>> + &pair->diff.stats, val);
>> + update_stats(&pair->diff.stats, val);
>> + }
>> }
>> }
>>
>> @@ -1250,6 +1292,8 @@ static const struct option options[] = {
>> "Show period values."),
>> OPT_BOOLEAN('F', "formula", &show_formula,
>> "Show formula."),
>> + OPT_BOOLEAN('n', "noisy", &show_noisy,
>> + "Show cycles noisy - WARNING: use only with -c cycles."),
>
> this should be more 'cycles' specific like --cycles-noisy or --cycles-hist?
>
> also I dont think we should use 'n' for this, just the long option
>
> jirka
>
Yes, it's cycles specific. Maybe --cycles-hist is better and the long
option should be enough. We can reserve -n for future feature. :)
Thanks
Jin Yao
next prev parent reply other threads:[~2019-08-13 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 23:30 [PATCH v3] perf diff: Report noisy for cycles diff Jin Yao
2019-08-12 8:35 ` Jiri Olsa
2019-08-13 0:40 ` Jin, Yao
2019-08-12 8:35 ` Jiri Olsa
2019-08-13 0:49 ` Jin, Yao [this message]
2019-08-12 8:35 ` Jiri Olsa
2019-08-13 4:13 ` Jin, Yao
2019-08-13 12:14 ` Jiri Olsa
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=28ce9bd0-dbbf-9e27-d40d-dafb0667a3b8@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