hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: ftrace: fix a few formatting issues 

Make sure that literal * characters are not interpreted as emphasis
markers.

Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Jonathan Corbet 2018-03-07 10:44:08 -07:00
parent 1606f8d8e7
commit 6234c7bd8c
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/trace/events.rst
View File

@ -42,7 +42,7 @@ To disable all events, echo an empty line to the set_event file::
# echo > /sys/kernel/debug/tracing/set_event
To enable all events, echo '*:*' or '*:' to the set_event file::
To enable all events, echo ``*:*`` or ``*:`` to the set_event file::
# echo *:* > /sys/kernel/debug/tracing/set_event
@ -50,7 +50,7 @@ The events are organized into subsystems, such as ext4, irq, sched,
etc., and a full event name looks like this: <subsystem>:<event>. The
subsystem name is optional, but it is displayed in the available_events
file. All of the events in a subsystem can be specified via the syntax
"<subsystem>:*"; for example, to enable all irq events, you can use the
``<subsystem>:*``; for example, to enable all irq events, you can use the
command::
# echo 'irq:*' > /sys/kernel/debug/tracing/set_event
@ -111,8 +111,8 @@ It also displays the format string that will be used to print the
event in text mode, along with the event name and ID used for
profiling.
Every event has a set of 'common' fields associated with it; these are
the fields prefixed with 'common_'. The other fields vary between
Every event has a set of ``common`` fields associated with it; these are
the fields prefixed with ``common_``. The other fields vary between
events and correspond to the fields defined in the TRACE_EVENT
definition for that event.
@ -190,7 +190,7 @@ And for string fields they are:
==, !=, ~
The glob (~) accepts a wild card character (*,?) and character classes
The glob (~) accepts a wild card character (\*,?) and character classes
([). For example::
prev_comm ~ "*sh"

8
Documentation/trace/ftrace.rst
View File

@ -2615,13 +2615,13 @@ To see which functions are being traced, you can cat the file:
Perhaps this is not enough. The filters also allow glob(7) matching.
<match>*
``<match>*``
will match functions that begin with <match>
*<match>
``*<match>``
will match functions that end with <match>
*<match>*
``*<match>*``
will match functions that have <match> in it
<match1>*<match2>
``<match1>*<match2>``
will match functions that begin with <match1> and end with <match2>
.. note::