re: Enabling built-in modules earlier in init

[Paul Goyette <paul%whooppee.com@localhost>]

On Wed, 16 Jun 2010, matthew green wrote:

> > I would like to enable the built-in modules much earlier, at least early
> > enough to have them available during auto-configuration.  The attached
> > patch accomplishes this.  I have briefly tested the patch, and it seems
> > not to have any unwanted side-effects, but I would appreciate feedback
> > from others who may be more familiar with the init sequence.
>
> what are the effects of this on built in driver modules?  they'll have
> their init routines run before autoconfig runs, right?  that seems to
> be an issue...

Yep, that could be an issue.

> i think having a class of builtin modules that are available during
> autoconfig isn't a bad thing.  perhaps the right answer is infact to
> convert MODULE_CLASS_SECMODEL into say MODULE_CLASS_EARLY, and remove
> the special case handling for MODULE_CLASS_SECMODEL to deal with
> calling secmodel_register()/secmodel_deregister() by pushing these
> calls into the mi_modcmd() calls inside the secmodules themselves.

This makes good sense to me.  Assuming we can arrive at some sort of 
concensus on this, I'll get working on it.


-------------------------------------------------------------------------
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------