iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc-dyndbg: describe "class CLASS_NAME" query support

Browse Source 
Add an explanation of the new "class CLASS_NAME" syntax and meaning,
noting that the module determines if CLASS_NAME applies to it.

Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
Link: https://lore.kernel.org/r/20220904214134.408619-19-jim.cromie@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Jim Cromie 2022-09-04 15:40:55 -06:00 committed by Greg Kroah-Hartman
parent a4a2a42741
commit 753914ed85
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Documentation/admin-guide/dynamic-debug-howto.rst
View File

@ -35,6 +35,7 @@ Dynamic debug has even more useful features:
- line number (including ranges of line numbers) - line number (including ranges of line numbers)
- module name - module name
- format string - format string
- class name (as known/declared by each module)
* Provides a debugfs control file: ``<debugfs>/dynamic_debug/control`` * Provides a debugfs control file: ``<debugfs>/dynamic_debug/control``
which can be read to display the complete list of known debug which can be read to display the complete list of known debug
@ -142,6 +143,7 @@ against. Possible keywords are:::
'file' string | 'file' string |
'module' string | 'module' string |
'format' string | 'format' string |
'class' string |
'line' line-range 'line' line-range
line-range ::= lineno | line-range ::= lineno |
@ -203,6 +205,15 @@ format
format "nfsd: SETATTR" // a neater way to match a format with whitespace format "nfsd: SETATTR" // a neater way to match a format with whitespace
format 'nfsd: SETATTR' // yet another way to match a format with whitespace format 'nfsd: SETATTR' // yet another way to match a format with whitespace
class
The given class_name is validated against each module, which may
have declared a list of known class_names. If the class_name is
found for a module, callsite & class matching and adjustment
proceeds. Examples::
class DRM_UT_KMS # a DRM.debug category
class JUNK # silent non-match
line line
The given line number or range of line numbers is compared The given line number or range of line numbers is compared
against the line number of each ``pr_debug()`` callsite. A single against the line number of each ``pr_debug()`` callsite. A single