Lines Matching refs:feature

9 The goal of this feature is to provide a kernel debug logging API 
17 The debug feature may also very useful for kernel and driver development.
22 feature with the function call debug_register(). This function initializes a 
58 /sys/kernel/debug therefore the debug feature can be accessed under
83 It is also possible to deactivate the debug feature globally for every
86 There are currently 2 possible triggers, which stop the debug feature
88 set to 1 the debug feature is running. If "debug_active" is set to 0 the
89 debug feature is turned off.
90 The second trigger which stops the debug feature is a kernel oops.
91 That prevents the debug feature from overwriting debug information that
92 happened before the oops. After an oops you can reactivate the debug feature
95 If you want to disallow the deactivation of the debug feature, you can use
97 feature cannot be stopped. If the debug feature is already stopped, it
177 Description:   stops the debug feature if stopping is allowed. Currently
456 Define 4 pages for the debug areas of debug feature "dasd":
459 Stooping the debug feature
465 2. Stop debug feature
484 Normally modules which use the debug feature will also have
511 available as long as the debug feature exists. The reason behind this is that
513 the debug feature. If you log a string that is freed afterwards, you will get
514 an OOPS when inspecting the debug feature, because then the debug feature will
578 It is not used by the debug feature itself.