public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Yong-Xuan Wang <yongxuan.wang@sifive.com>,
	Anup Patel <anup@brainfault.org>, Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	greentime.hu@sifive.com, vincent.chen@sifive.com,
	zong.li@sifive.com, Yong-Xuan Wang <yongxuan.wang@sifive.com>
Subject: Re: [PATCH] irqchip/riscv-imsic: sync-up state before CPU offline
Date: Tue, 05 May 2026 21:44:59 +0200	[thread overview]
Message-ID: <87bjety72c.ffs@tglx> (raw)
In-Reply-To: <20260503-imsic-v1-1-aa8330bd1c34@sifive.com>

On Sun, May 03 2026 at 23:05, Yong-Xuan Wang 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_pre" pointer of
> these interrupts can only be cleared after the old CPU backs to online.
> Therefore the affinity of an interrupt that are orignally target an
> offlined CPU can't be changed.

https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#changelog

> This patch force to clear the "move_pre" pointers before the CPU goes
> offline.

# git grep 'This patch' Documentation/process/

Thanks,

        tglx

  reply	other threads:[~2026-05-05 19:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04  6:05 [PATCH] irqchip/riscv-imsic: sync-up state before CPU offline Yong-Xuan Wang
2026-05-05 19:44 ` Thomas Gleixner [this message]
2026-05-05 19:46   ` Thomas Gleixner

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=87bjety72c.ffs@tglx \
    --to=tglx@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=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