Re: [PATCH] sched/fair: update_curr changed sum_exec_runtime to 1 when sum_exec_runtime is 0 beacuse some kernel code use sum_exec_runtime==0 to test task just be forked.

I find this when I run a docker test script. #-script begin-- for((i=0; i<100; i++)) do     echo "=== test $i start "     rm -rf /media/ram/docker/test/*     docker run -d --name test -h test -v

Re: [PATCH] sched/fair: update_curr changed sum_exec_runtime to 1 when sum_exec_runtime is 0 beacuse some kernel code use sum_exec_runtime==0 to test task just be forked.

On Mon, Aug 26, 2019 at 07:46:50PM +0800, QiaoChong wrote: > From: Chong Qiao > > Such as: > cpu_cgroup_attach> > sched_move_task> > task_change_group_fair> >task_move_group_fair> > detach_task_cfs_rq> > vruntime_normalized> > > /* >* When !on_rq, vruntime of the

[PATCH] sched/fair: update_curr changed sum_exec_runtime to 1 when sum_exec_runtime is 0 beacuse some kernel code use sum_exec_runtime==0 to test task just be forked.

From: Chong Qiao Such as: cpu_cgroup_attach> sched_move_task> task_change_group_fair> task_move_group_fair> detach_task_cfs_rq> vruntime_normalized> /* * When !on_rq, vruntime of the task has usually NOT been normalized. * But there are some cases where