From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753348AbcEZIiQ (ORCPT ); Thu, 26 May 2016 04:38:16 -0400 Received: from mga02.intel.com ([134.134.136.20]:62530 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753213AbcEZIiO (ORCPT ); Thu, 26 May 2016 04:38:14 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,367,1459839600"; d="scan'208";a="974855357" Date: Thu, 26 May 2016 08:40:46 +0800 From: Yuyang Du To: Vincent Guittot Cc: Peter Zijlstra , Ingo Molnar , linux-kernel , Dietmar Eggemann Subject: Re: [PATCH v2] sched: fix first task of a task group is attached twice Message-ID: <20160526004046.GJ18670@intel.com> References: <1464095335-27730-1-git-send-email-vincent.guittot@linaro.org> <1464188472-30086-1-git-send-email-vincent.guittot@linaro.org> <20160525223824.GI18670@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 26, 2016 at 10:26:54AM +0200, Vincent Guittot wrote: > On 26 May 2016 at 00:38, Yuyang Du wrote: > > On Wed, May 25, 2016 at 05:01:11PM +0200, Vincent Guittot wrote: > >> The cfs_rq->avg.last_update_time is initialize to 0 with the main effect > >> that the 1st sched_entity that will be attached, will keep its > >> last_update_time set to 0 and will attached once again during the > >> enqueue. > >> Initialize cfs_rq->avg.last_update_time to 1 instead. > > > > Actually, the first time (attach_task_cfs_rq()) is called even way > > before init_entity_runnable_average(), no? > > maybe there is an issue during the fork of a task too > This patch is about the init of the sched_avg of a task group. The > problem happens when the 1st task is moved the group but it's not > about the fork of a task Right, but the root cause is not addressed, which is when forked, the task should not be touched on sched avgs before init_entity_runnable_average() in wake_up_new_task(). You think?