From: Peter Zijlstra <peterz@infradead.org>
To: Xunlei Pang <xlpang@redhat.com>
Cc: linux-kernel@vger.kernel.org, Juri Lelli <juri.lelli@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] sched/deadline: No need to check NULL later_mask
Date: Fri, 1 Apr 2016 13:29:19 +0200 [thread overview]
Message-ID: <20160401112919.GP3430@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1459509198-26543-1-git-send-email-xlpang@redhat.com>
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?
next prev parent reply other threads:[~2016-04-01 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 11:13 [PATCH] sched/deadline: No need to check NULL later_mask Xunlei Pang
2016-04-01 11:29 ` Peter Zijlstra [this message]
2016-04-01 12:16 ` Xunlei Pang
2016-04-01 16:21 ` Peter Zijlstra
2016-04-02 10:14 ` Xunlei Pang
2016-04-06 9:30 ` Peter Zijlstra
2016-04-06 13:08 ` Xunlei Pang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160401112919.GP3430@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=xlpang@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.