From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965045AbbI2NSx (ORCPT ); Tue, 29 Sep 2015 09:18:53 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:33949 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964959AbbI2NSp (ORCPT ); Tue, 29 Sep 2015 09:18:45 -0400 Date: Tue, 29 Sep 2015 15:18:42 +0200 From: Frederic Weisbecker To: Peter Zijlstra Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, oleg@redhat.com, umgwanakikbuti@gmail.com, tglx@linutronix.de, rostedt@goodmis.org Subject: Re: [RFC][PATCH 05/11] sched: Add preempt argument to __schedule() Message-ID: <20150929131841.GC31582@lerouge> References: <20150929092825.540553633@infradead.org> <20150929093520.146533609@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150929093520.146533609@infradead.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 29, 2015 at 11:28:30AM +0200, Peter Zijlstra wrote: > There is only a single PREEMPT_ACTIVE use in the regular __schedule() > path and that is to circumvent the task->state check. Since the code > setting PREEMPT_ACTIVE is the immediate caller of __schedule() we can > replace this with a function argument. > > Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: Frederic Weisbecker