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:21:06 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100226658818502@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100216891319132@msgid-missing>
> The requirement is just that modprobe gets a new command-line paremeter
> which, when given in a call to load/unload a module, will also
> increment/decrement the module's reference count. I.e. if the parameter
> is "--ref" and the module ABC is not loaded, then the following should
> result in module ABC being in memory with a reference count of 1:
Modulo the issue about making a new "devices per driver" counter,
I'd also like to raise the issue of whether this counter shouldn't be
driven entirely by the kernel code binding drivers to devices.
That is, code the USB or PCI layers would increment/decrement
the counter when the binding was successfully achieved. No
changes to the device drivers needed, but having the kernel
maintain those counters would be safer than doing it in user mode.
- 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
next prev parent reply other threads:[~2001-10-05 7:21 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
2001-10-05 7:21 ` David Brownell [this message]
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-100226658818502@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).