Lines Matching +full:line +full:- +full:name
14 enabled per-callsite.
18 debug and add ``ccflags := -DDYNAMIC_DEBUG_MODULE`` into the Makefile of any
33 - source filename
34 - function name
35 - line number (including ranges of line numbers)
36 - module name
37 - format string
51 printing from source file ``svcsock.c``, line 1603 you simply do::
53 nullarbor:~ # echo 'file svcsock.c line 1603 +p' >
60 -bash: echo: write error: Invalid argument
83 nullarbor:~ # grep -i rdma <debugfs>/dynamic_debug/control | wc -l
86 nullarbor:~ # grep -i tcp <debugfs>/dynamic_debug/control | wc -l
92 the debug statement callsites with any non-default flags::
104 nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
106 nullarbor:~ # echo -n ' file svcsock.c line 1603 +p ' >
108 nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
119 ~# cat query-batch-file > <debugfs>/dynamic_debug/control
130 command ::= match-spec* flags-spec
132 The match-spec's are used to choose a subset of the known pr_debug()
133 callsites to which to apply the flags-spec. Think of them as a query
135 match-specs will select all debug statement callsites.
141 match-spec ::= 'func' string |
145 'line' line-range
147 line-range ::= lineno |
148 '-'lineno |
149 lineno'-' |
150 lineno'-'lineno
152 lineno ::= unsigned-int
156 ``line-range`` cannot contain space, e.g.
157 "1-30" is valid range but "1 - 30" is not.
163 The given string is compared against the function name
170 The given string is compared against either the src-root relative
178 file inode.c:1-100 # parse :tail as a line-range (above)
181 The given string is compared against the module name
182 of each callsite. The module name is the string as
184 suffix and with ``-`` changed to ``_``. Examples::
206 line
207 The given line number or range of line numbers is compared
208 against the line number of each ``pr_debug()`` callsite. A single
209 line number matches the callsite line number exactly. A
210 range of line numbers matches any callsite between the first
211 and last line number inclusive. An empty first number means
212 the first line in the file, an empty last line number means the
213 last line number in the file. Examples::
215 line 1603 // exactly line 1603
216 line 1600-1605 // the six lines from line 1600 to line 1605
217 line -1605 // the 1605 lines from line 1 to line 1605
218 line 1600- // all lines from line 1600 to the end of the file
224 - remove the given flags
231 f Include the function name in the printed message
232 l Include line number in the printed message
233 m Include module name in the printed message
243 Note the regexp ``^[-+=][flmpt_]+$`` matches a flags specification.
244 To clear all flags at once, use ``=_`` or ``-flmpt``.
250 To activate debug messages for core code and built-in modules during
271 If ``foo`` module is not built-in, ``foo.dyndbg`` will still be processed at
304 ``foo`` is extracted from the param-name, and applied to each query in
305 ``QUERY``, and only 1 match-spec of each type is allowed.
309 - modules do not need to define it explicitly
310 - every module gets it tacitly, whether they use pr_debug or not
311 - it doesn't appear in ``/sys/module/$module/parameters/``
314 For ``CONFIG_DYNAMIC_DEBUG`` kernels, any settings given at boot-time (or
315 enabled by ``-DDEBUG`` flag during compilation) can be disabled later via
318 echo "module module_name -p" > <debugfs>/dynamic_debug/control
325 // enable the message at line 1603 of file svcsock.c
326 nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
330 nullarbor:~ # echo -n 'file svcsock.c +p' >
334 nullarbor:~ # echo -n 'module nfsd +p' >
338 nullarbor:~ # echo -n 'func svc_process +p' >
342 nullarbor:~ # echo -n 'func svc_process -p' >
346 nullarbor:~ # echo -n 'format "nfsd: READ" +p' >
350 nullarbor:~ # echo -n '*usb* +p' > <debugfs>/dynamic_debug/control
353 nullarbor:~ # echo -n '+p' > <debugfs>/dynamic_debug/control
356 nullarbor:~ # echo -n '+mf' > <debugfs>/dynamic_debug/control
358 // boot-args example, with newlines and comments for readability
359 Kernel command line: ...