Commit 4027d080 authored by xiaofeng.yan's avatar xiaofeng.yan Committed by Ingo Molnar

sched/rt: Fix 'struct sched_dl_entity' and dl_task_time() comments, to match...

sched/rt: Fix 'struct sched_dl_entity' and dl_task_time() comments, to match the current upstream code
Signed-off-by: default avatarxiaofeng.yan <xiaofeng.yan@huawei.com>
Signed-off-by: default avatarPeter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1399605687-18094-1-git-send-email-xiaofeng.yan@huawei.comSigned-off-by: default avatarIngo Molnar <mingo@kernel.org>
parent 7aa2c016
...@@ -1175,8 +1175,8 @@ struct sched_dl_entity { ...@@ -1175,8 +1175,8 @@ struct sched_dl_entity {
/* /*
* Original scheduling parameters. Copied here from sched_attr * Original scheduling parameters. Copied here from sched_attr
* during sched_setscheduler2(), they will remain the same until * during sched_setattr(), they will remain the same until
* the next sched_setscheduler2(). * the next sched_setattr().
*/ */
u64 dl_runtime; /* maximum runtime for each instance */ u64 dl_runtime; /* maximum runtime for each instance */
u64 dl_deadline; /* relative deadline of each instance */ u64 dl_deadline; /* relative deadline of each instance */
......
...@@ -520,7 +520,7 @@ static enum hrtimer_restart dl_task_timer(struct hrtimer *timer) ...@@ -520,7 +520,7 @@ static enum hrtimer_restart dl_task_timer(struct hrtimer *timer)
* We need to take care of a possible races here. In fact, the * We need to take care of a possible races here. In fact, the
* task might have changed its scheduling policy to something * task might have changed its scheduling policy to something
* different from SCHED_DEADLINE or changed its reservation * different from SCHED_DEADLINE or changed its reservation
* parameters (through sched_setscheduler()). * parameters (through sched_setattr()).
*/ */
if (!dl_task(p) || dl_se->dl_new) if (!dl_task(p) || dl_se->dl_new)
goto unlock; goto unlock;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment