From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752432AbcHAJcE (ORCPT ); Mon, 1 Aug 2016 05:32:04 -0400 Received: from mail-wm0-f42.google.com ([74.125.82.42]:37713 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751059AbcHAJbp (ORCPT ); Mon, 1 Aug 2016 05:31:45 -0400 Message-ID: <1470043872.5903.5.camel@gmail.com> Subject: Re: [PATCH 4/4] sched,fair: Fix PELT integrity for new tasks From: Mike Galbraith To: Wanpeng Li , Peter Zijlstra Cc: Yuyang Du , Ingo Molnar , linux-kernel , Benjamin Segall , Paul Turner , Morten Rasmussen , Dietmar Eggemann , Matt Fleming , Vincent Guittot Date: Mon, 01 Aug 2016 11:31:12 +0200 In-Reply-To: References: <20160617120136.064100812@infradead.org> <20160617120454.150630859@infradead.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2016-08-01 at 15:30 +0800, Wanpeng Li wrote: > What's the meaning of "the task is hashed before we call > wake_up_new_task()"? See fork.c::copy_process() /* * Make it visible to the rest of the system, but dont wake it up yet. * Need tasklist lock for parent etc handling! */ write_lock_irq(&tasklist_lock); ....