[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150407135335.GI11983@kernel.org>
Date: Tue, 7 Apr 2015 10:53:35 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Yunlong Song <yunlong.song@...wei.com>,
David Ahern <dsahern@...il.com>
Cc: a.p.zijlstra@...llo.nl, paulus@...ba.org, mingo@...hat.com,
linux-kernel@...r.kernel.org, wangnan0@...wei.com
Subject: Re: [PATCH 0/9] perf sched replay: Make some improvements and fixes
Em Tue, Apr 07, 2015 at 11:20:42AM +0800, Yunlong Song escreveu:
> On 2015/3/31 21:46, Yunlong Song wrote:
> > Hi,
> > Found some functions to improve and bugs to fix in perf sched replay.
> >
> > Yunlong Song (9):
> > perf sched replay: Use struct task_desc instead of struct task_task
> > for correct meaning
> > perf sched replay: Increase the MAX_PID value to fix assertion failure
> > problem
> > perf sched replay: Alloc the memory of pid_to_task dynamically to
> > adapt to the unexpected change of pid_max
> > perf sched replay: Realloc the memory of pid_to_task stepwise to adapt
> > to the different pid_max configurations
> > perf sched replay: Fix the segmentation fault problem caused by pr_err
> > in threads
> > perf sched replay: Handle the dead halt of sem_wait when
> > create_tasks() fails for any task
> > perf sched replay: Fix the EMFILE error caused by the limitation of
> > the maximum open files
> > perf sched replay: Support using -f to override perf.data file
> > ownership
> > perf sched replay: Use replay_repeat to calculate the runavg of cpu
> > usage instead of the default value 10
> >
> > tools/perf/builtin-sched.c | 67 +++++++++++++++++++++++++++++++++++-----------
> > 1 file changed, 52 insertions(+), 15 deletions(-)
> >
>
> Ping...
All looks reasonable, applied.
David, please holler if you still have any concerns, or either we can
work from here, i.e. improving things with follow on patches.
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists