public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/2] ftrace updates
@ 2008-08-16  1:40 Steven Rostedt
  2008-08-16  1:40 ` [PATCH 1/2] ftrace: do not init module on ftrace disabled Steven Rostedt
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Steven Rostedt @ 2008-08-16  1:40 UTC (permalink / raw)
  To: linux-kernel
  Cc: Ingo Molnar, Thomas Gleixner, Peter Zijlstra, Andrew Morton,
	Linus Torvalds, David Miller

Due to the new mcount recording method, the assumptions about the records
that hold the mcount locations have changed.  Now we need to protect
reading and writing of the records between module load and reading of the
debugfs files. There is not much contention here, but they need to be
protected none the less.

I simply use the ftrace_lock to accomplish this. The ftrace_lock should
never be held under interrupt context so disabling interrupts should
not be necessary. I've run this under lockdep and lockdep has not
complained.

-- Steve


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-08-16 13:33 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-16  1:40 [PATCH 0/2] ftrace updates Steven Rostedt
2008-08-16  1:40 ` [PATCH 1/2] ftrace: do not init module on ftrace disabled Steven Rostedt
2008-08-16  1:40 ` [PATCH 2/2] ftrace: add necessary locking for ftrace records Steven Rostedt
2008-08-16 13:32 ` [PATCH 0/2] ftrace updates Ingo Molnar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox