9eaecdf176
when an ra(4) disk comes online the hardware interrupt ends up calling disk_set_info(), which triggers a sleep lock/alloc in this path which is triggered by LOCKDEBUG. piggy-back on the existing workqueue for autoconfiguration to handle this path and run the online completion in the work queue. this is a little ugly, in that it puts two different types of work into the one queue, but seems less ugly than creating a second workqueue for what is likely another one-time event (infact, the other user may be better handled via config_defer() -- i did not look too closely.) with this, LOCKDEBUG kernels work. tested in simh. |
||
|---|---|---|
| .. | ||
| files.mscp | ||
| mscp.c | ||
| mscp.h | ||
| mscp_disk.c | ||
| mscp_subr.c | ||
| mscp_tape.c | ||
| mscpreg.h | ||
| mscpvar.h | ||