linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Tiejun Chen <tiejun.chen@windriver.com>, <tglx@linutronix.de>
Cc: <stable-rt@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: [v1][PATCH] cpu_down: move migrate_enable() back
Date: Mon, 11 Nov 2013 10:32:55 -0500	[thread overview]
Message-ID: <5280F8A7.4070608@windriver.com> (raw)
In-Reply-To: <1383789967-5885-1-git-send-email-tiejun.chen@windriver.com>

On 13-11-06 09:06 PM, Tiejun Chen wrote:
> Commit 08c1ab68, "hotplug-use-migrate-disable.patch", intends to
> use migrate_enable()/migrate_disable() to replace that combination

Since you quote a commit ID, it would be nice if you mentioned that
it is in v3.8-rt from the stable-rt repo, instead of making people
look it up.

Also, since you have cc'd stable-rt@vger, there should be some mention
of what versions it might be appropriate for (3.4?  3.10?).

> of preempt_enable() and preempt_disable(), but actually in
> !CONFIG_PREEMPT_RT_FULL case, migrate_enable()/migrate_disable()
> are still equal to preempt_enable()/preempt_disable(). So that
> followed cpu_hotplug_begin()/cpu_unplug_begin(cpu) would go schedule()
> to trigger schedule_debug() like this:
> 
> _cpu_down()
> 	|
> 	+ migrate_disable() = preempt_disable()
> 	|
> 	+ cpu_hotplug_begin() or cpu_unplug_begin()
> 		|
> 		+ schedule()
> 			|
> 			+ __schedule()
> 				|
> 				+ preempt_disable();
> 				|
> 				+ __schedule_bug() is true!
> 
> So we should move migrate_enable() as the original scheme.

It is unclear to me what context you are thinking of/referencing
as the "original scheme"...

> 
> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
> ---
>  kernel/cpu.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index 98f2ea3..da6e128 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -594,6 +594,7 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen)
>  		err = -EBUSY;
>  		goto restore_cpus;
>  	}
> +	migrate_enable();
>  

So, what happens if we now get migrated right here, before the
hotplug_begin call below?

P.
--

>  	cpu_hotplug_begin();
>  	err = cpu_unplug_begin(cpu);
> @@ -647,7 +648,6 @@ static int __ref _cpu_down(unsigned int cpu, int tasks_frozen)
>  out_release:
>  	cpu_unplug_done(cpu);
>  out_cancel:
> -	migrate_enable();
>  	cpu_hotplug_done();
>  	if (!err)
>  		cpu_notify_nofail(CPU_POST_DEAD | mod, hcpu);
> 

  reply	other threads:[~2013-11-11 15:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  2:06 [v1][PATCH] cpu_down: move migrate_enable() back Tiejun Chen
2013-11-11 15:32 ` Paul Gortmaker [this message]
2013-11-15  9:31   ` Sebastian Andrzej Siewior
2013-11-16 13:05 ` Sebastian Andrzej Siewior

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=5280F8A7.4070608@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=stable-rt@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tiejun.chen@windriver.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).