Re: timing of module MODULE_STATE_COMING notifier

From	Rusty Russell <rusty@rustcorp.com.au>
Newsgroups	linux.kernel
Subject	Re: timing of module MODULE_STATE_COMING notifier
Date	2015-09-02 08:20 +0200
Message-ID	<q49yN-5ba-1@gated-at.bofh.it> (permalink)
References	<q3kPD-7SX-9@gated-at.bofh.it> <q3meJ-1lj-13@gated-at.bofh.it> <q3wQO-89h-15@gated-at.bofh.it> <q3EbF-1Wt-29@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

"Frank Ch. Eigler" <fche@redhat.com> writes:
> 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)?

Sure, patch welcome.

Cheers,
Rusty.
--
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/

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

timing of module MODULE_STATE_COMING notifier "Frank Ch. Eigler" <fche@redhat.com> - 2015-08-31 02:10 +0200
  Re: timing of module MODULE_STATE_COMING notifier Rusty Russell <rusty@rustcorp.com.au> - 2015-08-31 03:40 +0200
    Re: timing of module MODULE_STATE_COMING notifier "Frank Ch. Eigler" <fche@redhat.com> - 2015-08-31 15:00 +0200
      Re: timing of module MODULE_STATE_COMING notifier "Frank Ch. Eigler" <fche@redhat.com> - 2015-08-31 22:50 +0200
        Re: timing of module MODULE_STATE_COMING notifier Rusty Russell <rusty@rustcorp.com.au> - 2015-09-02 08:20 +0200

csiph-web