From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5EBDE23D7FF for ; Tue, 5 May 2026 19:46:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778010388; cv=none; b=cANruqFiu5X+mzpyBXgGmuVKQ4DQddOcfzxm/UPCWszpEyjKg2HjemzFbEmwO8E54i/dc4sTd2w7AMzNFFfuyijRLGxXKTYpXAS+PR+DX3YOVOfNplUs0gOlH2wnLpj9wY8Jzs3JmxbsC3lXIfpYubifJlZRi5ODjMSsBtwhrJ0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778010388; c=relaxed/simple; bh=jO1FzHZrNlKwD5ZAD+Uph7zwR6Brh+x7VS0clKFtqms=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=BQaac+JTzJrsJr5MgJFmf5JYwOJAXpmq2y8kFzq1mfyGygNzuGnOF/JFiIqc5tMVaq4DN9urz9Za+IWPRe73/giryLKwTFL3A2tq5vH/vwHlmCVV0whEd8hQE1wtvYEbN4GgBjsD/g0Vy//oHa43F8AsZUcMvtrKWX+Mjrf3amw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=B50iZQVc; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="B50iZQVc" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 39E6FC2BCB4; Tue, 5 May 2026 19:46:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778010388; bh=jO1FzHZrNlKwD5ZAD+Uph7zwR6Brh+x7VS0clKFtqms=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=B50iZQVcEj6X8w9MCAw8SfbHfNaYqHXkQz4XGt8tElNTDIcg6PSWvzHvSOv+19ZnO yhd4KQT/xuGRGdzHt8T54v8zL4M1CT1BfiZ8fJCbVetJlWM9LU/Miwh6RtxdvSjwH6 8OWaLAnfZ37kC758L9NPiTDzuRYShecKhEmD1h1eD9AY8Zhemd9xpB2etn0xuv8X4A Sk+TcxOJ2ZQ1me0mTlQgApeZxYmoUxKWOrX4kfCBpTpnNEy645wAnTu1V3wN3NrVrR gUZA1RWCpDWkRf8mhhGUGuhPmLi4gPm4fFldKmUKL728nqMBHGyz4tDMVU2MJxWhqV o0taOGjyXWRig== From: Thomas Gleixner To: Yong-Xuan Wang , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti 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 Subject: Re: [PATCH] irqchip/riscv-imsic: sync-up state before CPU offline In-Reply-To: <87bjety72c.ffs@tglx> References: <20260503-imsic-v1-1-aa8330bd1c34@sifive.com> <87bjety72c.ffs@tglx> Date: Tue, 05 May 2026 21:46:24 +0200 Message-ID: <878q9xy6zz.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Tue, May 05 2026 at 21:44, Thomas Gleixner wrote: > 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/ This change log also lacks a 'Fixes:' tag