From: "Ronny Tschüter" <Ronny.Tschueter@tu-dresden.de>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Tracing of power:power_start events doesn't work
Date: Mon, 03 May 2010 15:19:34 +0200 [thread overview]
Message-ID: <4BDECD66.2010906@tu-dresden.de> (raw)
Hello,
i use kernel version 2.6.33.2 (x86-64, Core 2 Duo) and the perf events
to track frequency and c states of my cpu. But if i want to trace
power:power_start events, it does not work. After typing
echo "power:power_start" | sudo tee set_event
on the console, the trace doesn't contain such events.
power:power_frequency and power:power_end events are reported correctly
by the system. I read in the mailing list that Robert Schoene had a
similiar problem, but with power:power_end events. Is there a known bug
regarding to trace_power_start methods in process.c?
Bye Ronny
--
Ronny Tschueter
Technische Universität Dresden
Center for Information Services
and High Performance Computing (ZIH)
D-01062 Dresden
Germany
Office: Willersbau, room A31
Phone: (+49) 351/463-35448
E-Mail: ronny.tschueter@tu-dresden.de
WWW: http://www.tu-dresden.de/zih
next reply other threads:[~2010-05-03 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 13:19 Ronny Tschüter [this message]
2010-05-03 21:36 ` Tracing of power:power_start events doesn't work Frank Ch. Eigler
2010-05-05 0:31 ` Steven Rostedt
2010-05-05 6:34 ` Ronny Tschüter
2010-05-05 17:23 ` Frederic Weisbecker
2010-05-06 6:32 ` Ronny Tschüter
2010-05-05 14:11 ` Ronny Tschüter
2010-05-05 14:31 ` Steven Rostedt
2010-05-05 14:33 ` Arjan van de Ven
2010-05-12 8:57 ` Robert Schöne
2010-06-11 10:26 ` Ronny Tschüter
2010-06-29 14:49 ` Ronny Tschüter
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=4BDECD66.2010906@tu-dresden.de \
--to=ronny.tschueter@tu-dresden.de \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.