From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
David Ahern <dsahern@gmail.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
Stephane Eranian <eranian@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: perf/ftrace: does PERF_EVENT_IOC_SET_FILTER serve any purpose?
Date: Tue, 9 Jun 2015 17:11:34 -0300 [thread overview]
Message-ID: <20150609201134.GJ3136@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1506091605350.9662@vincent-weaver-1.umelst.maine.edu>
Em Tue, Jun 09, 2015 at 04:07:01PM -0400, Vince Weaver escreveu:
> On Tue, 9 Jun 2015, Steven Rostedt wrote:
>
> > 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.
>
> I am running 4.1-rc7 and was trying to use perf_4.0.
>
> If I use the kernel's version of perf it works.
>
> sigh.
Indeed, its always a shame when that happens, I had a similar reaction
when Steven told it was validating the filesystem type, completely
unnecessary, has been there for a long time :-\
Date: Tue Jul 21 12:20:22 2009 -0400
perf_counter: Add tracepoint support to perf list, perf stat
- Arnaldo
next prev parent reply other threads:[~2015-06-09 20:11 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 [this message]
2015-06-10 6:51 ` Ingo Molnar
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=20150609201134.GJ3136@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox