From: patchwork-bot+linux-riscv@kernel.org
To: Yong-Xuan Wang <yongxuan.wang@sifive.com>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
tglx@kernel.org, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
linux-kernel@vger.kernel.org, greentime.hu@sifive.com,
vincent.chen@sifive.com, zong.li@sifive.com
Subject: Re: [PATCH v2] irqchip/riscv-imsic: sync-up state before CPU offline
Date: Fri, 22 May 2026 03:04:12 +0000 [thread overview]
Message-ID: <177941905239.602940.15678598632674221077.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260508-imsic-v2-1-e9f08dd46cf5@sifive.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@kernel.org>:
On Fri, 08 May 2026 02:31:21 -0700 you wrote:
> The "move_prev" pointer in struct imsic_vector on the new CPU is
> cleared only after the old CPU has cleared "move_next". But when
> migrating all the interrupts out from an offling CPU, since the CPU
> is already marked as "offlined", the IMSIC driver skip to sync-up the
> interrupt vector in __imsic_remote_sync(). The "move_prev" pointer of
> these interrupts can only be cleared after the old CPU backs to online.
> Therefore, the affinity of interrupts originally targeting an offlined
> CPU cannot be updated.
>
> [...]
Here is the summary with links:
- [v2] irqchip/riscv-imsic: sync-up state before CPU offline
https://git.kernel.org/riscv/c/cefafbd56140
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-22 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 9:31 Yong-Xuan Wang
2026-05-11 13:27 ` [tip: irq/urgent] irqchip/riscv-imsic: Clear interrupt move state during CPU offlining tip-bot2 for Yong-Xuan Wang
2026-05-22 3:04 ` 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=177941905239.602940.15678598632674221077.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--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=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tglx@kernel.org \
--cc=vincent.chen@sifive.com \
--cc=yongxuan.wang@sifive.com \
--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
Powered by JetHome