From: Scott Wood <scottwood@freescale.com>
To: York Sun <yorksun@freescale.com>
Cc: PPC list <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/85xx: Add back condition for smp
Date: Tue, 17 Apr 2012 17:17:50 -0500 [thread overview]
Message-ID: <4F8DEC0E.4060700@freescale.com> (raw)
In-Reply-To: <1334698746-11529-1-git-send-email-yorksun@freescale.com>
On 04/17/2012 04:39 PM, York Sun wrote:
> The timebase synchronization is only necessary if we need to reset a
> separate core. Currently only KEXEC and CPU hotplug require resetting
> a single core. The following code should be in the condition of
> CONFIG_KEXEC or CONFIG_HOTPLUG_CPU
>
> .give_timebase = smp_generic_give_timebase,
> .take_timebase = smp_generic_take_timebase,
>
> Signed-off-by: York Sun <yorksun@freescale.com>
> Acked-by: Li Yang <leoli@freescale.com>
> ---
> arch/powerpc/platforms/85xx/smp.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/platforms/85xx/smp.c b/arch/powerpc/platforms/85xx/smp.c
> index 56942af..868c6d7 100644
> --- a/arch/powerpc/platforms/85xx/smp.c
> +++ b/arch/powerpc/platforms/85xx/smp.c
> @@ -192,8 +192,10 @@ struct smp_ops_t smp_85xx_ops = {
> .cpu_disable = generic_cpu_disable,
> .cpu_die = generic_cpu_die,
> #endif
> +#if defined(CONFIG_KEXEC) || defined(CONFIG_HOTPLUG_CPU)
> .give_timebase = smp_generic_give_timebase,
> .take_timebase = smp_generic_take_timebase,
> +#endif
> };
>
> #ifdef CONFIG_KEXEC
Note that this is only a temporary fix, that assumes the environments
where tbsync is problematic[1] (virtualization and simulation) do not
enable CONFIG_KEXEC or CONFIG_HOTPLUG_CPU. Eventually the sync should
be done via CCSR like in U-Boot, and the decision on whether to do it
should be runtime.
-Scott
[1] More so than usual.
next prev parent reply other threads:[~2012-04-17 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 21:39 [PATCH] powerpc/85xx: Add back condition for smp York Sun
2012-04-17 22:17 ` Scott Wood [this message]
2012-04-18 14:15 ` Kumar Gala
2012-04-18 16:23 ` Scott Wood
2012-04-18 13:37 ` Kumar Gala
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=4F8DEC0E.4060700@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yorksun@freescale.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 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.