mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mihai Carabas <mihai.carabas@oracle.com>
To: scott@os.amperecomputing.com
Cc: catalin.marinas@arm.com, darren@os.amperecomputing.com,
	james.morse@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, will@kernel.org
Subject: Re: [PATCH v6] arm64: sdei: abort running SDEI handlers during crash
Date: Thu, 20 Jul 2023 12:43:35 +0300	[thread overview]
Message-ID: <9830b94a-da88-48f2-6fcd-da46b2e2ed0a@oracle.com> (raw)
In-Reply-To: <20230627002939.2758-1-scott@os.amperecomputing.com>

 > 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.

 > Fixes: f5df26961853 ("arm64: kernel: Add arch-specific SDEI entry 
code and CPU masking")
 > Signed-off-by: D Scott Phillips <scott@os.amperecomputing.com>

We have tested successfully this patch on Altra and AmpereOne.

Tested-by: Mihai Carabas <mihai.carabas@oracle.com>

  parent reply	other threads:[~2023-07-20  9:47 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 [this message]
2023-07-24 20:31 ` D Scott Phillips
2023-08-02 14:24 ` James Morse
2023-08-04 18:10 ` Will Deacon

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=9830b94a-da88-48f2-6fcd-da46b2e2ed0a@oracle.com \
    --to=mihai.carabas@oracle.com \
    --cc=catalin.marinas@arm.com \
    --cc=darren@os.amperecomputing.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott@os.amperecomputing.com \
    --cc=will@kernel.org \
    /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®