linux-kernel - Re: systemtap broken by removal of register_timer

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: <20130410112456.GA29886@gmail.com>
Date:	Wed, 10 Apr 2013 13:24:56 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	"Frank Ch. Eigler" <fche@...hat.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Mel Gorman <mgorman@...e.de>,
	LKML <linux-kernel@...r.kernel.org>,
	SystemTap <systemtap@...rceware.org>
Subject: Re: systemtap broken by removal of register_timer_hook


* Frank Ch. Eigler <fche@...hat.com> wrote:

> Hi -
> 
> On Wed, Apr 03, 2013 at 02:49:53PM +0200, Frederic Weisbecker wrote:
> 
> > Sounds good, would you like to propose a version? We are also
> > interested in a timer tick event tracepoint for dynticks debugging.
> 
> How about this?
> 
> Author: Frank Ch. Eigler <fche@...hat.com>
> Date:   Wed Apr 3 10:35:21 2013 -0400
> 
>     profiling: add profile_tick tracepoint
>     
>     Commit ba6fdda4 removed the timer_hook mechanism for modules to listen
>     to profiling timer ticks (without having to set up more complicated
>     perf mechanisms).  To reduce the impact on out-of-tree users, a
>     TRACE_EVENT-flavoured tracepoint is added in its place.  Tested with
>     perf and systemtap.

I'd suggest mentioning SystemTap here as the driving motivation. SystemTap 
triggered a generic kernel improvement here, no need to hide its identity!

Thanks,

	Ingo
--
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/