From: Joel Stanley <joel@jms.id.au>
To: benh@kernel.crashing.org, paulus@samba.org, anton@samba.org,
shangw@linux.vnet.ibm.com, hegdevasant@linux.vnet.ibm.com,
michael@ellerman.id.au, stewart@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] OPAL message log interface
Date: Fri, 28 Mar 2014 10:20:38 +1030 [thread overview]
Message-ID: <1395964240-8305-1-git-send-email-joel@jms.id.au> (raw)
These two patches add support for the message log, and expose a new OPAL call
called opal_invalid that allow me to cause OPAL to inject messages into the
log.
The naming is a bit mixed, as our device tree node is opal-memcons and I
retained the naming of the header structure 'struct memcons', but all other
references are to the OPAL message log.
They have been tested on a POWER7+ machine running some recent firmware.
Joel Stanley (2):
powerpc/powernv: Add OPAL message log interface
powerpc/powernv: Add invalid OPAL call
arch/powerpc/include/asm/opal.h | 6 ++
arch/powerpc/platforms/powernv/Makefile | 1 +
arch/powerpc/platforms/powernv/opal-messages.c | 97 ++++++++++++++++++++++++++
arch/powerpc/platforms/powernv/opal-wrappers.S | 1 +
arch/powerpc/platforms/powernv/opal.c | 6 +-
5 files changed, 110 insertions(+), 1 deletion(-)
create mode 100644 arch/powerpc/platforms/powernv/opal-messages.c
--
1.9.1
next reply other threads:[~2014-03-27 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 23:50 Joel Stanley [this message]
2014-03-27 23:50 ` [PATCH 1/2] powerpc/powernv: Add OPAL message log interface Joel Stanley
2014-03-30 22:21 ` Stewart Smith
2014-03-31 4:08 ` Michael Neuling
2014-03-31 4:21 ` Michael Neuling
2014-03-31 11:59 ` Benjamin Herrenschmidt
2014-03-31 22:52 ` Joel Stanley
2014-03-27 23:50 ` [PATCH 2/2] powerpc/powernv: Add invalid OPAL call Joel Stanley
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=1395964240-8305-1-git-send-email-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
--cc=shangw@linux.vnet.ibm.com \
--cc=stewart@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).