From: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH V4 0/3] powerpc/powernv: Error logging interfaces
Date: Tue, 04 Feb 2014 00:59:23 +0530 [thread overview]
Message-ID: <20140203192915.7790.20325.stgit@deepthi> (raw)
This patch series defines generic interfaces for error logging to
push down critical errors from powernv platform to FSP.
Also, it contains few minor fixes for the exisiting error logging
framework that retrieves error logs from FSP.
Changes from V3:
* Change memory allocation to GFP_ATOMIC, to generate
errors in bad context
* Move all error log generation related code to arch/powernv
rename it from opal_* to pnv_* .
Changes from V2:
* Review comments from V2 have been addressed
includes comment formats, changing naming
conventions and incorporated error handling
of the buffers.
* Minor typo fix and use of pr_err/pr_fmt to
log errors.
Deepthi Dharwar (3):
powernv: Push critical error logs to FSP
powernv: Correct spell error in opal-elog.c
powernv: Have uniform logging of errors in opal-elog.c
arch/powerpc/include/asm/opal.h | 36 +++++++++
arch/powerpc/platforms/powernv/opal-elog.c | 93 +++++++++++++++++++++---
arch/powerpc/platforms/powernv/opal-wrappers.S | 2 -
arch/powerpc/platforms/powernv/powernv.h | 84 ++++++++++++++++++++++
4 files changed, 203 insertions(+), 12 deletions(-)
-- Deepthi
next reply other threads:[~2014-02-03 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 19:29 Deepthi Dharwar [this message]
2014-02-03 19:29 ` [PATCH V4 1/3] powerpc/powernv: Push critical error logs to FSP Deepthi Dharwar
2014-02-03 19:29 ` [PATCH V4 2/3] powerpc/powernv: Correct spell error in opal-elog.c Deepthi Dharwar
2014-02-03 19:30 ` [PATCH V4 3/3] powerpc/powernv: Have uniform logging of errors " Deepthi Dharwar
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=20140203192915.7790.20325.stgit@deepthi \
--to=deepthi@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).