linux-kernel - Re: Tracing of power:power

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <y0msk68llai.fsf@fche.csb>
Date:	Mon, 03 May 2010 17:36:53 -0400
From:	fche@...hat.com (Frank Ch. Eigler)
To:	=?ISO-8859-15?Q?Ronny_Tsch=FCter?= 
	<Ronny.Tschueter@...dresden.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Tracing of power:power_start events doesn't work

=?ISO-8859-15?Q?Ronny_Tsch=FCter?= <Ronny.Tschueter@...dresden.de> writes:

> 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 [...]

FWIW, on that kernel version (Fedora 13 on Athlon X2), systemtap hooks
into all those tracepoints fine, and

# stap -e 'probe kernel.trace("power_start") { log($$parms) }'

produces plenty of traffic.

- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/