From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: paul.gortmaker@windriver.com, linuxppc-dev@lists.ozlabs.org,
mpe@ellerman.id.au, Xiaoming Ni <nixiaoming@huawei.com>,
stable@vger.kernel.org, oss@buserror.net,
benh@kernel.crashing.org, chenhui.zhao@freescale.com,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
paulus@samba.org, Yuantian.Tang@feescale.com
Cc: liuwenliang@huawei.com, chenjianguo3@huawei.com, wangle6@huawei.com
Subject: Re: [PATCH v2 0/2] powerpc:85xx: fix timebase sync issue when CONFIG_HOTPLUG_CPU=n
Date: Mon, 11 Oct 2021 23:06:34 +1100 [thread overview]
Message-ID: <163395399480.4094789.15095321874781475669.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210929033646.39630-1-nixiaoming@huawei.com>
On Wed, 29 Sep 2021 11:36:44 +0800, Xiaoming Ni wrote:
> When CONFIG_SMP=y, timebase synchronization is required for mpc8572 when
> the second kernel is started
> arch/powerpc/kernel/smp.c:
> int __cpu_up(unsigned int cpu, struct task_struct *tidle)
> {
> ...
> if (smp_ops->give_timebase)
> smp_ops->give_timebase();
> ...
> }
>
> [...]
Applied to powerpc/next.
[1/2] powerpc:85xx:Fix oops when mpc85xx_smp_guts_ids node cannot be found
https://git.kernel.org/powerpc/c/3c2172c1c47b4079c29f0e6637d764a99355ebcd
[2/2] powerpc:85xx: fix timebase sync issue when CONFIG_HOTPLUG_CPU=n
https://git.kernel.org/powerpc/c/c45361abb9185b1e172bd75eff51ad5f601ccae4
cheers
prev parent reply other threads:[~2021-10-11 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 2:51 [PATCH] powerpc:85xx: fix timebase sync issue when CONFIG_HOTPLUG_CPU=n Xiaoming Ni
2021-09-26 12:34 ` Xiaoming Ni
2021-09-29 3:36 ` [PATCH v2 0/2] " Xiaoming Ni
2021-09-29 3:36 ` [PATCH v2 1/2] powerpc:85xx:Fix oops when mpc85xx_smp_guts_ids node cannot be found Xiaoming Ni
2021-09-29 3:36 ` [PATCH v2 2/2] powerpc:85xx: fix timebase sync issue when CONFIG_HOTPLUG_CPU=n Xiaoming Ni
2021-10-11 12:06 ` Michael Ellerman [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=163395399480.4094789.15095321874781475669.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=Yuantian.Tang@feescale.com \
--cc=benh@kernel.crashing.org \
--cc=chenhui.zhao@freescale.com \
--cc=chenjianguo3@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liuwenliang@huawei.com \
--cc=mpe@ellerman.id.au \
--cc=nixiaoming@huawei.com \
--cc=oss@buserror.net \
--cc=paul.gortmaker@windriver.com \
--cc=paulus@samba.org \
--cc=stable@vger.kernel.org \
--cc=wangle6@huawei.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).