All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: 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>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf/ftrace: does PERF_EVENT_IOC_SET_FILTER serve any purpose?
Date: Tue, 09 Jun 2015 13:49:16 -0600	[thread overview]
Message-ID: <5577433C.5040702@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1506091547180.9662@vincent-weaver-1.umelst.maine.edu>

On 6/9/15 1:51 PM, Vince Weaver wrote:

> # 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.

Do you see this:

# ls /sys/kernel/debug/tracing/events/irq/irq_handler_entry/
enable  filter  format  id  trigger

It's used in kernel/irq/handle.c, handle_irq_event_percpu(). As I recall 
this tracepoint has been around a long time.

David

  reply	other threads:[~2015-06-09 19:49 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 [this message]
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

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=5577433C.5040702@gmail.com \
    --to=dsahern@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --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.