linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.ibm.com>
To: Ananth N Mavinakayanahalli <ananth@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	Vasant Hegde <hegdevasant@linux.ibm.com>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Stewart Smith <stewart@linux.ibm.com>
Subject: [RFC PATCH 0/5] Add FADump support on PowerNV platform
Date: Tue, 15 May 2018 10:28:50 +0530	[thread overview]
Message-ID: <152636029761.17123.10365462779196202939.stgit@hbathini.in.ibm.com> (raw)

Firmware-Assisted Dump (FADump) is currently supported only on pseries
platform. This patch series adds support for powernv platform too. 

The first two patches refactor the FADump code to make use of common
code across multiple platforms. The third patch adds basic FADump support
to powernv platform. The next patch processes state data provided by f/w
and adds core notes to core file. The last patch adds support to export
opalcore. This is to make debugging of failures in opal code easier.

The patch series is tested with a few workarounds in firmware and kernel
as the full and final firmware support is currently being worked on.
The below skiboot patch series adds the relevant OPAL changes:

    http://patchwork.ozlabs.org/project/skiboot/list/?series=42576

---

Hari Bathini (5):
      powerpc/fadump: move internal fadump code to a new file
      pseries/fadump: move out platform specific support from generic code
      powerpc/fadump: enable fadump support on powernv platform
      powerpc/fadump: process architected register state data provided by firmware
      powerpc/powernv: export /proc/opaldump for analysing opal crashes


 arch/powerpc/Kconfig                            |    2 
 arch/powerpc/include/asm/fadump.h               |  185 ----
 arch/powerpc/include/asm/opal-api.h             |    4 
 arch/powerpc/include/asm/opal.h                 |    1 
 arch/powerpc/kernel/Makefile                    |    2 
 arch/powerpc/kernel/fadump.c                    | 1111 +++++++++--------------
 arch/powerpc/kernel/fadump_internal.c           |  194 ++++
 arch/powerpc/kernel/fadump_internal.h           |  197 ++++
 arch/powerpc/platforms/powernv/Makefile         |    1 
 arch/powerpc/platforms/powernv/opal-wrappers.S  |    1 
 arch/powerpc/platforms/powernv/opalcore.c       |  282 ++++++
 arch/powerpc/platforms/powernv/opalcore.h       |   28 +
 arch/powerpc/platforms/powernv/powernv_fadump.c |  503 ++++++++++
 arch/powerpc/platforms/powernv/powernv_fadump.h |   72 +
 arch/powerpc/platforms/pseries/Makefile         |    1 
 arch/powerpc/platforms/pseries/pseries_fadump.c |  532 +++++++++++
 arch/powerpc/platforms/pseries/pseries_fadump.h |   96 ++
 17 files changed, 2335 insertions(+), 877 deletions(-)
 create mode 100644 arch/powerpc/kernel/fadump_internal.c
 create mode 100644 arch/powerpc/kernel/fadump_internal.h
 create mode 100644 arch/powerpc/platforms/powernv/opalcore.c
 create mode 100644 arch/powerpc/platforms/powernv/opalcore.h
 create mode 100644 arch/powerpc/platforms/powernv/powernv_fadump.c
 create mode 100644 arch/powerpc/platforms/powernv/powernv_fadump.h
 create mode 100644 arch/powerpc/platforms/pseries/pseries_fadump.c
 create mode 100644 arch/powerpc/platforms/pseries/pseries_fadump.h

--
Signature

             reply	other threads:[~2018-05-15  4:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15  4:58 Hari Bathini [this message]
2018-05-15  4:58 ` [RFC PATCH 1/5] powerpc/fadump: move internal fadump code to a new file Hari Bathini
2018-05-15  4:59 ` [RFC PATCH 2/5] pseries/fadump: move out platform specific support from generic code Hari Bathini
2018-05-15  4:59 ` [RFC PATCH 3/5] powerpc/fadump: enable fadump support on powernv platform Hari Bathini
2018-05-15  4:59 ` [RFC PATCH 4/5] powerpc/fadump: process architected register state data provided by firmware Hari Bathini
2018-05-15  4:59 ` [RFC PATCH 5/5] powerpc/powernv: export /proc/opaldump for analysing opal crashes Hari Bathini

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=152636029761.17123.10365462779196202939.stgit@hbathini.in.ibm.com \
    --to=hbathini@linux.ibm.com \
    --cc=ananth@linux.ibm.com \
    --cc=hegdevasant@linux.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=stewart@linux.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).