Managing and Developing Dynamically Loadable Kernel Modules

Managing Dynamically Loadable Kernel Modules

Chapter 12512

the next kernel or module build. If

value

is y, it will be dynamically

loadable. If

value

is n it will be statically linked.

The -b

value

option speciﬁes the phase during which the module will be

loaded, assuming it has been conﬁgured and registered with the kernel.

The

value

argument can be one of the following:

1 (BOOT1) Speciﬁes that the module should be loaded

during phase 1 of the kernel boot sequence.

2 (BOOT2) Speciﬁes that the module should be loaded

during phase 2 of the kernel boot sequence.

i (INIT) Speciﬁes that the module should be loaded

during the init process.

a (AUTO) Speciﬁes that the module is not to be loaded

upon system reboot, but should remain ready to load on

demand, or by the DKLM auto loading mechanism.

The planned loading phase will become the conﬁgured loading phase

once a module is conﬁgured and registered with the kernel.

NOTE If the module does not support dynamic linkage, an attempt to set the

planned linkage as dynamic (kmsystem -l y), and/or an attempt to set

the planned loading phase (kmsystem -b

phase

) will result in an error.

To prepare a loadable module to be dynamically loaded into the kernel,

execute this command:

/usr/sbin/kmsystem -c y -l y -b

phase module_name

NOTE A module’s system description ﬁle, as well as the HP-UX system ﬁle,

must only be modiﬁed using the kmsystem or kmtune commands. It is

important to follow this practice because the format of planned

attributes and their location in the system will change in future releases

and if you manually modify the system ﬁles as they are currently

designed, your modiﬁcations will not be forward compatible.

Querying and Tuning System Parameters for DLKM Modules

Use the kmtune command to query, set, or reset system (tunable)