From: patchwork-bot+linux-riscv@kernel.org
To: Nick Hu <nick.hu@sifive.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, tglx@linutronix.de,
peterz@infradead.org, anup@brainfault.org,
samuel.holland@sifive.com, tj@kernel.org, alexghiti@rivosinc.com,
linux-kernel@vger.kernel.org, greentime.hu@sifive.com,
zong.li@sifive.com
Subject: Re: [PATCH v2] RISC-V: Enable the IPI before workqueue_online_cpu()
Date: Thu, 01 Aug 2024 16:40:37 +0000 [thread overview]
Message-ID: <172253043788.13740.11553891732223082482.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240717031714.1946036-1-nick.hu@sifive.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 17 Jul 2024 11:17:14 +0800 you wrote:
> Sometimes the hotplug cpu stalls at the arch_cpu_idle() for a while after
> workqueue_online_cpu(). When cpu stalls at the idle loop, the reschedule
> IPI is pending. However the enable bit is not enabled yet so the cpu stalls
> at WFI until watchdog timeout. Therefore enable the IPI before the
> workqueue_online_cpu() to fix the issue.
>
> Fixes: 63c5484e7495 ("workqueue: Add multiple affinity scopes and interface to select them")
> Signed-off-by: Nick Hu <nick.hu@sifive.com>
>
> [...]
Here is the summary with links:
- [v2] RISC-V: Enable the IPI before workqueue_online_cpu()
https://git.kernel.org/riscv/c/3908ba2e0b24
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-08-01 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 3:17 [PATCH v2] RISC-V: Enable the IPI before workqueue_online_cpu() Nick Hu
2024-07-17 5:38 ` Anup Patel
2024-08-01 16:40 ` patchwork-bot+linux-riscv [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=172253043788.13740.11553891732223082482.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nick.hu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=zong.li@sifive.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