From: Jin Yao <yao.jin@linux.intel.com>
To: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com,
Jin Yao <yao.jin@linux.intel.com>
Subject: [PATCH v5 0/6] perf report/script: Support percent and multiple range in --time option
Date: Sat, 21 Oct 2017 07:27:48 +0800 [thread overview]
Message-ID: <1508542074-29483-1-git-send-email-yao.jin@linux.intel.com> (raw)
v5:
---
1. There is an issue that the sample walking can only work when
'--buildid-all' is not enabled. So we need to let the walking
be able to work even if '--buildid-all' is enabled and let the
processing skips the dso hit marking for this case.
2. Check if first/last sample time is recorded in perf data file.
If it's not recorded, return error message to user.
Patched modified in v5:
perf record: Get the first sample time and last sample time
perf report: support time percent and multiple time ranges
perf script: support time percent and multiple time ranges
v4:
---
1. Use perf script time style for timestamp printing. Also add with
the printing of sample duration. For example:
perf report --header
time of first sample : 5276531.323099
time of last sample : 5276555.345625
sample duration : 24022.526 ms
2. Fix an invalid time string issue. For example,
perf script --time 10%/10x12321xsdfdasfdsafdsafdsa
Now in code, it uses strtol to replace atoi.
3. Remove perf_time__skip_sample, only uses perf_time__ranges_skip_sample
in perf report/perf script.
v3:
---
1. Move the definitions of first_sample_time/last_sample_time from
perf_session and struct record to perf_evlist and update the
related code.
v2:
---
1. This patch creates a new header feature type HEADER_SAMPLE_TIME and related
ops. Save the first sample time and the last sample time to the feature
section in perf file header.
2. Add checking for last element in time range.
For example, select the first and second 10% time slices.
perf report --time 10%/1,10%/2
Note that now it includes the last element in [10%, 20%] but it
doesn't include the last element in [0, 10%). It's to avoid
the overlap.
Following patches are changed:
perf header: Record first sample time and last sample time in perf file header
perf record: Get the first sample time and last sample time
perf util: Create function to perform multiple time range checking
v1: initial post
----------------
Current perf report/script/... have a --time option to limit the time
range of output. But it only supports the absolute time.
The patch series extend this option to let it support percent of time
and support the multiple time ranges.
For example:
1. Select the second 10% time slice
perf report --time 10%/2
2. Select from 0% to 10% time slice
perf report --time 0%-10%
It also support the multiple time ranges.
3. Select the first and second 10% time slices
perf report --time 10%/1,10%/2
4. Select from 0% to 10% and 30% to 40% slices
perf report --time 0%-10%,30%-40%
Jin Yao (6):
perf header: Record first sample time and last sample time in perf
file header
perf record: Get the first sample time and last sample time
perf util: Create function to parse time percent
perf util: Create function to perform multiple time range checking
perf report: support time percent and multiple time ranges
perf script: support time percent and multiple time ranges
tools/perf/Documentation/perf-report.txt | 16 ++
tools/perf/Documentation/perf-script.txt | 16 ++
tools/perf/Documentation/perf.data-file-format.txt | 4 +
tools/perf/builtin-record.c | 20 +-
tools/perf/builtin-report.c | 34 ++-
tools/perf/builtin-script.c | 31 ++-
tools/perf/util/evlist.h | 2 +
tools/perf/util/header.c | 60 ++++++
tools/perf/util/header.h | 1 +
tools/perf/util/time-utils.c | 233 +++++++++++++++++++--
tools/perf/util/time-utils.h | 6 +
11 files changed, 394 insertions(+), 29 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-20 15:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 23:27 Jin Yao [this message]
2017-10-20 23:27 ` [PATCH v5 1/6] perf header: Record first sample time and last sample time in perf file header Jin Yao
2017-10-20 23:27 ` [PATCH v5 2/6] perf record: Get the first sample time and last sample time Jin Yao
2017-10-23 15:04 ` Jiri Olsa
2017-10-23 17:38 ` Jin, Yao
2017-10-23 19:05 ` Arnaldo Carvalho de Melo
2017-10-24 2:03 ` Jin, Yao
2017-10-24 7:16 ` Jiri Olsa
2017-10-24 7:29 ` Jin, Yao
2017-11-03 13:00 ` Jin, Yao
2017-11-03 16:29 ` Arnaldo Carvalho de Melo
2017-11-03 21:33 ` Jin, Yao
2017-11-04 10:24 ` Jiri Olsa
2017-11-06 0:28 ` Jin, Yao
2017-10-20 23:27 ` [PATCH v5 3/6] perf util: Create function to parse time percent Jin Yao
2017-10-20 23:27 ` [PATCH v5 4/6] perf util: Create function to perform multiple time range checking Jin Yao
2017-10-20 23:27 ` [PATCH v5 5/6] perf report: support time percent and multiple time ranges Jin Yao
2017-10-20 23:27 ` [PATCH v5 6/6] perf script: " Jin Yao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1508542074-29483-1-git-send-email-yao.jin@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.