Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit fe4ec72c authored by Masanari Iida's avatar Masanari Iida Committed by Jonathan Corbet
Browse files

docs: tracing: Fix typos in histogram.rst 



This patch fixes some spelling typos in histogram.rst

Signed-off-by: default avatarMasanari Iida <standby24x7@gmail.com>
Acked-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 42f6ebd8

Documentation/trace/histogram.rst

+5 −5
Original line number Diff line number Diff line
@@ -1010,7 +1010,7 @@ Extended error information 


  For example, suppose we wanted to take a look at the relative

  weights in terms of skb length for each callpath that leads to a

  netif_receieve_skb event when downloading a decent-sized file using

  netif_receive_skb event when downloading a decent-sized file using

  wget.



  First we set up an initially paused stacktrace trigger on the
@@ -1843,7 +1843,7 @@ practice, not every handler.action combination is currently supported; 
if a given handler.action combination isn't supported, the hist

trigger will fail with -EINVAL;



The default 'handler.action' if none is explicity specified is as it

The default 'handler.action' if none is explicitly specified is as it

always has been, to simply update the set of values associated with an

entry.  Some applications, however, may want to perform additional

actions at that point, such as generate another event, or compare and
@@ -2088,7 +2088,7 @@ The following commonly-used handler.action pairs are available: 
    and the saved values corresponding to the max are displayed

    following the rest of the fields.



    If a snaphot was taken, there is also a message indicating that,

    If a snapshot was taken, there is also a message indicating that,

    along with the value and event that triggered the global maximum:



    # cat /sys/kernel/debug/tracing/events/sched/sched_switch/hist
@@ -2176,7 +2176,7 @@ The following commonly-used handler.action pairs are available: 
    hist trigger entry.



    Note that in this case the changed value is a global variable

    associated withe current trace instance.  The key of the specific

    associated with current trace instance.  The key of the specific

    trace event that caused the value to change and the global value

    itself are displayed, along with a message stating that a snapshot

    has been taken and where to find it.  The user can use the key
@@ -2203,7 +2203,7 @@ The following commonly-used handler.action pairs are available: 
    and the saved values corresponding to that value are displayed

    following the rest of the fields.



    If a snaphot was taken, there is also a message indicating that,

    If a snapshot was taken, there is also a message indicating that,

    along with the value and event that triggered the snapshot::



      # cat /sys/kernel/debug/tracing/events/tcp/tcp_probe/hist