From: Benjamin King <benjaminking@web.de>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: Re: perf tracepoints for regular user?
Date: Mon, 25 Jan 2016 16:43:43 +0100 [thread overview]
Message-ID: <20160125154343.GA11166@localhost> (raw)
In-Reply-To: <20160121140505.GB2312@kernel.org>
On Thu, Jan 21, 2016 at 11:05:05AM -0300, Arnaldo Carvalho de Melo wrote:
>Not having tracefs, if that is indeed the case, only means that the
>remount isn't needed, as what is in tracefs is what, before its
>existence, lived in a debugfs directory, /sys/kernel/debug/tracing, i.e.
>remounting just /sys/kernel/debug/ would then be enough.
I could not make /sys/kernel/debug/tracing available to a regular users even
after upgrading to kernel 4.4, so I just did a desperate system upgrade and -
lo and behold - it now works, by which I mean
1) tracefs is mounted and when remounted world readable...
2) ...regular users can read /sys/kernel/debug/tracing/uprobe_events and...
3) ...see the probes in perf and...
4) ...use them for tracing.
So it was all my fault, being too lazy to upgrade, thanks for the help and
sorry for the noise!
Cheers,
Benjamin
prev parent reply other threads:[~2016-01-25 15:43 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
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 [this message]
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=20160125154343.GA11166@localhost \
--to=benjaminking@web.de \
--cc=acme@kernel.org \
--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).