RFC: modules and 2.5

From: Jeff Garzik (jgarzik@mandrakesoft.com)
Date: Tue Jul 03 2001 - 00:13:45 EST

A couple things that would be nice for 2.5 is
- let MOD_INC_USE_COUNT work even when module is built into kernel, and
- let THIS_MODULE exist and be valid even when module is built into

This introduces bloat into the static kernel for modules which do not
take advantage of this, so perhaps we can make this new behavior
conditional on CONFIG_xxx option. Individual drivers which make use of
the behavior can do something like

        dep_tristate 'my driver' CONFIG_MYDRIVER $CONFIG_PCI
        if [ "$CONFIG_MYDRIVER" != "n" -a \
             "$CONFIG_STATIC_MODULES" != "y" ]; then
           define_bool CONFIG_STATIC_MODULES y

The reasoning behind this is that module use counts are useful sometimes
even when the driver is built into the kernel. Other facilities like
inter_xxx are [obviously] useful when built into the kernel, so it makes
sense to at least optionally support homogenous module treatment across
static or modular builds.

Jeff Garzik      | "I respect faith, but doubt is
Building 1024    |  what gives you an education."
MandrakeSoft     |           -- Wilson Mizner
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Sat Jul 07 2001 - 21:00:11 EST