Oliver O'Halloran <ooh...@gmail.com> writes: > Recent versions of skiboot will raise an OPAL event (read: interrupt) > when firmware writes an error message to its internal console. In > conjunction they provide an OPAL call that the kernel can use to extract > these messages from the OPAL log to allow them to be written into the > kernel's log buffer where someone will (hopefully) look at them. > > For the companion skiboot patches see: > > https://lists.ozlabs.org/pipermail/skiboot/2016-December/005861.html > > Signed-off-by: Oliver O'Halloran <ooh...@gmail.com> > --- > arch/powerpc/include/asm/opal-api.h | 5 +++- > arch/powerpc/include/asm/opal.h | 1 + > arch/powerpc/platforms/powernv/opal-msglog.c | 41 > ++++++++++++++++++++++++++ > arch/powerpc/platforms/powernv/opal-wrappers.S | 1 + > 4 files changed, 47 insertions(+), 1 deletion(-) > > diff --git a/arch/powerpc/include/asm/opal-api.h > b/arch/powerpc/include/asm/opal-api.h > index 0e2e57bcab50..cb9c0e6afb33 100644 > --- a/arch/powerpc/include/asm/opal-api.h > +++ b/arch/powerpc/include/asm/opal-api.h > @@ -167,7 +167,8 @@ > #define OPAL_INT_EOI 124 > #define OPAL_INT_SET_MFRR 125 > #define OPAL_PCI_TCE_KILL 126 > -#define OPAL_LAST 126 > +#define OPAL_SCRAPE_LOG 128
(another thought, along with the skiboot thoughts), I don't like the SCRAPE_LOG name so much, as it's more of a "hey linux, here's some log messages from firmware, possibly before you were involved"... OPAL_FETCH_LOG ? -- Stewart Smith OPAL Architect, IBM.