From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934542AbcLLR1h (ORCPT ); Mon, 12 Dec 2016 12:27:37 -0500 Received: from mail-pg0-f65.google.com ([74.125.83.65]:34339 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753761AbcLLR1g (ORCPT ); Mon, 12 Dec 2016 12:27:36 -0500 Date: Tue, 13 Dec 2016 02:26:20 +0900 From: Namhyung Kim To: David Ahern Cc: Arnaldo Carvalho de Melo , Ingo Molnar , Peter Zijlstra , Jiri Olsa , LKML , Andi Kleen , Minchan Kim Subject: Re: [PATCHSET 0/6] perf sched timehist: Introduce --idle-hist option (v2) Message-ID: <20161212172620.GD4142@danjae.aot.lge.com> References: <20161208144755.16673-1-namhyung@kernel.org> <00499939-48a7-217d-8127-47763abf5fbd@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <00499939-48a7-217d-8127-47763abf5fbd@gmail.com> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi David, On Sat, Dec 10, 2016 at 09:32:54AM -0700, David Ahern wrote: > On 12/8/16 7:47 AM, Namhyung Kim wrote: > > Hi, > > > > This patchset implements the idle hist feature which analyze reason of system > > idle. Sometimes I need to investigate what makes CPUs to go idle even though > > I have jobs to do. It may be due to I/O, waiting on lock or whatever. > > > > ... > > > Namhyung Kim (6): > > perf sched timehist: Split is_idle_sample() > > perf sched timehist: Introduce struct idle_time_data > > perf sched timehist: Save callchain when entering idle > > perf sched timehist: Skip non-idle events when necessary > > perf sched timehist: Add -I/--idle-hist option > > perf sched timehist: Show callchains for idle stat > > > > tools/perf/Documentation/perf-sched.txt | 4 + > > tools/perf/builtin-sched.c | 252 +++++++++++++++++++++++++++----- > > 2 files changed, 222 insertions(+), 34 deletions(-) > > > > LGTM > > Acked-by: David Ahern Thanks! > > Suggested improvement: Add the length of the time window. ie., data collected > (or analyzed over if --time is used) for N.M seconds. Puts the amount of idle > time into perspective. Do you mean adding an elapsed time so that it can see the cpu utilization (or something similar)? Then we need to expose the elapsed time during record or maybe just use time difference between first and last sample? Thanks, Namhyung