From: Will Deacon <will@kernel.org>
To: gregkh@linuxfoundation.org, guoren@kernel.org, arnd@arndb.de
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
linux-xtensa@linux-xtensa.org, Guo Ren <guoren@linux.alibaba.com>,
linux-csky@vger.kernel.org
Subject: Re: [PATCH V4 0/4] arch: patch_text: Fixup last cpu should be master
Date: Fri, 8 Apr 2022 14:58:45 +0100 [thread overview]
Message-ID: <164941462755.3967238.7784714539452982763.b4-ty@kernel.org> (raw)
In-Reply-To: <20220407073323.743224-1-guoren@kernel.org>
On Thu, 7 Apr 2022 15:33:19 +0800, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.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.
>
> [...]
Applied first patch only to arm64 (for-next/fixes), thanks!
[1/4] arm64: patch_text: Fixup last cpu should be master
https://git.kernel.org/arm64/c/31a099dbd91e
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-04-08 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:33 [PATCH V4 0/4] arch: patch_text: Fixup last cpu should be master guoren
2022-04-07 7:33 ` [PATCH V4 1/4] arm64: " guoren
2022-04-07 7:33 ` [PATCH V4 2/4] riscv: " guoren
2022-04-07 7:33 ` [PATCH V4 3/4] xtensa: " guoren
2022-04-07 7:33 ` [PATCH V4 4/4] csky: " guoren
2022-04-08 13:58 ` Will Deacon [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=164941462755.3967238.7784714539452982763.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=kernel-team@android.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-xtensa@linux-xtensa.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