public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	linux-kernel@vger.kernel.org,
	Chad Paradis <chad.paradis@umit.maine.edu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [patch] perf tools: perf list broken on ARM
Date: Thu, 9 Jan 2014 09:12:06 -0300	[thread overview]
Message-ID: <20140109121206.GA30069@ghostprotocols.net> (raw)
In-Reply-To: <871u0hd0x4.fsf@sejong.aot.lge.com>

Em Thu, Jan 09, 2014 at 05:17:27PM +0900, Namhyung Kim escreveu:
> Hi Vince,
> 
> On Wed, 8 Jan 2014 16:30:17 -0500 (EST), Vince Weaver wrote:
> > just checking on the status of this patch.  Am I sending it to the wrong 
> > place?  Did it get lost in the post-holiday e-mail purges?  
> >
> > The bug is annoying if you're trying to use perf on ARM systems.
> 
> Right, acme, would you please merge this?

I will, but having a patch authored by someone and Acked-by that same
person looks weird, so, to clarify, this was written by Vince, acked by
you, right?

- Arnaldo
 
> Thanks,
> Namhyung
> 
> >
> > On Mon, 30 Dec 2013, Vince Weaver wrote:
> >
> >> 
> >> "perf list" listing of hardware events doesn't work on older ARM devices.
> >> The change enabling event detection:
> >> 
> >>  commit b41f1cec91c37eeea6fdb15effbfa24ea0a5536b
> >>  Author: Namhyung Kim <namhyung.kim@lge.com>
> >>  Date:   Tue Aug 27 11:41:53 2013 +0900
> >> 
> >>      perf list: Skip unsupported events
> >> 
> >> 
> >> uses the following code in tools/perf/util/parse-events.c:
> >> 
> >>         struct perf_event_attr attr = {
> >>                 .type = type,
> >>                 .config = config,
> >>                 .disabled = 1,
> >>                 .exclude_kernel = 1,
> >>         };
> >> 
> >> On ARM machines pre-dating the Cortex-A15 this doesn't work, as
> >> these machines don't support .exclude_kernel.  So starting with 3.12
> >> "perf list" does not report any hardware events at all on older
> >> machines (seen on Rasp-Pi, Pandaboard, Beagleboard, etc).
> >> 
> >> This version of the patch makes changes suggested by Namhyung Kim
> >> to check for EACCESS and retry (instead of just dropping
> >> the exclude_kernel) so we can properly handle machines where 
> >> /proc/sys/kernel/perf_event_paranoid is set to 2.
> >> 
> >> Reported-by: Chad Paradis <chad.paradis@umit.maine.edu>
> >> Signed-off-by: Vince Weaver <vincent.weaver@maine.edu>
> >> Acked-by: Namhyung Kim <namhyung@kernel.org>
> >> 
> >> diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
> >> index 6de6f89..1fa98b9 100644
> >> --- a/tools/perf/util/parse-events.c
> >> +++ b/tools/perf/util/parse-events.c
> >> @@ -1082,12 +1082,12 @@ int is_valid_tracepoint(const char *event_string)
> >>  static bool is_event_supported(u8 type, unsigned config)
> >>  {
> >>  	bool ret = true;
> >> +	int open_return;
> >>  	struct perf_evsel *evsel;
> >>  	struct perf_event_attr attr = {
> >>  		.type = type,
> >>  		.config = config,
> >>  		.disabled = 1,
> >> -		.exclude_kernel = 1,
> >>  	};
> >>  	struct {
> >>  		struct thread_map map;
> >> @@ -1099,7 +1099,20 @@ static bool is_event_supported(u8 type, unsigned config)
> >>  
> >>  	evsel = perf_evsel__new(&attr);
> >>  	if (evsel) {
> >> -		ret = perf_evsel__open(evsel, NULL, &tmap.map) >= 0;
> >> +		open_return = perf_evsel__open(evsel, NULL, &tmap.map);
> >> +		ret = open_return >= 0;
> >> +
> >> +		if (open_return == -EACCES) {
> >> +			/*
> >> +			 * This happens if the paranoid value
> >> +			 * /proc/sys/kernel/perf_event_paranoid is set to 2
> >> +			 * Re-run with exclude_kernel set; we don't do that
> >> +			 * by default as some ARM machines do not support it.
> >> +			 *
> >> +			 */
> >> +			evsel->attr.exclude_kernel = 1;
> >> +			ret = perf_evsel__open(evsel, NULL, &tmap.map) >= 0;
> >> +		}
> >>  		perf_evsel__delete(evsel);
> >>  	}
> >>  
> >> 
> >
> > Vince Weaver
> > vincent.weaver@maine.edu
> > http://www.eece.maine.edu/~vweaver/

  reply	other threads:[~2014-01-09 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 20:39 [patch] perf tools: perf list broken on ARM Vince Weaver
2014-01-08 21:30 ` Vince Weaver
2014-01-09  8:17   ` Namhyung Kim
2014-01-09 12:12     ` Arnaldo Carvalho de Melo [this message]
2014-01-09 12:37       ` Namhyung Kim
2014-01-09 12:48         ` Arnaldo Carvalho de Melo
2014-02-05 20:34           ` Vince Weaver
2014-02-06 13:38             ` Arnaldo Carvalho de Melo
2014-01-09  9:02   ` Peter Zijlstra
2014-02-22 17:55 ` [tip:perf/core] perf list: Fix checking for supported events on older kernels tip-bot for Vince Weaver
  -- strict thread matches above, loose matches on Subject: below --
2013-12-09 21:58 [patch] perf tools: perf list broken on ARM Vince Weaver
2013-12-10  2:11 ` Namhyung Kim
2013-12-10  3:58   ` Vince Weaver
2013-12-10  5:08     ` Namhyung Kim

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=20140109121206.GA30069@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=chad.paradis@umit.maine.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=vincent.weaver@maine.edu \
    /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