All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Arjan van de Ven <arjan@infradead.org>
Cc: devzero@web.de, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/2] show being-loaded/being-unloaded indicator for modules
Date: Tue, 8 Jan 2008 08:05:00 +1100	[thread overview]
Message-ID: <200801080805.00639.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080107062116.0aa37438@laptopd505.fenrus.org>

On Tuesday 08 January 2008 01:21:16 Arjan van de Ven wrote:
> On Mon, 07 Jan 2008 11:09:23 +0100
>
> devzero@web.de wrote:
> > this looks very useful!
> >
> > >Unfortunatly, it's not always easy to see directly
> > >which module is being loaded/unloaded from the oops itself.
> >
> > no wonder, as most modules seem to be very quiet on on load/unload.
> >
> >
> >
> >
> > but i wonder if some mandatory "print a message on init/exit"
> > wouldn`t give a benefit to admins or end-users, too. sure this would
> > additionally clutter up syslog, but it would add transparency.
>
> Regardless of the usefulness, really, if this would be mandatory for all
> modules, it should be done in the module loader itself....
> But I'm not entirely convinced how useful that is to do always, although I
> can see the point of having it as debug option, similar to the initcall
> debug stuff...

We could overload initcall_debug for this if we wanted to be consistant.  But 
I'm just not sure it'd be clear when to turn it on...

Rusty.

  reply	other threads:[~2008-01-07 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 10:09 [patch 1/2] show being-loaded/being-unloaded indicator for modules devzero
2008-01-07 14:21 ` Arjan van de Ven
2008-01-07 21:05   ` Rusty Russell [this message]
2008-01-07 21:43 ` Valdis.Kletnieks

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=200801080805.00639.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=arjan@infradead.org \
    --cc=devzero@web.de \
    --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.