linux-kernel - Re: request to add trace off and trace on with events

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: <1271711427.10448.69.camel@gandalf.stny.rr.com>
Date:	Mon, 19 Apr 2010 17:10:27 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Tim Bird <tim.bird@...sony.com>
Cc:	"Bird, Tim" <Timothy.Bird@...sony.com>,
	Tom Zanussi <tzanussi@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Chase Douglas <chase.douglas@...onical.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: request to add trace off and trace on with events

On Mon, 2010-04-19 at 13:56 -0700, Tim Bird wrote:

> I'm not sure either.  In general I dislike proliferating
> pseudo-files.  But if the tracing filter conditional is
> different from the trigger conditional, it might be needed
> to have something separate.

I was thinking of keeping the filter trigger the trigger too.

I think we talked about this in the past. Where the "trigger" file would
default be print, but could also add other triggers to it. Thus, you do
not need to print when the event is hit (with filters). I think I
originally called this a "command", but multiple commands could perform
this.

> 
> In KFT there were some non-event related trigger conditionals,
> like - start tracing after 20 milliseconds and stop after
> 80 milliseconds.
> 
> Another thing I considered for KFT triggers, but didn't get
> around to implementing, was countdown triggers - such as
> "start tracing on the 5th execution of do_fork".
> 
> With the function or function_graph tracer, since the buffer
> overflows quickly, these kinds of triggered trace starts and stops
> can help pinpoint the data you need.

Try:

echo 'try_to_wake_up:traceon:5' 'schedule:traceoff:5' > set_ftrace_filter

;-)

-- Steve


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