public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.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: Mon, 12 Aug 2019 10:35:43 +0200	[thread overview]
Message-ID: <20190812083543.GA11752@krava> (raw)
In-Reply-To: <20190809233029.12265-1-yao.jin@linux.intel.com>

On Sat, Aug 10, 2019 at 07:30:29AM +0800, Jin Yao wrote:

SNIP

>  static int process_block_per_sym(struct hist_entry *he)
> @@ -684,6 +694,21 @@ static struct hist_entry *get_block_pair(struct hist_entry *he,
>  	return NULL;
>  }
>  
> +static void init_spark_values(unsigned long *svals, int num)
> +{
> +	for (int i = 0; i < num; i++)
> +		svals[i] = 0;
> +}
> +
> +static void update_spark_value(unsigned long *svals, int num,
> +			       struct stats *stats, u64 val)
> +{
> +	int n = stats->n;
> +
> +	if (n < num)
> +		svals[n] = val;
> +}
> +
>  static void compute_cycles_diff(struct hist_entry *he,
>  				struct hist_entry *pair)
>  {
> @@ -692,6 +717,23 @@ static void compute_cycles_diff(struct hist_entry *he,
>  		pair->diff.cycles =
>  			pair->block_info->cycles_aggr / pair->block_info->num_aggr -
>  			he->block_info->cycles_aggr / he->block_info->num_aggr;
> +

should below code be executed only for show_noisy?

jirka

> +		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);
> +		}
>  	}
>  }

SNIP

  reply	other threads:[~2019-08-12  8:35 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 [this message]
2019-08-13  0:40   ` Jin, Yao
2019-08-12  8:35 ` Jiri Olsa
2019-08-13  0:49   ` Jin, Yao
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=20190812083543.GA11752@krava \
    --to=jolsa@redhat.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=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.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