Date: Mon, 31 Aug 2015 16:40:17 -0400
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: timing of module MODULE_STATE_COMING notifier
Message-ID: <20150831204017.GI29756@redhat.com>
References: <20150831000642.GG29756@redhat.com> <87si70p7c9.fsf@rustcorp.com.au> <20150831125326.GH29756@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150831125326.GH29756@redhat.com>
User-Agent: Mutt/1.4.2.2i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 782
Lines: 25

Hi, Rusty -


I wrote:

> [...]
> > Notifiers suck for stuff like this :( Module state has many steps,
> > so my preference has been to open-code explicit hooks.  [...]
> 
> You mean something like the trace_module_load()?  (We will probably
> experiment with hooking into that tracepoint instead of the notifier.)
> [...]

It turns out this works OK, except for EXPORT_TRACEPOINT_SYMBOL_GPL.
Could we get a set of EXPORT_TRACEPOINT_SYMBOL_GPL's for the
trace/events/module.h tracepoints (at least module_load and
module_free)?


- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/