Managing and Developing Dynamically Loadable Kernel Modules

Managing Dynamically Loadable Kernel Modules

Chapter 12500

• its own master and system ﬁles

• its own mod.o object ﬁle that implements only that module

❏ The mod.o object ﬁle must contain the module wrapper code.

NOTE See the master (4) manual page for descriptions of the traditional and

modular master ﬁles, and the system (4) manual page for a description of

the traditional and modular system ﬁles. See kmsystem(1M) and

kmtune(1M) for descriptionsof how toset and geta module’s conﬁgurable

attributes.

Kernel modules written as traditional modules are still supported in HP-

UX. Driver developers are encouraged to re-package their static modules

according to the module packaging architecture introduced with DLKM

modules, as traditional packaging support may be obsoleted in a future

release.

Types of DLKMs

The DLKM feature currently supports the following types of kernel

modules:

❏ WSIO class drivers

❏ WSIO interface drivers

❏ STREAMS drivers

❏ STREAMS modules

❏ Miscellaneous modules – for example, loadable “libraries” of kernel

functions

DLKM Advantages

DLKM modules provide many advantages relative to static modules,

including:

❏ Reducing time spent on device driver development by streamlining

the driver installation process

❏ Making it easier for administrators to install device drivers from

other vendors

❏ Improving system availability by allowing device drivers and other