All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>,
	David Ahern <dsahern@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCHv2] perf/stat: Report unsupported events properly
Date: Tue, 17 Feb 2015 10:13:44 +0000	[thread overview]
Message-ID: <54E31458.3060009@arm.com> (raw)
In-Reply-To: <20150213205026.GA31817@redhat.com>

On 13/02/15 20:50, Arnaldo Carvalho de Melo wrote:
> Em Fri, Feb 13, 2015 at 12:39:24PM -0700, David Ahern escreveu:
>>
>>
>> On 02/13/2015 11:40 AM, Suzuki K. Poulose wrote:
>>> From: "Suzuki K. Poulose" <suzuki.poulose@arm.com>
>>>
>>> Commit 1971f59 (perf stat: Use read_counter in read_counter_aggr )
>>> broke the perf stat output for unsupported counters.
>>>
>>>   $ perf stat -v -a -C 0 -e CCI_400/config=24/ sleep 1
>>>   Warning:
>>>   CCI_400/config=24/ event is not supported by the kernel.
>>>
>>>    Performance counter stats for 'system wide':
>>>
>>>                    0      CCI_400/config=24/
>>>
>>>          1.080265400 seconds time elapsed
>>>
>>> Where it used to be :
>>>
>>> $ perf stat -v -a -C 0 -e CCI_400/config=24/ sleep 1
>>>   Warning:
>>>   CCI_400/config=24/ event is not supported by the kernel.
>>>
>>>    Performance counter stats for 'system wide':
>>>
>>>      <not supported>      CCI_400/config=24/
>>>
>>>          1.083840675 seconds time elapsed
>>>
>>> This patch fixes the issues by checking if the counter is supported,
>>> before reading and logging the counter value.
>>>
>>> Cc: Jiri Olsa <jolsa@kernel.org>
>>> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
>>> Signed-off-by: Suzuki K. Poulose <suzuki.poulose@arm.com>
>>> ---
>>>   tools/perf/builtin-stat.c |    5 ++++-
>>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
>>> index e598e4e..d28949d 100644
>>> --- a/tools/perf/builtin-stat.c
>>> +++ b/tools/perf/builtin-stat.c
>>> @@ -510,6 +510,9 @@ static int read_counter(struct perf_evsel *counter)
>>>   	int ncpus = perf_evsel__nr_cpus(counter);
>>>   	int cpu, thread;
>>>
>>> +	if (!counter->supported)
>>> +		return -ENOENT;
>>> +
>>>   	if (counter->system_wide)
>>>   		nthreads = 1;
>>>
>>> @@ -1285,7 +1288,7 @@ static void print_counter_aggr(struct perf_evsel *counter, char *prefix)
>>>   	if (prefix)
>>>   		fprintf(output, "%s", prefix);
>>>
>>> -	if (scaled == -1) {
>>> +	if (scaled == -1 || !counter->supported) {
>>>   		fprintf(output, "%*s%s",
>>>   			csv_output ? 0 : 18,
>>>   			counter->supported ? CNTR_NOT_COUNTED : CNTR_NOT_SUPPORTED,
>>>
>>
>> Just hit this as well.
>>
>> Acked-and-Tested-by: David Ahern <dsahern@gmail.com>
>
> Gack, 10ms after I sent my pre-California pull req :-\
>
> Will go in the next one :-)
I think this may need to goto 3.19 stable series as well. Missed that. 
Do you want me to send it there ?

Cheers
Suzuki



  reply	other threads:[~2015-02-17 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 18:40 [PATCHv2] perf/stat: Report unsupported events properly Suzuki K. Poulose
2015-02-13 19:39 ` David Ahern
2015-02-13 20:50   ` Arnaldo Carvalho de Melo
2015-02-17 10:13     ` Suzuki K. Poulose [this message]
2015-02-27 19:40     ` David Ahern
2015-03-03  6:22 ` [tip:perf/core] perf stat: " tip-bot for Suzuki K. Poulose

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=54E31458.3060009@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.