All of lore.kernel.org
 help / color / mirror / Atom feed
From: romain.perier@gmail.com (Romain Perier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: rockchip: Add cpu hotplug support for RK3XXX SoCs
Date: Fri, 18 Jul 2014 08:16:02 +0200	[thread overview]
Message-ID: <53C8BBA2.7060308@gmail.com> (raw)
In-Reply-To: <20140717221436.GZ21766@n2100.arm.linux.org.uk>

Hi all,

you're probably talking about __cpu_die at 
http://lxr.free-electrons.com/source/arch/arm/kernel/smp.c#L223 . The 
problem being that the thread below which executes cpu_die completes the 
completion before executing smp_ops.cpu_die. So smp_ops.cpu_kill might 
be executed before smp_ops.cpu_die (in some cases cache coherency would 
not be turned off). Note that almost all SoCs do the same thing.


On 18/07/2014 00:14, Russell King - ARM Linux wrote:
> On Thu, Jul 17, 2014 at 05:11:50PM +0000, Romain Perier wrote:
>> +static DECLARE_COMPLETION(cpu_died);
>> +
>> +static int rockchip_cpu_kill(unsigned int cpu)
>> +{
>> +	if (!wait_for_completion_timeout(&cpu_died, msecs_to_jiffies(1000))) {
>> +		pr_err("CPU%d: didn't die correctly\n", cpu);
>> +		return 0;
>> +	}
> Please explain the point of this cpu_died thing.
>
> I think you should read arch/arm/kernel/smp.c, searching for cpu_died
> in there.
>

  reply	other threads:[~2014-07-18  6:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 17:11 [PATCH] ARM: rockchip: Add cpu hotplug support for RK3XXX SoCs Romain Perier
2014-07-17 22:14 ` Russell King - ARM Linux
2014-07-18  6:16   ` Romain Perier [this message]
2014-07-18  8:29     ` Russell King - ARM Linux
2014-07-18 16:43       ` [PATCH v1] " Romain Perier

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=53C8BBA2.7060308@gmail.com \
    --to=romain.perier@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.