From: aburov@orc-group.com (Andrei Burov)
Subject: [lttng-dev] Unable to use stalled-cycles-frontend perf counter
Date: Tue, 2 Jun 2015 17:32:44 +0300 [thread overview]
Message-ID: <556DBE8C.7030306@orc-group.com> (raw)
Hello!
I've encountered a problem with lttng (LTTng Trace Control) 2.5.0 -
Fumisterie. When I am trying to access stalled-cycles-frontend perf
counter, it somehow corrupts the tracefile. Below is a simple test which
is using code of hello program from lttng doc.
$ls
hello hello.c hello-tp.c hello-tp.h hello-tp.o hello-tp.tp
$lttng create
Session auto-20150602-160131 created.
Traces will be written in /home/user/lttng-traces/auto-20150602-160131
$lttng enable-event -u hello_world:my_first_tracepoint
UST event hello_world:my_first_tracepoint created in channel channel0
$lttng add-context -u -t perf:thread:stalled-cycles-frontend
UST context perf:thread:stalled-cycles-frontend added to all channels
$lttng start
Tracing started for session auto-20150602-160131
$./hello
Hello, World!
Press Enter to continue...
Quitting now!
lttng stop
Waiting for data availability.
Tracing stopped for session auto-20150602-160131
$lttng view
Trace directory: /home/user/lttng-traces/auto-20150602-160131
[error] Cannot open any trace for reading.
[error] opening trace "/home/user/lttng-traces/auto-20150602-160131" for
reading.
[error] none of the specified trace paths could be opened.
$lttng destroy && lttng create
Session auto-20150602-160131 destroyed
Session auto-20150602-160224 created.
Traces will be written in /home/user/lttng-traces/auto-20150602-160224
$lttng enable-event -u hello_world:my_first_tracepoint
UST event hello_world:my_first_tracepoint created in channel channel0
$lttng add-context -u -t perf:thread:cycles
UST context perf:thread:cycles added to all channels
$lttng start
Tracing started for session auto-20150602-160224
$./hello
Hello, World!
Press Enter to continue...
Quitting now!
$lttng stop
Waiting for data availability.
Tracing stopped for session auto-20150602-160224
$lttng view
Trace directory: /home/user/lttng-traces/auto-20150602-160224
[16:03:14.431724221] (+?.?????????) krypton.com
hello_world:my_first_tracepoint: { cpu_id = 1 }, { perf_thread_cycles =
281474976715686 }, { my_string_field = "hi there!", my_integer_field = 23 }
[16:03:14.432296656] (+0.000572435) krypton.com
hello_world:my_first_tracepoint: { cpu_id = 1 }, { perf_thread_cycles =
281474976722947 }, { my_string_field = "./hello", my_integer_field = 0 }
[16:03:14.432300284] (+0.000003628) krypton.com
hello_world:my_first_tracepoint: { cpu_id = 1 }, { perf_thread_cycles =
281474976726469 }, { my_string_field = "x^2", my_integer_field = 1 }
Thanks for your help!
Andrei
________________________________
This e-mail is confidential and may contain legally privileged information. It is intended only for the addressees. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message from your system.
next reply other threads:[~2015-06-02 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 14:32 Andrei Burov [this message]
2015-06-03 5:15 ` Mathieu Desnoyers
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=556DBE8C.7030306@orc-group.com \
--to=aburov@orc-group.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox