Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754622AbcDAL31 (ORCPT ); Fri, 1 Apr 2016 07:29:27 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:37611 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751055AbcDAL30 (ORCPT ); Fri, 1 Apr 2016 07:29:26 -0400 Date: Fri, 1 Apr 2016 13:29:19 +0200 From: Peter Zijlstra To: Xunlei Pang Cc: linux-kernel@vger.kernel.org, Juri Lelli , Ingo Molnar , Steven Rostedt Subject: Re: [PATCH] sched/deadline: No need to check NULL later_mask Message-ID: <20160401112919.GP3430@twins.programming.kicks-ass.net> References: <1459509198-26543-1-git-send-email-xlpang@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1459509198-26543-1-git-send-email-xlpang@redhat.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 306 Lines: 8 On Fri, Apr 01, 2016 at 07:13:18PM +0800, Xunlei Pang wrote: > Unlike rt tasks, we (should) have no deadline tasks in > booting phase before the mask is allocated, so we can > safely remove the check. Why? And have the kernel explode once it grows an early deadline task? Is there _any_ benefit to this?