From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>
Cc: linuxppc-dev@lists•ozlabs.org, Nicholas Piggin <npiggin@gmail•com>
Subject: Re: powerpc/pseries: add definitions for new H_SIGNAL_SYS_RESET hcall
Date: Sat, 3 Dec 2016 22:28:15 +1100 (AEDT) [thread overview]
Message-ID: <3tW80H3Pn5z9t1F@ozlabs.org> (raw)
In-Reply-To: <20161108060806.16168-1-npiggin@gmail.com>
On Tue, 2016-11-08 at 06:08:06 UTC, Nicholas Piggin wrote:
> This has not made its way to a PAPR release yet, but we have an hcall
> number assigned.
>
> H_SIGNAL_SYS_RESET = 0x380
>
> Syntax:
> hcall(uint64 H_SIGNAL_SYS_RESET, /* generate a system reset NMI on */
> /* the threads indicated by target */
> int64 target); /* thread target selection */
> /* -1 = target all online threads including the caller */
> /* -2 = target all online threads except for the caller */
> /* All other negative values: reserved */
> /* Positive values: The thread to be targeted, */
> /* obtained from the value of the "ibm,ppc-interrupt-server#s" */
> /* property of the CPU in the OF device tree */
>
> Semantics:
> - If the NMI handlers are not registered, terminate the partition.
> - Invalid target: return H_Parameter.
> - Otherwise: Generate a system reset NMI on target thread(s),
> return H_Success.
>
> This will be used by crash/debug code to get stuck CPUs into a known state.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/53ce299615e587e900548eb6b384c3
cheers
prev parent reply other threads:[~2016-12-03 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 6:08 [PATCH] powerpc/pseries: add definitions for new H_SIGNAL_SYS_RESET hcall Nicholas Piggin
2016-11-08 8:40 ` Michael Ellerman
2016-12-03 11:28 ` Michael Ellerman [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=3tW80H3Pn5z9t1F@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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