All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
Cc: "jirislaby@kernel.org" <jirislaby@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	SoC Team <soc@kernel.org>, Olof Johansson <olof@lixom.net>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH] soc: fujitsu: Add A64FX diagnostic interrupt driver
Date: Fri, 25 Feb 2022 11:51:26 +0100	[thread overview]
Message-ID: <Yhi0rrkSR63ZhjX1@kroah.com> (raw)
In-Reply-To: <OSZPR01MB7050EF799D97D05A8C4597E7EB3E9@OSZPR01MB7050.jpnprd01.prod.outlook.com>

On Fri, Feb 25, 2022 at 10:35:10AM +0000, hasegawa-hitomi@fujitsu.com wrote:
> Hi Greg and Jiri,
> 
> I'm trying to implement a feature for A64FX that will panic when
> a diagnostic interrupt is received.
> Arnd suggested that handle_sysrq() should be used
> but I'm wonderingif it's ok to call it in NMI.
> Would you please let me know if we can call handle_sysrq() in NMI?

I doubt it, but try it and see!

WARNING: multiple messages have this Message-ID (diff)
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
Cc: "jirislaby@kernel.org" <jirislaby@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	SoC Team <soc@kernel.org>, Olof Johansson <olof@lixom.net>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH] soc: fujitsu: Add A64FX diagnostic interrupt driver
Date: Fri, 25 Feb 2022 11:51:26 +0100	[thread overview]
Message-ID: <Yhi0rrkSR63ZhjX1@kroah.com> (raw)
In-Reply-To: <OSZPR01MB7050EF799D97D05A8C4597E7EB3E9@OSZPR01MB7050.jpnprd01.prod.outlook.com>

On Fri, Feb 25, 2022 at 10:35:10AM +0000, hasegawa-hitomi@fujitsu.com wrote:
> Hi Greg and Jiri,
> 
> I'm trying to implement a feature for A64FX that will panic when
> a diagnostic interrupt is received.
> Arnd suggested that handle_sysrq() should be used
> but I'm wonderingif it's ok to call it in NMI.
> Would you please let me know if we can call handle_sysrq() in NMI?

I doubt it, but try it and see!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-02-25 10:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  9:20 [PATCH] soc: fujitsu: Add A64FX diagnostic interrupt driver Hitomi Hasegawa
2022-02-18  9:20 ` Hitomi Hasegawa
2022-02-18 10:35 ` Arnd Bergmann
2022-02-18 10:35   ` Arnd Bergmann
2022-02-22 10:52   ` hasegawa-hitomi
2022-02-22 10:52     ` hasegawa-hitomi
2022-02-25 10:35     ` hasegawa-hitomi
2022-02-25 10:35       ` hasegawa-hitomi
2022-02-25 10:51       ` gregkh [this message]
2022-02-25 10:51         ` gregkh
2022-02-25 11:20       ` Arnd Bergmann
2022-02-25 11:20         ` Arnd Bergmann
2022-02-28  8:05         ` Sumit Garg
2022-02-28  8:05           ` Sumit Garg
2022-02-28  8:51           ` hasegawa-hitomi
2022-02-28  8:51             ` hasegawa-hitomi

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=Yhi0rrkSR63ZhjX1@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=hasegawa-hitomi@fujitsu.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.