Messages in this thread | | | Subject | Re: [PATCH] sched: remove resetting exec_start in put_prev_task_rt() | From | Steven Rostedt <> | Date | Wed, 01 Jun 2011 10:22:57 -0400 |
| |
On Wed, 2011-06-01 at 22:03 +0800, Hillf Danton wrote: > Resetting exec_start, after updated in update_curr_rt(), could open window for > messing up the subsequent computations of delta_exec of the given task.
The domain scheduling was mostly done by Peter, but when you make a change like this, you need to explain it better than this. I really have no idea what you mean in this change log.
Please give an example of how this "open window" can mess up the subsequent computations of delta_exec. That is, have write a theoretical timeline of events that shows in detail how this can mess things up.
This makes understanding your changes much easier, otherwise you will have to wait till we have the time to look and figure things out ourselves. As we are currently working on other areas of the kernel so you will have to wait much longer than if you showed us exactly what happened.
Thanks!
-- Steve
> > Signed-off-by: Hillf Danton <dhillf@gmail.com> > --- > kernel/sched_rt.c | 1 - > 1 files changed, 0 insertions(+), 1 deletions(-) > > diff --git a/kernel/sched_rt.c b/kernel/sched_rt.c > index 88725c9..0f0cfce 100644 > --- a/kernel/sched_rt.c > +++ b/kernel/sched_rt.c > @@ -1166,7 +1166,6 @@ static struct task_struct > *pick_next_task_rt(struct rq *rq) > static void put_prev_task_rt(struct rq *rq, struct task_struct *p) > { > update_curr_rt(rq); > - p->se.exec_start = 0; > > /* > * The previous task needs to be made eligible for pushing
| |