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;
From:   Will Deacon <will@kernel.org>
To:     D Scott Phillips <scott@os.amperecomputing.com>,
        linux-arm-kernel@lists.infradead.org,
        James Morse <james.morse@arm.com>
Cc:     catalin.marinas@arm.com, kernel-team@android.com,
        Will Deacon <will@kernel.org>,
        Darren Hart <darren@os.amperecomputing.com>,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] arm64: sdei: abort running SDEI handlers during crash
Date:   Fri,  4 Aug 2023 19:10:15 +0100
Message-Id: <169116693391.147594.8584700236925488135.b4-ty@kernel.org>
In-Reply-To: <20230627002939.2758-1-scott@os.amperecomputing.com>
References: <20230627002939.2758-1-scott@os.amperecomputing.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 26 Jun 2023 17:29:39 -0700, D Scott Phillips wrote:
> Interrupts are blocked in SDEI context, per the SDEI spec: "The client
> interrupts cannot preempt the event handler." If we crashed in the SDEI
> handler-running context (as with ACPI's AGDI) then we need to clean up the
> SDEI state before proceeding to the crash kernel so that the crash kernel
> can have working interrupts.
> 
> Track the active SDEI handler per-cpu so that we can COMPLETE_AND_RESUME
> the handler, discarding the interrupted context.
> 
> [...]

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64: sdei: abort running SDEI handlers during crash
      https://git.kernel.org/arm64/c/5cd474e57368

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev