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 v2] perf diff: Report noisy for cycles diff
Date: Tue, 6 Aug 2019 19:39:20 +0800	[thread overview]
Message-ID: <085edaa4-e8f2-f501-5ffc-4d07b4ea85ad@linux.intel.com> (raw)
In-Reply-To: <20190806083413.GG7695@krava>



On 8/6/2019 4:34 PM, Jiri Olsa wrote:
> On Thu, Jul 25, 2019 at 06:14:32AM +0800, Jin Yao wrote:
> 
> SNIP
> 
>> +}
>> +
>>   double avg_stats(struct stats *stats)
>>   {
>>   	return stats->mean;
>> diff --git a/tools/perf/util/stat.h b/tools/perf/util/stat.h
>> index 95b4de7a9d51..3448d319a220 100644
>> --- a/tools/perf/util/stat.h
>> +++ b/tools/perf/util/stat.h
>> @@ -8,14 +8,18 @@
>>   #include <sys/time.h>
>>   #include <sys/resource.h>
>>   #include <sys/wait.h>
>> +#include <stdio.h>
>>   #include "xyarray.h"
>>   #include "rblist.h"
>>   #include "perf.h"
>>   #include "event.h"
>>   
>> +#define NUM_SPARK_VALS	8 /* support spark line on first N items */
>> +
>>   struct stats {
>>   	double n, mean, M2;
>>   	u64 max, min;
>> +	unsigned long svals[NUM_SPARK_VALS];
>>   };
> 
> please do it without changing the 'struct stats', it's all
> over the place and diff would be the only user
> 
> thanks
> jirka
> 

OK, I see. I will save the svals[] in other struct.

Thanks
Jin Yao




  reply	other threads:[~2019-08-06 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 22:14 [PATCH v2] perf diff: Report noisy for cycles diff Jin Yao
2019-08-06  0:16 ` Jin, Yao
2019-08-06  8:34 ` Jiri Olsa
2019-08-06 11:39   ` Jin, Yao [this message]
2019-08-06  8:34 ` Jiri Olsa
2019-08-06 11:46   ` Jin, Yao
2019-08-06  8:34 ` Jiri Olsa
2019-08-06 11:32   ` 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=085edaa4-e8f2-f501-5ffc-4d07b4ea85ad@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