mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
	Chad Paradis <chad.paradis@umit.maine.edu>,
	David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	Jiri Olsa <jolsa@redhat.com>, Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [patch] perf tools: perf list broken on ARM
Date: Tue, 10 Dec 2013 14:08:51 +0900	[thread overview]
Message-ID: <874n6hjnrw.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1312092250020.6229@vincent-weaver-1.um.maine.edu> (Vince Weaver's message of "Mon, 9 Dec 2013 22:58:46 -0500 (EST)")

On Mon, 9 Dec 2013 22:58:46 -0500 (EST), Vince Weaver wrote:
> On Tue, 10 Dec 2013, Namhyung Kim wrote:
>
>> Hi Vince,
>> Okay, the reason I set the bit was consideration of a very strict
>> perf_event_paranoid setting (-2).
>> 
>> So maybe we can try it again with the bit cleared after a failure, or
>> checking the paranoid setting first.
>
> If perf_event_paranoid is set to 2 then you should get EPERM rather than 
> ENOENT or EINVAL, right?  Maybe that could be used too.

Ah, yes, it's 2. :)  And it also can use the return value then.

>
> As a side note, why doesn't paranoid 2 block events that don't have
> exclude_hv set?

Hmm.. maybe because it predated the bit?

Thanks,
Namhyung

  reply	other threads:[~2013-12-10  5:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 21:58 Vince Weaver
2013-12-10  2:11 ` Namhyung Kim
2013-12-10  3:58   ` Vince Weaver
2013-12-10  5:08     ` Namhyung Kim [this message]
2013-12-30 20:39 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
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

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=874n6hjnrw.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=chad.paradis@umit.maine.edu \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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
all inboxes | Powered by JetHome®