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 EE8AB3D6493 for ; Tue, 5 May 2026 19:45:02 +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=1778010303; cv=none; b=gaDzKjzeNs/6irUwkXKUd+iO2hLELBf7DckTpAmqoutqUJgpy7EbicOysHWdoDRLvcJsGC8r3ZAGPsw98nwi6DHQtGGHcqf0zSI/DHGVVjw/6bOKRYP+XR3r5H9g2rduGIyFfbSOj/lrv2Er0rN6aXRNplTUzFfUWmz6SLYeEi8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778010303; c=relaxed/simple; bh=NmT6DVe9ATLJwqubgZU8SUcwl+X6QPGj+PpZGS7QtRw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Di7pAY3rWXPfGGxFx+xj0Ten8fFpVIqsFoiY6ZTZUvSLqwbAFj6xRhNnow4OGY1doK9IIx3inUDt2RQRQqsOh6WhMs5sMIjw40wfCFyPeL/HDcy71oAD2S1TuecAPlDmPr5z2VKL9CVuMK2pNI06rZ0t3Q3MUkBkCneQEcdVe3Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=TmJFQ1kz; 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="TmJFQ1kz" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E4044C2BCB4; Tue, 5 May 2026 19:45:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778010302; bh=NmT6DVe9ATLJwqubgZU8SUcwl+X6QPGj+PpZGS7QtRw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=TmJFQ1kziJ1/QEOICQn7oG81ImsADDzKzoxREfO9uyP+gAjP2bQO6i4sRSB4xgL9k F/0xnID3sONrR+MOYESf3UQLOMFOKOfx6wA4m2FJygzPOoAk1hjSrdOI8VgUEwGW9S qr4phZUxMjdcEEm0JdWQOl+ple+h5wndhCArnDtCIGEI3xMZgoJncnl3jXGfuiGjBp 3J0cRZ5RYVAVAYz/bXK2DCLbqAb0ttM9xmlXeqdt5L77eP7h/MRGYM8GUS/UcgKTUL 5QJz271va2WfGJfStlretQk6ZH4zb18Vj7QfB3Qw1NdV8Nnpi5oyYORCFbGOYPYPZf 8/aXgOlzHp5Fg== 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: <20260503-imsic-v1-1-aa8330bd1c34@sifive.com> References: <20260503-imsic-v1-1-aa8330bd1c34@sifive.com> Date: Tue, 05 May 2026 21:44:59 +0200 Message-ID: <87bjety72c.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 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