[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1335173994.28150.106.camel@twins>
Date: Mon, 23 Apr 2012 11:39:54 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Juri Lelli <juri.lelli@...il.com>
Cc: tglx@...utronix.de, mingo@...hat.com, rostedt@...dmis.org,
cfriesen@...tel.com, oleg@...hat.com, fweisbec@...il.com,
darren@...art.com, johan.eker@...csson.com, p.faure@...tech.ch,
linux-kernel@...r.kernel.org, claudio@...dence.eu.com,
michael@...rulasolutions.com, fchecconi@...il.com,
tommaso.cucinotta@...up.it, nicola.manica@...i.unitn.it,
luca.abeni@...tn.it, dhaval.giani@...il.com, hgu1972@...il.com,
paulmck@...ux.vnet.ibm.com, raistlin@...ux.it,
insop.song@...csson.com, liming.wang@...driver.com
Subject: Re: [PATCH 03/16] sched: SCHED_DEADLINE data structures.
On Mon, 2012-04-23 at 11:36 +0200, Juri Lelli wrote:
> On 04/23/2012 11:30 AM, Peter Zijlstra wrote:
> > On Fri, 2012-04-06 at 09:14 +0200, Juri Lelli wrote:
> >> /*
> >> + * This function validates the new parameters of a -deadline task.
> >> + * We ask for the deadline not being zero, and greater or equal
> >> + * than the runtime.
> >> + */
> >> +static bool
> >> +__checkparam_dl(const struct sched_param2 *prm)
> >> +{
> >> + return prm&& (&prm->sched_deadline) != 0&&
> >> + (s64)(&prm->sched_deadline -&prm->sched_runtime)>= 0;
> >> +}
> >
> > Shouldn't this also include deadline == period for now?
>
> No notion of period in 03/16. It is inserted in 08/16 and checkparam
> changed accordingly.
Ah, ok. got confused by 2/ having sched_period.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists