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
Table | Debug Level Field Format |
|
| ||||||
|
|
|
|
|
|
|
|
|
|
| 7 | 6 |
|
|
| ||||
|
|
|
|
|
|
|
|
|
|
FID |
| MLOG |
| CLOG |
| UNUSED |
| LEVEL | |
|
|
|
|
|
|
|
|
|
|
Table | Debug Level Field Values |
|
|
|
| ||||
|
|
|
|
|
|
|
|
|
|
Bit |
| Name |
| Value |
|
|
| Meaning | |
|
| (hex) |
|
|
| ||||
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
LEVE | ZCOM_DEBUG_LEVE |
| 0x0000000 |
| Debug level (0 means no debug, else | ||||
L | L |
|
| F |
| debug enabled for all debug code this is | |||
|
|
|
|
|
| of a level the same or lower than this | |||
|
|
|
|
|
| value.) |
|
| |
|
|
|
|
|
| ||||
CLOG | ZCOM_DEBUG_CLOG |
| 0x0000001 |
| If set, log debug message to system | ||||
|
|
|
| 0 |
| console. |
|
| |
|
|
|
|
|
| ||||
MLOG | ZCOM_DEBUG_MLO |
| 0x0000002 |
| If set, log debug messages to ZCOM | ||||
| G |
|
| 0 |
| message log. |
|
| |
|
|
|
|
|
| ||||
FID | ZCOM_DEBUG_FID |
| 0x0000FF0 |
| Number to identify one of the LDM | ||||
|
|
|
| 0 |
| 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.
130 | Chapter 3 |