[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJN39oh4NQGBPTXR37mMr2hbDosTQbzM2qN5Okjjt9TLMiEocw@mail.gmail.com>
Date: Tue, 14 Mar 2017 17:39:40 -0700
From: Brendan Gregg <bgregg@...flix.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
linux-kernel@...r.kernel.org, Namhyung Kim <namhyung@...nel.org>
Subject: Re: [PATCH] perf sched timehist: Add --next option
On Tue, Mar 14, 2017 at 6:12 AM, Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
> Em Tue, Mar 14, 2017 at 01:56:29AM +0000, Brendan Gregg escreveu:
>> The --next option shows the next task for each context switch, providing
>> more context for the sequence of scheduler events.
>>
>> $ perf sched timehist --next | head
>> Samples do not have callchains.
>> time cpu task name wait time sch delay run time
>> [tid/pid] (msec) (msec) (msec)
>> --------------- ------ ------------------------------ --------- --------- ---------
>
> Thanks, applied.
>
> Minor request: when printing tool output in the cset comment, please add
> two spaces before all lines, my git-am scripts get confused with that
> --- thinking its a separator.
Ok, will do in the future, thanks Arnaldo!
Brendan
Powered by blists - more mailing lists