linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Unloading drivers, start-up, shut-down and a rewrite (a problem)
Date: Fri, 05 Oct 2001 07:13:15 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100226612217136@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100216891319132@msgid-missing>

Quoting David Hinds:
> Just so you know, and not saying whether it is a better or worse
> solution, the way PCMCIA drivers handle this, is that there's a
> separate interface, /proc/bus/pccard/drivers, that has "use counts"
> for PCMCIA drivers that indicate how many physical devices are
> currently associated with each driver.  These use counts are
> independent of the regular module use counts.

And FWIW, when I've thought of how to solve this "driver unload"
problem in a clean way that improves user-friendliness, that's just
what I end up wanting:  a devices-per-driver count that's distinct
from the existing uses-per-driver refcount.

It's late, so don't hold me to this, but I think adding that is probably
sufficient for user-mode policy decisions.  Hotplugging would by
default consider the device-per-driver count when seeing if it's OK
to unload a driver module.

Likely "rmmod" needs a flag that says whether the device count is
ignored, as (effectively) done today. Driver developers will want the
flexibility to say "remove this driver even though there's hardware
attached, I've got a bugfix".  USB developers work in that mode
today, it's quite handy.

- Dave



_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2001-10-05  7:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04  3:14 Unloading drivers, start-up, shut-down and a rewrite (a problem) Stamatis Mitrofanis
2001-10-04  4:29 ` Keith Owens
2001-10-05  0:03 ` Stamatis Mitrofanis
2001-10-05  5:58 ` Keith Owens
2001-10-05  6:25 ` David Hinds
2001-10-05  7:13 ` David Brownell [this message]
2001-10-05  7:21 ` David Brownell
2001-10-05  7:28 ` Keith Owens
2001-10-05  8:16 ` Oliver Neukum
2001-10-05  8:53 ` David Brownell
2001-10-05 15:26 ` David Hinds

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=marc-linux-hotplug-100226612217136@msgid-missing \
    --to=david-b@pacbell.net \
    --cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).