linux-kernel - Re: [PATCH] tracing/filters: allow event filters to be set only when not tracing

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: <alpine.DEB.2.00.0904031241280.21481@gandalf.stny.rr.com>
Date:	Fri, 3 Apr 2009 12:43:15 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Tom Zanussi <tzanussi@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>, fweisbec@...il.com
Subject: Re: [PATCH] tracing/filters: allow event filters to be set only when
 not tracing


On Fri, 3 Apr 2009, Ingo Molnar wrote:
> > 
> > My kneejerk reaction is "why would anyone want to trace the idle 
> > loop?"
> 
> heh :-)
> 
> Idle enter/exit events are useful to tune power use for example. The 
> more events we have there, the more we prevent the CPU from slowly 
> going into deep sleep mode.

I can say I use it a lot. I'm still needing a way to set the function pid 
recorder to 0 since the conversion to the pid structure. There are times 
I only want to trace the interrupts that happen in the idle loop.

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