[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1263808633.4283.152.camel@laptop>
Date: Mon, 18 Jan 2010 10:57:13 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Tejun Heo <tj@...nel.org>
Cc: torvalds@...ux-foundation.org, mingo@...e.hu, awalls@...ix.net,
linux-kernel@...r.kernel.org, jeff@...zik.org,
akpm@...ux-foundation.org, jens.axboe@...cle.com,
rusty@...tcorp.com.au, cl@...ux-foundation.org,
dhowells@...hat.com, arjan@...ux.intel.com, avi@...hat.com,
johannes@...solutions.net, andi@...stfloor.org,
Mike Galbraith <efault@....de>
Subject: Re: [PATCH 06/40] sched: add wakeup/sleep sched_notifiers and
allow NULL notifier ops
On Mon, 2010-01-18 at 09:57 +0900, Tejun Heo wrote:
> @@ -2439,6 +2440,8 @@ static inline void ttwu_post_activation(struct task_struct *p, struct rq *rq,
> rq->idle_stamp = 0;
> }
> #endif
> + if (success)
> + fire_sched_notifiers(p, wakeup);
> }
>
> /**
So why can't you call fire_sched_notifier(p, wakeup) right next to
activate_task(rq, p, 1) in ttwu_activate() ?
> @@ -5481,10 +5484,12 @@ need_resched_nonpreemptible:
> clear_tsk_need_resched(prev);
>
> if (prev->state && !(preempt_count() & PREEMPT_ACTIVE)) {
> - if (unlikely(signal_pending_state(prev->state, prev)))
> + if (unlikely(signal_pending_state(prev->state, prev))) {
> prev->state = TASK_RUNNING;
> - else
> + } else {
> + fire_sched_notifiers(prev, sleep);
> deactivate_task(rq, prev, 1);
> + }
> switch_count = &prev->nvcsw;
> }
>
--
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