From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
David Ahern <dsahern@gmail.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Stephane Eranian <eranian@gmail.com>,
Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: perf/ftrace: does PERF_EVENT_IOC_SET_FILTER serve any purpose?
Date: Wed, 10 Jun 2015 08:51:39 +0200 [thread overview]
Message-ID: <20150610065139.GA10200@gmail.com> (raw)
In-Reply-To: <20150609155506.3c7d5fc3@gandalf.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 9 Jun 2015 15:51:53 -0400 (EDT)
> Vince Weaver <vincent.weaver@maine.edu> wrote:
>
> > On Tue, 9 Jun 2015, David Ahern wrote:
> >
> > > On 6/9/15 12:30 PM, Vince Weaver wrote:
> > > > Hello
> > > >
> > > > I've been working on documenting the PERF_EVENT_IOC_SET_FILTER ioctl.
> > > >
> > > > I've been trying for the past 2 days and have been unable to get any
> > > > result except EINVAL.
> > > >
> > > > Does anyone ever use this ioctl? Does anyone know how to use this ioctl?
> > >
> > > yes and yes it works.
> > >
> > > perf record -e irq:irq_handler_entry --filter irq==28 \
> > > -e irq:softirq_entry --filter vec==6 -a \
> > > -- sleep 5
> >
> > # perf record -e irq:irq_handler_entry --filter irq==28 -e irq:softirq_entry --filter vec==6 -a -- sleep 5
> > invalid or unsupported event: 'irq:irq_handler_entry'
> > Run 'perf list' for a list of valid events
> >
> > perf list doesn't show any tracepoint events, despite having debugfs
> > mounted and running as root and /sys/kernel/debug/tracing/events/ being
> > populated.
> >
>
> What kernel are you using? You may need to update perf.
>
> We switched to a tracefs filesystem, but the old perf wont read any events if
> it's not located in debugfs. That is, it actually tested which filesystem the
> event files were mounted on, and if they didn't match the debugfs mount type, it
> ignored them. That was fixed recently.
That fix should probably be backported to stable kernels, to keep old instances
working.
Thanks,
Ingo
prev parent reply other threads:[~2015-06-10 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 18:30 perf/ftrace: does PERF_EVENT_IOC_SET_FILTER serve any purpose? Vince Weaver
2015-06-09 19:25 ` David Ahern
2015-06-09 19:51 ` Vince Weaver
2015-06-09 19:49 ` David Ahern
2015-06-09 20:02 ` Vince Weaver
2015-06-09 19:59 ` David Ahern
2015-06-09 20:18 ` Vince Weaver
2015-06-09 19:55 ` Steven Rostedt
2015-06-09 20:07 ` Vince Weaver
2015-06-09 20:11 ` Arnaldo Carvalho de Melo
2015-06-10 6:51 ` Ingo Molnar [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=20150610065139.GA10200@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=eranian@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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 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.