Lines Matching full:feature

2 S390 Debug Feature
11 The goal of this feature is to provide a kernel debug logging API
21 The debug feature may also very useful for kernel and driver development.
26 feature with the function call :c:func:`debug_register()`.
64 ``/sys/kernel/debug`` therefore the debug feature can be accessed under
89 It is also possible to deactivate the debug feature globally for every
93 There are currently 2 possible triggers, which stop the debug feature
95 set to 1 the debug feature is running. If ``debug_active`` is set to 0 the
96 debug feature is turned off.
98 The second trigger which stops the debug feature is a kernel oops.
99 That prevents the debug feature from overwriting debug information that
100 happened before the oops. After an oops you can reactivate the debug feature
104 If you want to disallow the deactivation of the debug feature, you can use
106 feature cannot be stopped. If the debug feature is already stopped, it
252 Define 4 pages for the debug areas of debug feature "dasd"::
256 Stopping the debug feature
264 2. Stop debug feature::
285 Normally modules which use the debug feature will also have
312   is available as long as the debug feature exists. The reason behind this is
314   in  the debug feature. If you log a string that is freed afterwards, you will
315   get an OOPS when inspecting the debug feature, because then the debug feature
381 It is not used by the debug feature itself.
392 When a view is read from the debugfs, the Debug Feature calls the