On Thu, 20 Oct 2016 11:21:22 +0200
Thomas Huth <th...@redhat.com> wrote:
> On 20.10.2016 08:59, Nicholas Piggin wrote:
> > The H_SIGNAL_SYS_RESET hcall allows a guest CPU to raise a system
> > reset exception on other CPUs in the same guest.
> >
> > Signed-off-by: Nicholas Piggin <npig...@gmail.com>
> > ---
> > hw/ppc/spapr_hcall.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> > include/hw/ppc/spapr.h | 8 +++++++-
> > 2 files changed, 49 insertions(+), 1 deletion(-)
> ...
> > diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
> > index aeaba3e..a28538b 100644
> > --- a/include/hw/ppc/spapr.h
> > +++ b/include/hw/ppc/spapr.h
> > @@ -339,7 +339,13 @@ struct sPAPRMachineState {
> > #define H_XIRR_X 0x2FC
> > #define H_RANDOM 0x300
> > #define H_SET_MODE 0x31C
> > -#define MAX_HCALL_OPCODE H_SET_MODE
> > +#define H_SIGNAL_SYS_RESET 0x380
> > +#define MAX_HCALL_OPCODE H_SIGNAL_SYS_RESET
> > +
> > +/* Parameters to H_SIGNAL_SYS_RESET */
> > +#define H_SIGNAL_SYS_RESET_ALL -1
> > +#define H_SIGNAL_SYS_RESET_ALLBUTSELF -2
> > +
> >
> > /* The hcalls above are standardized in PAPR and implemented by pHyp
> > * as well.
>
> Is there a spec for this hypercall? I can't find it in LoPAPR v1.1 ?
Oh sorry, I should have said that this is going through an internal
process at moment and not in a released document yet. I'll try to get
a more satisfying answer on that one.
Thanks,
Nick
