[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161025212441.GA24538@danjae.aot.lge.com>
Date: Wed, 26 Oct 2016 06:24:41 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Jiri Olsa <jolsa@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>
Subject: Re: [PATCH 1/3] perf sched map: Apply cpu color when there's an
activity
Hi Arnaldo,
On Tue, Oct 25, 2016 at 03:07:46PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 24, 2016 at 11:02:43AM +0900, Namhyung Kim escreveu:
> > Applying cpu color always doesn't help readability IMHO. Instead it
> > might be better to applying the color when there's an activity on those
> > CPUs.
>
> thanks, applied the three patches.
Thanks, but unfortunately the patch 3/3 has a bug. Could you please
fold the fix below into the patch?
Thanks,
Namhyung
diff --git a/tools/perf/builtin-sched.c b/tools/perf/builtin-sched.c
index f0ab715b4923..a8e58d495a66 100644
--- a/tools/perf/builtin-sched.c
+++ b/tools/perf/builtin-sched.c
@@ -1218,7 +1218,7 @@ static void output_lat_thread(struct perf_sched *sched, struct work_atoms *work_
(double)work_list->total_runtime / NSEC_PER_MSEC,
work_list->nb_atoms, (double)avg / NSEC_PER_MSEC,
(double)work_list->max_lat / NSEC_PER_MSEC,
- timestamp_in_usec(buf, sizeof(buf), work_list->max_lat));
+ timestamp_in_usec(buf, sizeof(buf), work_list->max_lat_at));
}
static int pid_cmp(struct work_atoms *l, struct work_atoms *r)
Powered by blists - more mailing lists