On 18 October 2011 10:07, Jukka Ruohonen <jruoho...@iki.fi> wrote: > On Tue, Oct 18, 2011 at 08:43:46AM +0200, Marc Balmer wrote: >> Am 18.10.11 06:27, schrieb Jukka Ruohonen: >> > On Tue, Oct 18, 2011 at 12:07:45AM +0000, Jared D. McNeill wrote: >> >> Module Name: src >> >> Committed By: jmcneill >> >> Date: Tue Oct 18 00:07:45 UTC 2011 >> >> >> >> Modified Files: >> >> src/sys/arch/x86/x86: vmt.c >> >> >> >> Log Message: >> >> don't allow module autounload >> > >> > I wonder should autounloading be prohibited for all driver-class modules? >> >> Why? When the parent goes away, why not autounload a driver? > > I am not sure. But have we thought about all the consequences and corner- > cases? Unloading happens while modifying hardware state? Deferred calls > in the drivers? And so on? To me it also seems that if I manually load > a driver-module, I expect it to stay loaded until I unload it.
Presumably whether to permit autounload should be an option that can be specified at manual module load time, then the default is less important.
