Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
In-Reply-To: <20230703183126.1567625-1-maz@kernel.org>
References: <20230703183126.1567625-1-maz@kernel.org>
Subject: Re: [PATCH] risc-v: Fix order of IPI enablement vs RCU startup
Message-Id: <168860030768.22647.6698047675033569268.b4-ty@rivosinc.com>
Date:   Wed, 05 Jul 2023 16:38:27 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc:     Conor Dooley <conor@kernel.org>,
        Anup Patel <apatel@ventanamicro.com>,
        Linus Torvalds <torvalds@linux-foundation.org>
From:   Palmer Dabbelt <palmer@rivosinc.com>
To:     linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org>
Precedence: bulk


On Mon, 03 Jul 2023 19:31:26 +0100, Marc Zyngier wrote:
> Conor reports that risc-v tries to enable IPIs before telling the
> core code to enable RCU. With the introduction of the mapple tree
> as a backing store for the irq descriptors, this results in
> a very shouty boot sequence, as RCU is legitimately upset.
> 
> Restore some sanity by moving the risc_ipi_enable() call after
> notify_cpu_starting(), which explicitly enables RCU on the calling
> CPU.
> 
> [...]

Applied, thanks!

[1/1] risc-v: Fix order of IPI enablement vs RCU startup
      https://git.kernel.org/palmer/c/6259f3443c6a

Best regards,
-- 
Palmer Dabbelt <palmer@rivosinc.com>