From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ashay Rane <ashay.r@gmail.com>
Cc: linux-perf-users@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Ashay Rane <ashay.rane@tacc.utexas.edu>
Subject: Re: [PATCH 1/1] Fix number of events displayed in header
Date: Tue, 20 Mar 2012 13:46:16 -0600 [thread overview]
Message-ID: <4F68DE88.1040301@gmail.com> (raw)
In-Reply-To: <20120320194241.GA24870@infradead.org>
On 3/20/12 1:42 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Mar 20, 2012 at 02:23:16PM -0500, Ashay Rane escreveu:
>> From: Ashay Rane<ashay.rane@tacc.utexas.edu>
>
> Too short a changeset comment, please elaborate.
>
> The change at least would have to be changed from
>
> "Events: %llu", total_period
>
> to
>
> "Total period: %llu", total_period
>
> To be consistent in what we call "Events", i.e. right now it is telling
> the number of PERF_RECORD_SAMPLE events, with your change it woul0d be
> showing the sum of the periods in all samples.
Does not seem appropriate to change from number of sample events to
period for all event types. This change assumes the event is cycles,
cpu-clock or task-clock.
David
>
> - Arnaldo
>
>> Signed-off-by: Ashay Rane<ashay.rane@tacc.utexas.edu>
>> ---
>> tools/perf/builtin-report.c | 6 ++----
>> 1 files changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
>> index 25d34d4..58a20cf 100644
>> --- a/tools/perf/builtin-report.c
>> +++ b/tools/perf/builtin-report.c
>> @@ -202,11 +202,9 @@ static size_t hists__fprintf_nr_sample_events(struct hists *self,
>> const char *evname, FILE *fp)
>> {
>> size_t ret;
>> - char unit;
>> - unsigned long nr_events = self->stats.nr_events[PERF_RECORD_SAMPLE];
>> + u64 total_period = self->stats.total_period;
>>
>> - nr_events = convert_unit(nr_events,&unit);
>> - ret = fprintf(fp, "# Events: %lu%c", nr_events, unit);
>> + ret = fprintf(fp, "# Events: %llu", total_period);
>> if (evname != NULL)
>> ret += fprintf(fp, " %s", evname);
>> return ret + fprintf(fp, "\n#\n");
>> --
>> 1.7.4.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-20 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 19:23 [PATCH 1/1] Fix number of events displayed in header Ashay Rane
2012-03-20 19:42 ` Arnaldo Carvalho de Melo
2012-03-20 19:46 ` David Ahern [this message]
2012-03-20 19:47 ` Peter Zijlstra
2012-03-20 19:51 ` Ashay Rane
2012-03-20 19:59 ` Peter Zijlstra
2012-03-20 20:04 ` Ashay Rane
2012-03-20 20:09 ` Peter Zijlstra
2012-03-20 20:27 ` Ashay Rane
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 22:24 Ashay Rane
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=4F68DE88.1040301@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=ashay.r@gmail.com \
--cc=ashay.rane@tacc.utexas.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).