HP UX 11i v1 I/O Cards manual Debug Level Field Format

ZCOM Tables and Data Structures

ZCOM Kernel Data

DEBUG - Debug level

This field is used by the LDM to produce driver debug logs for its processing. Some LDM modules have embedded debug codes, which check this field to log debug messages. The format of this field is shown in Table 3-49. The values of the bits in the field are described in Table 3-50.

Table 3-49		Debug Level Field Format
15-8		7	6			5-4	3-0
FID		MLOG		CLOG		UNUSED	LEVEL
Table 3-50		Debug Level Field Values
Bit	Name			Value (hex)	Meaning
LEVEL	ZCOM_DEBUG_LEVEL			0x0000000F	Debug level (0 means no debug, else debug
					enabled for all debug code this is of a level the
					same or lower than this value.)
CLOG	ZCOM_DEBUG_CLOG			0x00000010	If set, log debug message to system console.
MLOG	ZCOM_DEBUG_MLOG			0x00000020	If set, log debug messages to ZCOM message
					log.
FID	ZCOM_DEBUG_FID			0x0000FF00	Number to identify one of the LDM module to
					log debug messages (0 means all modules).
					The module ID is embedded in the source
					code. Refer to the source code to know the
					module ID of a particular file.

This field is maintained by the zmon debug and zmon nodebug commands. Because the debug logging increases the LDM overhead and is mainly for internal use, these commands are not recommended for users.

MEMPTR, MEMSIZE -Kernel memory size pointers

These are pointers to the size of kernel memory allocated by the LDM. The memory is used to hold ZCOM subsystem Memory Tables. In the current implementation, there is a fixed amount of memory defined in the kernel for use by the ZCOM subsystem, determined by the kernel zcom_mem_size tunable parameter defined at kernel build time. Hence, these fields are assigned to that part of memory.

124 Chapter 3