Previously it was only allowed to use at most 10 time slices
in 'perf report --time'.

This patch removes this limitation.
For example, following command line is OK (12 time slices)

perf report --stdio --time 
1%/1,1%/2,1%/3,1%/4,1%/5,1%/6,1%/7,1%/8,1%/9,1%/10,1%/11,1%/12

Signed-off-by: Jin Yao <yao....@linux.intel.com>
---
 tools/perf/Documentation/perf-report.txt |  2 +-
 tools/perf/builtin-report.c              | 23 +++++++++++++++++------
 2 files changed, 18 insertions(+), 7 deletions(-)

diff --git a/tools/perf/Documentation/perf-report.txt 
b/tools/perf/Documentation/perf-report.txt
index 5522ce0..1940c4f 100644
--- a/tools/perf/Documentation/perf-report.txt
+++ b/tools/perf/Documentation/perf-report.txt
@@ -403,7 +403,7 @@ OPTIONS
        to end of file.
 
        Also support time percent with multiple time range. Time string is
-       'a%/n,b%/m,...' or 'a%-b%,c%-%d,...'. The maximum number of slices is 
10.
+       'a%/n,b%/m,...' or 'a%-b%,c%-%d,...'.
 
        For example:
        Select the second 10% time slice:
diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
index 77c954c..fe89021 100644
--- a/tools/perf/builtin-report.c
+++ b/tools/perf/builtin-report.c
@@ -54,8 +54,6 @@
 #include <unistd.h>
 #include <linux/mman.h>
 
-#define PTIME_RANGE_MAX        10
-
 struct report {
        struct perf_tool        tool;
        struct perf_session     *session;
@@ -76,7 +74,8 @@ struct report {
        const char              *cpu_list;
        const char              *symbol_filter_str;
        const char              *time_str;
-       struct perf_time_interval ptime_range[PTIME_RANGE_MAX];
+       struct perf_time_interval *ptime_range;
+       int                     range_size;
        int                     range_num;
        float                   min_percent;
        u64                     nr_entries;
@@ -1299,24 +1298,33 @@ int cmd_report(int argc, const char **argv)
        if (symbol__init(&session->header.env) < 0)
                goto error;
 
+       report.ptime_range = perf_time__range_alloc(report.time_str,
+                                                   &report.range_size);
+       if (!report.ptime_range) {
+               ret = -ENOMEM;
+               goto error;
+       }
+
        if (perf_time__parse_str(report.ptime_range, report.time_str) != 0) {
                if (session->evlist->first_sample_time == 0 &&
                    session->evlist->last_sample_time == 0) {
                        pr_err("HINT: no first/last sample time found in perf 
data.\n"
                               "Please use latest perf binary to execute 'perf 
record'\n"
                               "(if '--buildid-all' is enabled, please set 
'--timestamp-boundary').\n");
-                       return -EINVAL;
+                       ret = -EINVAL;
+                       goto error;
                }
 
                report.range_num = perf_time__percent_parse_str(
-                                       report.ptime_range, PTIME_RANGE_MAX,
+                                       report.ptime_range, report.range_size,
                                        report.time_str,
                                        session->evlist->first_sample_time,
                                        session->evlist->last_sample_time);
 
                if (report.range_num < 0) {
                        pr_err("Invalid time string\n");
-                       return -EINVAL;
+                       ret = -EINVAL;
+                       goto error;
                }
        } else {
                report.range_num = 1;
@@ -1332,6 +1340,9 @@ int cmd_report(int argc, const char **argv)
                ret = 0;
 
 error:
+       if (report.ptime_range)
+               free(report.ptime_range);
+
        perf_session__delete(session);
        return ret;
 }
-- 
2.7.4

Reply via email to