lkml.org 
[lkml]   [2019]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 15/19] perf time-utils: Fix --time documentation
    Date
    Correct some punctuation and spelling and correct the format to show that
    the time resolution is nanoseconds not microseconds.

    Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
    ---
    tools/perf/Documentation/perf-diff.txt | 6 +++---
    tools/perf/Documentation/perf-report.txt | 6 +++---
    tools/perf/Documentation/perf-script.txt | 6 +++---
    3 files changed, 9 insertions(+), 9 deletions(-)

    diff --git a/tools/perf/Documentation/perf-diff.txt b/tools/perf/Documentation/perf-diff.txt
    index da7809b15cc9..5732f69580ab 100644
    --- a/tools/perf/Documentation/perf-diff.txt
    +++ b/tools/perf/Documentation/perf-diff.txt
    @@ -142,9 +142,9 @@ OPTIONS
    perf diff --time 0%-10%,30%-40%

    It also supports analyzing samples within a given time window
    - <start>,<stop>. Times have the format seconds.microseconds. If 'start'
    - is not given (i.e., time string is ',x.y') then analysis starts at
    - the beginning of the file. If stop time is not given (i.e, time
    + <start>,<stop>. Times have the format seconds.nanoseconds. If 'start'
    + is not given (i.e. time string is ',x.y') then analysis starts at
    + the beginning of the file. If stop time is not given (i.e. time
    string is 'x.y,') then analysis goes to the end of the file. Time string is
    'a1.b1,c1.d1:a2.b2,c2.d2'. Use ':' to separate timestamps for different
    perf.data files.
    diff --git a/tools/perf/Documentation/perf-report.txt b/tools/perf/Documentation/perf-report.txt
    index f441baa794ce..3de029f6881d 100644
    --- a/tools/perf/Documentation/perf-report.txt
    +++ b/tools/perf/Documentation/perf-report.txt
    @@ -412,12 +412,12 @@ OPTIONS

    --time::
    Only analyze samples within given time window: <start>,<stop>. Times
    - have the format seconds.microseconds. If start is not given (i.e., time
    + have the format seconds.nanoseconds. If start is not given (i.e. time
    string is ',x.y') then analysis starts at the beginning of the file. If
    - stop time is not given (i.e, time string is 'x.y,') then analysis goes
    + stop time is not given (i.e. time string is 'x.y,') then analysis goes
    to end of file.

    - Also support time percent with multiple time range. Time string is
    + Also support time percent with multiple time ranges. Time string is
    'a%/n,b%/m,...' or 'a%-b%,c%-%d,...'.

    For example:
    diff --git a/tools/perf/Documentation/perf-script.txt b/tools/perf/Documentation/perf-script.txt
    index c59fd52e9e91..878349cce968 100644
    --- a/tools/perf/Documentation/perf-script.txt
    +++ b/tools/perf/Documentation/perf-script.txt
    @@ -361,12 +361,12 @@ include::itrace.txt[]

    --time::
    Only analyze samples within given time window: <start>,<stop>. Times
    - have the format seconds.microseconds. If start is not given (i.e., time
    + have the format seconds.nanoseconds. If start is not given (i.e. time
    string is ',x.y') then analysis starts at the beginning of the file. If
    - stop time is not given (i.e, time string is 'x.y,') then analysis goes
    + stop time is not given (i.e. time string is 'x.y,') then analysis goes
    to end of file.

    - Also support time percent with multipe time range. Time string is
    + Also support time percent with multiple time ranges. Time string is
    'a%/n,b%/m,...' or 'a%-b%,c%-%d,...'.

    For example:
    --
    2.17.1
    \
     
     \ /
      Last update: 2019-06-04 15:03    [W:4.022 / U:0.316 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site