Managing and Developing Dynamically Loadable Kernel Modules

Managing Dynamically Loadable Kernel Modules

Chapter 12 499

DLKM Module Packaging

The DLKM infrastructure speciﬁes that:

❏ A kernel module must be packaged modularly with at least:

Planned

Phase,

Conﬁgured

Phase

The Planned Loading Phase and the Conﬁgured

Loading Phase are conﬁgurable attributes that allow

the administrator to request a speciﬁc load time for a

DLKM module, as long as the loading phase is

supported by the module. The Planned Loading Phase

can be set using kmsystem(1M) for any module

installed on the system, and will be used for the next

module conﬁguration and registration [See

config(1M) and kmupdate(1M).]

Once a module is conﬁgured and registered with the

kernel, the Planned Loading Phase is used to

initialize the Conﬁgured Loading Phase for that

module. The Conﬁgured Loading Phase can be

changed with kmadmin(1M) for any DLKM module

registered with the kernel.

The possible values are BOOT1, BOOT2, INIT, and

AUTO. BOOT1 will attempt to load the module at every

system reboot during phase 1 of the boot sequence.

BOOT2 will attempt to load the module at every

system reboot during phase 2 of the boot sequence.

INIT will attempt to load the module at every system

reboot during the init process, via rc scripts. AUTO will

leave the module ready to load on demand or via the

DLKM auto-load mechanism (load on access).

BOOT1 is valid if the Supported Loading Phases

include BOOT1. BOOT2 is valid if the Supported

Loading Phases include BOOT2. INIT and AUTO are

valid if the Supported Loading Phases include RUN.

Table 12-1 Important Terms and Concepts

Term /

Concept

Deﬁnition