All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin King <benjaminking@web.de>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: Linux perf users <linux-perf-users@vger.kernel.org>
Subject: Re: perf tracepoints for regular user?
Date: Tue, 19 Jan 2016 06:02:44 +0100	[thread overview]
Message-ID: <20160119050244.GA13183@localhost> (raw)
In-Reply-To: <4927145.OUESRpdSEU@agathebauer>

Hi Milian,

On Sun, Jan 17, 2016 at 10:20:00PM +0100, Milian Wolff wrote:
>On Freitag, 15. Januar 2016 22:05:16 CET Benjamin King wrote:
>> I am trying to use 'perf stat -e uprobes:xyz' on a tracepoint that I have
>> previously set, but with no 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

Hm, that does not work for me. I can do the first remount, but not the
second:
-----
$ sudo mount -o remount,mode=755 /sys/kernel/debug/tracing
mount: can't find /sys/kernel/debug/tracing in /etc/fstab
$ mount|grep debug
none on /sys/kernel/debug type debugfs (rw,mode=755,mode=755)
-----

And then, I still can not see tracepoints as a regular user:
-----
$ perf list tracepoint

List of pre-defined events (to be used in -e):

$ 
-----

If this works for you, then maybe it's my version? I'm on 4.2.3


Cheers,
  Benjamin

  parent reply	other threads:[~2016-01-19  5:02 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 [this message]
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=20160119050244.GA13183@localhost \
    --to=benjaminking@web.de \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=milian.wolff@kdab.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.