Commit b8381ce7 authored by Masami Hiramatsu's avatar Masami Hiramatsu Committed by Steven Rostedt (VMware)

Documentation: tracing: Fix typos in boot-time tracing documentation

Fix typos in boottime-trace.rst according to Randy's suggestions.

Link: http://lkml.kernel.org/r/157949060335.25888.13153184562531693684.stgit@devnote2Suggested-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Acked-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarMasami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
parent a4798eb4
...@@ -13,7 +13,7 @@ Boot-time tracing allows users to trace boot-time process including ...@@ -13,7 +13,7 @@ Boot-time tracing allows users to trace boot-time process including
device initialization with full features of ftrace including per-event device initialization with full features of ftrace including per-event
filter and actions, histograms, kprobe-events and synthetic-events, filter and actions, histograms, kprobe-events and synthetic-events,
and trace instances. and trace instances.
Since kernel cmdline is not enough to control these complex features, Since kernel command line is not enough to control these complex features,
this uses bootconfig file to describe tracing feature programming. this uses bootconfig file to describe tracing feature programming.
Options in the Boot Config Options in the Boot Config
...@@ -21,7 +21,7 @@ Options in the Boot Config ...@@ -21,7 +21,7 @@ Options in the Boot Config
Here is the list of available options list for boot time tracing in Here is the list of available options list for boot time tracing in
boot config file [1]_. All options are under "ftrace." or "kernel." boot config file [1]_. All options are under "ftrace." or "kernel."
refix. See kernel parameters for the options which starts prefix. See kernel parameters for the options which starts
with "kernel." prefix [2]_. with "kernel." prefix [2]_.
.. [1] See :ref:`Documentation/admin-guide/bootconfig.rst <bootconfig>` .. [1] See :ref:`Documentation/admin-guide/bootconfig.rst <bootconfig>`
...@@ -50,7 +50,7 @@ kernel.fgraph_filters = FILTER[, FILTER2...] ...@@ -50,7 +50,7 @@ kernel.fgraph_filters = FILTER[, FILTER2...]
Add fgraph tracing function filters. Add fgraph tracing function filters.
kernel.fgraph_notraces = FILTER[, FILTER2...] kernel.fgraph_notraces = FILTER[, FILTER2...]
Add fgraph non tracing function filters. Add fgraph non-tracing function filters.
Ftrace Per-instance Options Ftrace Per-instance Options
...@@ -81,10 +81,10 @@ ftrace.[instance.INSTANCE.]tracer = TRACER ...@@ -81,10 +81,10 @@ ftrace.[instance.INSTANCE.]tracer = TRACER
Set TRACER to current tracer on boot. (e.g. function) Set TRACER to current tracer on boot. (e.g. function)
ftrace.[instance.INSTANCE.]ftrace.filters ftrace.[instance.INSTANCE.]ftrace.filters
This will take an array of tracing function filter rules This will take an array of tracing function filter rules.
ftrace.[instance.INSTANCE.]ftrace.notraces ftrace.[instance.INSTANCE.]ftrace.notraces
This will take an array of NON-tracing function filter rules This will take an array of NON-tracing function filter rules.
Ftrace Per-Event Options Ftrace Per-Event Options
...@@ -93,7 +93,7 @@ Ftrace Per-Event Options ...@@ -93,7 +93,7 @@ Ftrace Per-Event Options
These options are setting per-event options. These options are setting per-event options.
ftrace.[instance.INSTANCE.]event.GROUP.EVENT.enable ftrace.[instance.INSTANCE.]event.GROUP.EVENT.enable
Enables GROUP:EVENT tracing. Enable GROUP:EVENT tracing.
ftrace.[instance.INSTANCE.]event.GROUP.EVENT.filter = FILTER ftrace.[instance.INSTANCE.]event.GROUP.EVENT.filter = FILTER
Set FILTER rule to the GROUP:EVENT. Set FILTER rule to the GROUP:EVENT.
...@@ -145,10 +145,10 @@ below:: ...@@ -145,10 +145,10 @@ below::
} }
} }
Also, boottime tracing supports "instance" node, which allows us to run Also, boot-time tracing supports "instance" node, which allows us to run
several tracers for different purpose at once. For example, one tracer several tracers for different purpose at once. For example, one tracer
is for tracing functions start with "user\_", and others tracing "kernel\_" is for tracing functions starting with "user\_", and others tracing
functions, you can write boot config as below:: "kernel\_" functions, you can write boot config as below::
ftrace.instance { ftrace.instance {
foo { foo {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment