linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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, mikey@neuling.org,
	stewart@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 0/2] OPAL message log interface
Date: Tue,  1 Apr 2014 14:28:18 +1030	[thread overview]
Message-ID: <1396324700-22457-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.

Changes in V2:

The guts of the function used to read the console has been reworked. In doing
so, I've addressed the comments from Mikey and Ben:

 - Added barrier between reading header and data
 - Only read out_pos once
 - Check the return code before adding it to the number of bytes read

Unlike V1, this version correctly reads out a wrapped buffer.

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-msglog.c   | 120 +++++++++++++++++++++++++
 arch/powerpc/platforms/powernv/opal-wrappers.S |   1 +
 arch/powerpc/platforms/powernv/opal.c          |   7 +-
 5 files changed, 134 insertions(+), 1 deletion(-)
 create mode 100644 arch/powerpc/platforms/powernv/opal-msglog.c

-- 
1.9.1

             reply	other threads:[~2014-04-01  3:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  3:58 Joel Stanley [this message]
2014-04-01  3:58 ` [PATCH v2 1/2] powerpc/powernv: Add OPAL message log interface Joel Stanley
2014-04-01  3:58 ` [PATCH v2 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=1396324700-22457-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=mikey@neuling.org \
    --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).