From: Rusty Russell <rusty@rustcorp.com.au>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: timing of module MODULE_STATE_COMING notifier
Date: Wed, 02 Sep 2015 15:32:58 +0930 [thread overview]
Message-ID: <87lhcp1hpp.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20150831204017.GI29756@redhat.com>
"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.
prev parent reply other threads:[~2015-09-02 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 0:06 timing of module MODULE_STATE_COMING notifier Frank Ch. Eigler
2015-08-31 1:36 ` Rusty Russell
2015-08-31 12:53 ` Frank Ch. Eigler
2015-08-31 20:40 ` Frank Ch. Eigler
2015-09-02 6:02 ` Rusty Russell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhcp1hpp.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.