linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Amit K. Arora" <aarora@linux.vnet.ibm.com>
Cc: tj@kernel.org, Ingo Molnar <mingo@elte.hu>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	Gautham R Shenoy <ego@in.ibm.com>,
	Darren Hart <dvhltc@us.ibm.com>,
	Brian King <brking@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make sure timers have migrated before killing migration_thread
Date: Tue, 25 May 2010 13:31:35 +0200	[thread overview]
Message-ID: <1274787095.5882.949.camel@twins> (raw)
In-Reply-To: <20100524095951.GA17680@amitarora.in.ibm.com>

On Mon, 2010-05-24 at 15:29 +0530, Amit K. Arora wrote:
> 
> Thus, since above race can never happen, is there any other issue with
> this patch ?

It doesn't seem to apply nicely...

> 
> Signed-off-by: Amit Arora <aarora@in.ibm.com>
> Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
> ---
> diff -Nuarp linux-2.6.34.org/kernel/sched.c linux-2.6.34/kernel/sched.c
> --- linux-2.6.34.org/kernel/sched.c     2010-05-18 22:56:21.000000000 -0700
> +++ linux-2.6.34/kernel/sched.c 2010-05-18 22:58:31.000000000 -0700
> @@ -5942,14 +5942,26 @@ migration_call(struct notifier_block *nf
>                 cpu_rq(cpu)->migration_thread = NULL;
>                 break;
>  
> +       case CPU_POST_DEAD:
> +               /*
> +                * Bring the migration thread down in CPU_POST_DEAD event,
> +                * since the timers should have got migrated by now and thus
> +                * we should not see a deadlock between trying to kill the
> +                * migration thread and the sched_rt_period_timer.
> +                */
> +               cpuset_lock();
> +               rq = cpu_rq(cpu);
> +               kthread_stop(rq->migration_thread);
> +               put_task_struct(rq->migration_thread);
> +               rq->migration_thread = NULL;
> +               cpuset_unlock();
> +               break;
> +
>         case CPU_DEAD:
>         case CPU_DEAD_FROZEN:
>                 cpuset_lock(); /* around calls to cpuset_cpus_allowed_lock() */
>                 migrate_live_tasks(cpu);
>                 rq = cpu_rq(cpu);
> -               kthread_stop(rq->migration_thread);
> -               put_task_struct(rq->migration_thread);
> -               rq->migration_thread = NULL;
>                 /* Idle task back to normal (off runqueue, low prio) */
>                 raw_spin_lock_irq(&rq->lock);
>                 update_rq_clock(rq);
> 
> 

  parent reply	other threads:[~2010-05-25 11:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19  9:05 [PATCH] Make sure timers have migrated before killing migration_thread Amit K. Arora
2010-05-19  9:31 ` Peter Zijlstra
2010-05-19 12:13   ` [PATCH v2] " Amit K. Arora
2010-05-20  7:28     ` Peter Zijlstra
2010-05-23  9:07       ` Mike Galbraith
2010-05-23  9:13         ` Peter Zijlstra
2010-05-24  6:43       ` Amit K. Arora
2010-05-25 20:19       ` Thomas Gleixner
2010-05-26  6:43         ` Peter Zijlstra
2010-05-24  9:59   ` [PATCH] " Amit K. Arora
2010-05-24 13:28     ` Peter Zijlstra
2010-05-24 15:16       ` Srivatsa Vaddagiri
2010-05-24 15:55         ` Peter Zijlstra
2010-05-25 11:31     ` Peter Zijlstra [this message]
2010-05-25 12:10       ` Amit K. Arora
2010-05-25 13:23       ` [PATCH v3] " Amit K. Arora
2010-05-25 14:22         ` Peter Zijlstra
2010-05-25 16:27         ` Tejun Heo
2010-05-31  7:18         ` [tip:sched/urgent] sched: Make sure timers have migrated before killing the migration_thread tip-bot for Amit K. Arora

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=1274787095.5882.949.camel@twins \
    --to=peterz@infradead.org \
    --cc=aarora@linux.vnet.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=ego@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@kernel.org \
    --cc=vatsa@in.ibm.com \
    /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).