From: Lin Ming <minggr@gmail.com>
To: linux-perf-users@vger.kernel.org
Cc: 陳韋任 <chenwj@iis.sinica.edu.tw>
Subject: Re: What perf_event_paranoid can do?
Date: Mon, 21 Mar 2011 16:35:11 +0800 [thread overview]
Message-ID: <AANLkTimJ36H76Z77AmauMWtZ9hOM62X1Y2jJa5H6fxWa@mail.gmail.com> (raw)
In-Reply-To: <20110321061435.GA52815@cs.nctu.edu.tw>
On Mon, Mar 21, 2011 at 2:14 PM, 陳韋任 <chenwj@iis.sinica.edu.tw> wrote:
> Hi, folks
>
> I don't know what "perf_event_paranoid" is for. Sometimes
> `perf` told me tweaking perf_event_paranoid. For example,
>
> $ perf stat -e branches:pp ls
> No permission to collect stats.
> Consider tweaking /proc/sys/kernel/perf_event_paranoid.
>
> I cannot find any document talks about what perf_event_paranoid
> is and what we can do on it.
It's used to control if some action is allowed or not for normal user.
See comments at kernel/perf_event.c:
/*
* perf event paranoia level:
* -1 - not paranoid at all
* 0 - disallow raw tracepoint access for unpriv
* 1 - disallow cpu events for unpriv
* 2 - disallow kernel profiling for unpriv
*/
Lin Ming
>
> Any suggestion appreciated.
>
> Regards,
> chenwj
>
> --
> Wei-Ren Chen (陳韋任)
> Parallel Processing Lab, Institute of Information Science,
> Academia Sinica, Taiwan (R.O.C.)
> Tel:886-2-2788-3799 #1667
> --
> 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:[~2011-03-21 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 6:14 What perf_event_paranoid can do? 陳韋任
2011-03-21 8:35 ` Lin Ming [this message]
2011-03-21 9:19 ` 陳韋任
2011-03-21 9:56 ` 陳韋任
2011-03-21 13:46 ` Lin Ming
2011-03-21 13:51 ` Lin Ming
2011-03-22 1:10 ` 陳韋任
2011-03-22 1:55 ` 陳韋任
2011-03-22 3:09 ` Lin Ming
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=AANLkTimJ36H76Z77AmauMWtZ9hOM62X1Y2jJa5H6fxWa@mail.gmail.com \
--to=minggr@gmail.com \
--cc=chenwj@iis.sinica.edu.tw \
--cc=linux-perf-users@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 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).