[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1251354307.18584.40.camel@twins>
Date: Thu, 27 Aug 2009 08:25:07 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Li Zefan <lizf@...fujitsu.com>, Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing/profile: Fix profile_disable vs module_unload
On Wed, 2009-08-26 at 15:48 -0400, Steven Rostedt wrote:
> Here's another patch that moves the module ref count administration to the
> trace events themselves. This should satisfy both you and Peter.
> +#ifdef MODULE
> +# define event_trace_up_ref() \
> + do { \
> + if (!try_module_get(THIS_MODULE)) { \
> + atomic_dec(&event_call->profile_count); \
> + return -1; \
> + } \
> + } while (0)
> +# define event_trace_down_ref() module_put(THIS_MODULE)
> +#else
> +# define event_trace_up_ref() do { } while (0)
> +# define event_trace_down_ref() do { } while (0)
> +#endif
> +
> #undef TRACE_EVENT
> #define TRACE_EVENT(call, proto, args, tstruct, assign, print) \
> \
> @@ -399,16 +413,20 @@ static int ftrace_profile_enable_##call(struct ftrace_event_call *event_call) \
> { \
> int ret = 0; \
> \
> - if (!atomic_inc_return(&event_call->profile_count)) \
> + if (!atomic_inc_return(&event_call->profile_count)) { \
> + event_trace_up_ref(); \
> ret = register_trace_##call(ftrace_profile_##call); \
> + } \
> \
> return ret; \
> } \
> \
> static void ftrace_profile_disable_##call(struct ftrace_event_call *event_call)\
> { \
> - if (atomic_add_negative(-1, &event_call->profile_count)) \
> + if (atomic_add_negative(-1, &event_call->profile_count)) { \
> unregister_trace_##call(ftrace_profile_##call); \
> + event_trace_down_ref(); \
> + } \
> }
Ha, almost, make that {un,}register_ftrace_##call() and stick the module
gunk in there, and I'm ok.
--
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/
Powered by blists - more mailing lists