24 messages in org.freebsd.freebsd-archkldunload DIAGNOSTIC idea...| From | Sent On | Attachments |
|---|---|---|
| Poul-Henning Kamp | Jul 20, 2004 11:21 am | |
| Brian Fundakowski Feldman | Jul 20, 2004 11:32 am | |
| Poul-Henning Kamp | Jul 20, 2004 11:40 am | |
| Brian Fundakowski Feldman | Jul 20, 2004 11:53 am | |
| Willem Jan Withagen | Jul 20, 2004 12:08 pm | |
| Scott Long | Jul 20, 2004 12:09 pm | |
| Scott Long | Jul 20, 2004 12:11 pm | |
| David Schultz | Jul 20, 2004 1:40 pm | |
| Andrea Campi | Jul 20, 2004 11:18 pm | |
| Poul-Henning Kamp | Jul 20, 2004 11:47 pm | |
| Julian Elischer | Jul 21, 2004 12:09 am | |
| Doug Rabson | Jul 21, 2004 2:10 am | |
| Poul-Henning Kamp | Jul 21, 2004 2:22 am | |
| Doug Rabson | Jul 21, 2004 3:37 am | |
| Poul-Henning Kamp | Jul 21, 2004 4:02 am | |
| Doug Rabson | Jul 21, 2004 4:20 am | |
| Poul-Henning Kamp | Jul 21, 2004 4:37 am | |
| Doug Rabson | Jul 21, 2004 5:20 am | |
| Poul-Henning Kamp | Jul 21, 2004 5:30 am | |
| M. Warner Losh | Jul 21, 2004 7:51 am | |
| Brian Fundakowski Feldman | Jul 21, 2004 8:08 am | |
| Poul-Henning Kamp | Jul 21, 2004 9:38 am | |
| M. Warner Losh | Jul 21, 2004 10:14 am | |
| Poul-Henning Kamp | Jul 21, 2004 10:16 am |
| Subject: | kldunload DIAGNOSTIC idea... | |
|---|---|---|
| From: | Doug Rabson (df...@nlsystems.com) | |
| Date: | Jul 21, 2004 3:37:36 am | |
| List: | org.freebsd.freebsd-arch | |
On Wed, 2004-07-21 at 10:21, Poul-Henning Kamp wrote:
In message <2004...@nlsystems.com>, Doug Rabson writes:
The original intention was that drivers use the device_busy()/device_unbusy() counter to handle these things. In some cases, just calling device_busy() from fooopen() and device_unbusy() from fooclose() is sufficient.
That is not enough. All methods in cdevsw, and things not in cdevsw (clone handlers, call backs, etc etc) needs to refcount.
I have a lot of this working in a tree here, and will commit it once I have gone over it a few more times.
Methods in cdevsw which can't be called unless the device is opened can rely on a single counter managed by open/close in most cases. Other callbacks may or may not need extra handling depending on whether or not the callback can persist past close.
Will you use the existing device_busy() counter or will each driver use its own counter?