linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: josephl@nvidia.com (Joseph Lo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: tegra: add CPU hotplug support
Date: Wed, 15 Aug 2012 17:14:51 +0800	[thread overview]
Message-ID: <1345022091.25319.158.camel@jlo-ubuntu-64.nvidia.com> (raw)
In-Reply-To: <502A99CD.3060400@wwwdotorg.org>

Hi Stephen,

Thanks for your review.

On Wed, 2012-08-15 at 02:32 +0800, Stephen Warren wrote:
> On 08/14/2012 02:07 AM, Joseph Lo wrote:
> > This patch set adds CPU hotplug support for Tegra20 and Tegra30 SoCs.
> > 
> > The first 3 patches make the CPU clock and reset control be a module and
> > the abstraction APIs for TegraXX SoCs. And clean up some codes for later
> > usage. Then add CPU hotplug support for Tegra20 and Tegra30.
> > 
> > Verified on Seaboard(Tegra20) and Cardhu(Tegra30)
> 
> There are two problems with this series:
> 
> 1) It doesn't compile if CONFIG_HOTPLUG_CPU isn't enabled. Please also
> make sure that Tegra20-only and Tegra30-only kernels compile (I didn't
> check this, so it may well already be the case).

I will add one more patch to enable HOTPLUG_CPU in this patch set.

I also verified the compiling and functionality of the Tegra20-only and
Tegra30-only kernels. It's OK.
> 
> 2) It prevents the "reboot" from working; the kernel hangs as it
> attempts to do the reboot. I've confirmed this isn't the case without
> this patch series, even if CONFIG_HOTPLUG_CPU is enabled.

I just found during the reboot process. It will call to
"platfor_cpu_kill" before assert the reset. But in this patch, the
"platform_cpu_kill" can't just be called along. It must be called after
"platform_cpu_die". So I will move all the SoC specific CPU shutdown
code into "platform_cpu_die" not separate into two functions. It will
prevent the system hang when calling to "smp_send_stop". (the flow for
your reference,
sys_reboot->machine_restart->smp_send_stop->smp_kill_cpus->platform_cpu_kill.)
> 
> I assume we'll want to enable CONFIG_HOTPLUG_CPU in tegra_defconfig once
> this is checked in?

Thanks,
Joseph

--
nvpublic

      reply	other threads:[~2012-08-15  9:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14  8:07 [PATCH 0/5] ARM: tegra: add CPU hotplug support Joseph Lo
2012-08-14  8:07 ` [PATCH 1/5] ARM: tegra: introduce tegra_cpu_car_ops structures Joseph Lo
2012-08-14  8:07 ` [PATCH 2/5] ARM: tegra: replace the CPU CAR access code by tegra_cpu_car_ops Joseph Lo
2012-08-14  8:07 ` [PATCH 3/5] ARM: tegra: clean up the common assembly macros into sleep.h Joseph Lo
2012-08-14  8:07 ` [PATCH 4/5] ARM: tegra30: add CPU hotplug support Joseph Lo
2012-08-14  8:07 ` [PATCH 5/5] ARM: tegra20: " Joseph Lo
2012-08-14 18:32 ` [PATCH 0/5] ARM: tegra: " Stephen Warren
2012-08-15  9:14   ` Joseph Lo [this message]

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=1345022091.25319.158.camel@jlo-ubuntu-64.nvidia.com \
    --to=josephl@nvidia.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 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).