On 10/04/2016 05:04 AM, Namhyung Kim wrote:
On Mon, Oct 03, 2016 at 03:04:48PM -0700, Joonwoo Park wrote:
On 09/30/2016 10:15 PM, Namhyung Kim wrote:
Hi Joonwoo,
On Wed, Sep 28, 2016 at 07:25:26PM -0700, Joonwoo Park wrote:
Perf sched latency is handy to find out the maximum sched latency
On Mon, Oct 03, 2016 at 03:04:48PM -0700, Joonwoo Park wrote:
>
>
> On 09/30/2016 10:15 PM, Namhyung Kim wrote:
> > Hi Joonwoo,
> >
> > On Wed, Sep 28, 2016 at 07:25:26PM -0700, Joonwoo Park wrote:
> > > Perf sched latency is handy to find out the maximum sched latency and
> > > the time stamp o
On 09/30/2016 10:15 PM, Namhyung Kim wrote:
Hi Joonwoo,
On Wed, Sep 28, 2016 at 07:25:26PM -0700, Joonwoo Park wrote:
Perf sched latency is handy to find out the maximum sched latency and
the time stamp of the event. After running sched latency, if a found
latency looks suspicious it's quite
Hi Joonwoo,
On Wed, Sep 28, 2016 at 07:25:26PM -0700, Joonwoo Park wrote:
> Perf sched latency is handy to find out the maximum sched latency and
> the time stamp of the event. After running sched latency, if a found
> latency looks suspicious it's quite reasonable to run perf script
> subsequent
On 09/28/2016 07:25 PM, Joonwoo Park wrote:
Perf sched latency is handy to find out the maximum sched latency and
the time stamp of the event. After running sched latency, if a found
latency looks suspicious it's quite reasonable to run perf script
subsequently and search with the time stamp g
Perf sched latency is handy to find out the maximum sched latency and
the time stamp of the event. After running sched latency, if a found
latency looks suspicious it's quite reasonable to run perf script
subsequently and search with the time stamp given by perf sched latency
to continue further d
6 matches
Mail list logo