[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJF2gTQ5zPrEtaxowmQOj5gBMtinB1NbuVUG9qvuDfB9vNvG5A@mail.gmail.com>
Date: Thu, 7 Apr 2022 14:37:56 +0800
From: Guo Ren <guoren@...nel.org>
To: Max Filippov <jcmvbkbc@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>, Chris Zankel <chris@...kel.net>,
Linux-Arch <linux-arch@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@...ux-xtensa.org>,
Guo Ren <guoren@...ux.alibaba.com>,
Masami Hiramatsu <mhiramat@...nel.org>, stable@...r.kernel.org
Subject: Re: [PATCH V3] xtensa: patch_text: Fixup last cpu should be master
On Thu, Apr 7, 2022 at 11:35 AM Max Filippov <jcmvbkbc@...il.com> wrote:
>
> On Wed, Apr 6, 2022 at 7:28 AM <guoren@...nel.org> wrote:
> >
> > From: Guo Ren <guoren@...ux.alibaba.com>
> >
> > These patch_text implementations are using stop_machine_cpuslocked
> > infrastructure with atomic cpu_count. The original idea: When the
> > master CPU patch_text, the others should wait for it. But current
> > implementation is using the first CPU as master, which couldn't
> > guarantee the remaining CPUs are waiting. This patch changes the
> > last CPU as the master to solve the potential risk.
> >
> > Signed-off-by: Guo Ren <guoren@...ux.alibaba.com>
> > Signed-off-by: Guo Ren <guoren@...nel.org>
> > Reviewed-by: Max Filippov <jcmvbkbc@...il.com>
> > Reviewed-by: Masami Hiramatsu <mhiramat@...nel.org>
> > Cc: <stable@...r.kernel.org>
> > ---
> > arch/xtensa/kernel/jump_label.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Thanks. Applied to my xtensa tree.
I've missed the "Fixes:" for stable@...r.kernel.org, so I would update
v3 to fix it.
>
> -- Max
--
Best Regards
Guo Ren
ML: https://lore.kernel.org/linux-csky/
Powered by blists - more mailing lists