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 [thread overview]
Message-ID: <169116693391.147594.8584700236925488135.b4-ty@kernel.org> (raw)
In-Reply-To: <20230627002939.2758-1-scott@os.amperecomputing.com>
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
prev parent reply other threads:[~2023-08-04 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 0:29 D Scott Phillips
2023-07-06 22:00 ` D Scott Phillips
2023-07-20 9:43 ` Mihai Carabas
2023-07-24 20:31 ` D Scott Phillips
2023-08-02 14:24 ` James Morse
2023-08-04 18:10 ` Will Deacon [this message]
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=169116693391.147594.8584700236925488135.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=darren@os.amperecomputing.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@os.amperecomputing.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
all inboxes | Powered by JetHome®