linux-kernel - Re: [PATCH] tracing/ftrace: stop {irqs,preempt}soff tracers when tracing is stopped

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.0903181000370.10610@gandalf.stny.rr.com>
Date:	Wed, 18 Mar 2009 10:00:52 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing/ftrace: stop {irqs,preempt}soff tracers when
 tracing is stopped




On Wed, 18 Mar 2009, Ingo Molnar wrote:
> > 
> > I tested the call to the start/stop callbacks from tracing_start() 
> > and tracing_stop() but it's not possible for now: the sched_switch 
> > tracer register/unregister his tracepoints from these callbacks, 
> > thus allocate some memory. But tracing_start/stop can be called 
> > from atomic.
> > 
> > I discussed about that with Steven on irc, and for now the v1 
> > should be applied as a temporary solution. We plan to simplify 
> > later the start/stop callbacks from each tracers that need it.
> 
> ok. Steve, could you please pick v1 up?

Will do.

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