In order to make SVG smaller and faster to browse add possibility to
switch off power related information with -T switch.

Signed-off-by: Stanislav Fomichev <[email protected]>
---
 tools/perf/builtin-timechart.c | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/tools/perf/builtin-timechart.c b/tools/perf/builtin-timechart.c
index e6c041301aa4..c7b30a8c7f3b 100644
--- a/tools/perf/builtin-timechart.c
+++ b/tools/perf/builtin-timechart.c
@@ -41,6 +41,7 @@
 #define PWR_EVENT_EXIT -1
 
 static int proc_num = 15;
+static bool no_power;
 
 
 static unsigned int    numcpus;
@@ -967,7 +968,8 @@ static void write_svg_file(const char *filename)
        draw_cpu_usage();
        if (proc_num)
                draw_process_bars();
-       draw_c_p_states();
+       if (!no_power)
+               draw_c_p_states();
        if (proc_num)
                draw_wakeups();
 
@@ -1076,6 +1078,15 @@ static int __cmd_record(int argc, const char **argv)
 }
 
 static int
+parse_tasks(const struct option *opt __maybe_unused,
+           const char *arg __maybe_unused,
+           int unset __maybe_unused)
+{
+       no_power = 1;
+       return 0;
+}
+
+static int
 parse_process(const struct option *opt __maybe_unused, const char *arg,
              int __maybe_unused unset)
 {
@@ -1103,6 +1114,8 @@ int cmd_timechart(int argc, const char **argv,
        OPT_INTEGER('w', "width", &svg_page_width, "page width"),
        OPT_CALLBACK_NOOPT('P', "power-only", NULL, NULL,
                     "output power data only", parse_power),
+       OPT_CALLBACK_NOOPT('T', "tasks-only", NULL, NULL,
+                    "output processes data only", parse_tasks),
        OPT_CALLBACK('p', "process", NULL, "process",
                      "process selector. Pass a pid or process name.",
                       parse_process),
-- 
1.8.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to