From: Ingo Molnar <mingo@kernel.org>
To: Luca Abeni <luca.abeni@unitn.it>
Cc: Juri Lelli <juri.lelli@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/deadline: remove dl_new from sched_dl_entity
Date: Sat, 5 Mar 2016 09:50:59 +0100 [thread overview]
Message-ID: <20160305085059.GA23473@gmail.com> (raw)
In-Reply-To: <1457095365-28113-1-git-send-email-luca.abeni@unitn.it>
* Luca Abeni <luca.abeni@unitn.it> wrote:
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index 57b939c..e0c4456 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -352,7 +352,14 @@ static inline void setup_new_dl_entity(struct sched_dl_entity *dl_se,
> struct dl_rq *dl_rq = dl_rq_of_se(dl_se);
> struct rq *rq = rq_of_dl_rq(dl_rq);
>
> - WARN_ON(!dl_se->dl_new || dl_se->dl_throttled);
> + WARN_ON(dl_time_before(rq_clock(rq), dl_se->deadline));
> +
> + /* We are racing with the deadline timer. So, do nothing because
> + the deadline timer handler will take care of properly recharging
> + the runtime and postponing the deadline
> + */
> + if(dl_se->dl_throttled)
> + return;
Obligatory:
Please use the customary (multi-line) comment style:
/*
* Comment .....
* ...... goes here.
*/
... specified in Documentation/CodingStyle.
> static void switched_to_dl(struct rq *rq, struct task_struct *p)
> {
> + if (dl_time_before(p->dl.deadline, rq_clock(rq))) {
> + setup_new_dl_entity(&p->dl, &p->dl);
> + }
Obligatory:
Please don't use curly braces around single statements.
Thanks,
Ingo
next prev parent reply other threads:[~2016-03-05 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 12:42 [PATCH] sched/deadline: remove dl_new from sched_dl_entity Luca Abeni
2016-03-05 8:50 ` Ingo Molnar [this message]
2016-03-05 20:50 ` luca abeni
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=20160305085059.GA23473@gmail.com \
--to=mingo@kernel.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).