Commit 2e171403 authored by Randy Dunlap's avatar Randy Dunlap Committed by Jonathan Corbet

Documentation: trace/histogram-design: drop doubled words

Drop the doubled words "to" and "the".
Signed-off-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>
Link: https://lore.kernel.org/r/20200703212453.30553-3-rdunlap@infradead.orgSigned-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 1747db54
...@@ -780,7 +780,7 @@ same part of the hist_data->fields[] array as normal values:: ...@@ -780,7 +780,7 @@ same part of the hist_data->fields[] array as normal values::
Moving on to the sched_switch trigger hist_debug output, in addition Moving on to the sched_switch trigger hist_debug output, in addition
to the unused wakeup_lat variable, we see a new section displaying to the unused wakeup_lat variable, we see a new section displaying
variable references. Variable references are displayed in a separate variable references. Variable references are displayed in a separate
section because in addition to to being logically separate from section because in addition to being logically separate from
variables and values, they actually live in a separate hist_data variables and values, they actually live in a separate hist_data
array, var_refs[]. array, var_refs[].
...@@ -863,7 +863,7 @@ event. ...@@ -863,7 +863,7 @@ event.
The onmatch() action below basically says that whenever we have a The onmatch() action below basically says that whenever we have a
sched_switch event, if we have a matching sched_waking event, in this sched_switch event, if we have a matching sched_waking event, in this
case if we have a pid in the sched_waking histogram that matches the case if we have a pid in the sched_waking histogram that matches the
the next_pid field on this sched_switch event, we retrieve the next_pid field on this sched_switch event, we retrieve the
variables specified in the wakeup_latency() trace action, and use variables specified in the wakeup_latency() trace action, and use
them to generate a new wakeup_latency event into the trace stream. them to generate a new wakeup_latency event into the trace stream.
......
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