From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755535AbcKOHeU (ORCPT ); Tue, 15 Nov 2016 02:34:20 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:34995 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752217AbcKOHeS (ORCPT ); Tue, 15 Nov 2016 02:34:18 -0500 Date: Tue, 15 Nov 2016 08:34:13 +0100 From: Ingo Molnar To: Namhyung Kim Cc: Arnaldo Carvalho de Melo , David Ahern , Peter Zijlstra , Jiri Olsa , LKML , Stephane Eranian , Andi Kleen Subject: Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v1) Message-ID: <20161115073413.GA7016@gmail.com> References: <20161114161243.15403-1-namhyung@kernel.org> <20161115064214.GB27089@gmail.com> <20161115065509.GB16821@danjae.aot.lge.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161115065509.GB16821@danjae.aot.lge.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Namhyung Kim wrote: > > > By default it shows the individual schedule events, including the time between > > > sched-in events for the task, the task scheduling delay (time between wakeup > > > and actually running) and run time for the task: > > > > > > time cpu task name[tid/pid] b/n time sch delay run time > > > ------------- ---- -------------------- --------- --------- --------- > > > 79371.874569 [11] gcc[31949] 0.014 0.000 1.148 > > > 79371.874591 [10] gcc[31951] 0.000 0.000 0.024 > > > 79371.874603 [10] migration/10[59] 3.350 0.004 0.011 > > > 79371.874604 [11] 1.148 0.000 0.035 > > > 79371.874723 [05] 0.016 0.000 1.383 > > > 79371.874746 [05] gcc[31949] 0.153 0.078 0.022 > > > ... > > > > What does the 'b/n' abbreviation stand for? 'Between'? Could we call the column > > 'sch wait' instead, or so? > > Looks better, or what about 'wait time'? Works for me! > I'd go with the first option - simply adding arrows. It's good enough to > identify each function IMHO. Ok! Thanks, Ingo