From: Milian Wolff <milian.wolff@kdab.com>
To: Benjamin King <benjaminking@web.de>
Cc: Linux perf users <linux-perf-users@vger.kernel.org>
Subject: Re: perf tracepoints for regular user?
Date: Sun, 17 Jan 2016 22:20:00 +0100 [thread overview]
Message-ID: <4927145.OUESRpdSEU@agathebauer> (raw)
In-Reply-To: <20160115210516.GA6329@localhost>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On Freitag, 15. Januar 2016 22:05:16 CET Benjamin King wrote:
> Hi,
>
> I am trying to use 'perf stat -e uprobes:xyz' on a tracepoint that I have
> previously set, but with no success.
> I thought that I should be able to do that when allowing my user access to
> debugfs, but this is what I get:
>
> $ id -u;id -g
> 1001
> 1001
> $ mount|grep debug
> none on /sys/kernel/debug type debugfs (rw,uid=1001,gid=1001)
> $ ls /sys/kernel/debug
> acpi bluetooth cleancache dell_laptop dri extfrag ...
> $ ls /sys/kernel/debug/tracing/
> ls: cannot open directory /sys/kernel/debug/tracing/: Permission denied
>
> So, my user can't look in the tracing subdirectory and perf list doesn't
> show the uprobes either.
>
> I have also tried to ´sudo setcap cap_sys_admin+eip $(which perf)´, also
> without success.
Try these commands:
$ sudo mount -o remount,mode=755 /sys/kernel/debug
$ sudo mount -o remount,mode=755 /sys/kernel/debug/tracing
$ echo \"-1\" | sudo tee /proc/sys/kernel/perf_event_paranoid
HTH
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2016-01-17 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 21:05 perf tracepoints for regular user? Benjamin King
2016-01-17 21:20 ` Milian Wolff [this message]
2016-01-17 21:56 ` Milian Wolff
2016-01-19 5:02 ` Benjamin King
2016-01-19 22:18 ` Arnaldo Carvalho de Melo
2016-01-20 11:50 ` Aw: " Benjamin King
2016-01-21 14:05 ` Arnaldo Carvalho de Melo
2016-01-25 15:43 ` Benjamin King
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=4927145.OUESRpdSEU@agathebauer \
--to=milian.wolff@kdab.com \
--cc=benjaminking@web.de \
--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).