Managing and Developing Dynamically Loadable Kernel Modules

Managing Dynamically Loadable Kernel Modules

Chapter 12 521

Whole HP-UX Kernel Conﬁguration to Include a Statically Conﬁgured

Loadable Module

When conﬁguring a DLKM module into the system as statically

conﬁgured, config builds an entire kernel, that is, conﬁgures the static

kernel and all kernel modules. For a whole kernel conﬁguration, config

proceeds as follows:

1. Reads the traditional and modular master conﬁguration ﬁles for the

kernel modules

2. Reads the HP-UX system ﬁle

3. Reads the system description ﬁles for the kernel modules

4. Checks the interface functions or symbols used by the kernel modules

5. Generates several C output ﬁles (including two makeﬁles named

config.mk and config.mod) describing the system conﬁguration

6. Executes the config.mod makeﬁle to conﬁgure any dynamically

loadable modules associated with the new kernel

7. Executes the config.mk makeﬁle to conﬁgure a new kernel, to link

the kernel with the appropriate kernel libraries associated with

traditional modules, and with the statically linked modules, and to

generate the kernel symbol table

8. Places the newly generated static kernel ﬁle (vmunix_test) in the

/stand/build directory

9. Places the generated symbol table ﬁle (symtab) and generated

dynamically loadable module image ﬁles (

module_names

) under the

kernel function set directory associated with the newly generated

kernel.

10.Generates a kernel-speciﬁc KRS ﬁle that includes the module

registration information associated with the newly generated kernel.

NOTE A whole kernel conﬁguration generates several ﬁles that will make up

the kernel component set for the new kernel. After a whole kernel

conﬁguration, a kernel update (see next section) and a system shutdown

and restart are required to be able to make the newly conﬁgured kernel

the active kernel. The kernel update step, initiated with the kmupdate

command or config -u, is now a required step to be able to successfully