linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: wang@infradead.org, Jiri Olsa <jolsa@kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: using SDT events
Date: Tue, 27 Sep 2016 10:55:38 -0300	[thread overview]
Message-ID: <20160927135538.GN5588@kernel.org> (raw)

Masami,

	Testing something else (event aliases/JSON) I saw the many sdt
events available via 'perf list', decided to use the usual workflow,
failed, what am I doing wrong?


[root@jouet ~]# perf list sdt_qemu:pci*

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

  sdt_qemu:pci_cfg_read                              [SDT event]
  sdt_qemu:pci_cfg_write                             [SDT event]
  sdt_qemu:pci_update_mappings_add                   [SDT event]
  sdt_qemu:pci_update_mappings_del                   [SDT event]
[root@jouet ~]# perf record -e sdt_qemu:pci* -a
event syntax error: 'sdt_qemu:pci*'
                     \___ unknown tracepoint

Error:	File /sys/kernel/debug/tracing/events/sdt_qemu/pci* not found.
Hint:	Perhaps this kernel misses some CONFIG_ setting to enable this
feature?.

Run 'perf list' for a list of valid events

 Usage: perf record [<options>] [<command>]
    or: perf record [<options>] -- <command> [<options>]

    -e, --event <event>   event selector. use 'perf list' to list
available events
[root@jouet ~]# 

             reply	other threads:[~2016-09-27 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 13:55 Arnaldo Carvalho de Melo [this message]
2016-09-27 18:40 ` using SDT events Masami Hiramatsu
2016-09-28 13:34   ` Arnaldo Carvalho de Melo

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=20160927135538.GN5588@kernel.org \
    --to=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=wang@infradead.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).