linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH 0/6] EEH Cleanup
Date: Wed, 16 Jul 2014 15:50:13 +1000	[thread overview]
Message-ID: <1405489819-26211-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)

The patchset is EEH cleanup and expected to be merged during 3.17
window. The the patchset is expected to be applied after:

   |    EEH support for guest
   |    2 more bug fixes for EEH support for guest
   |    M64 related EEH changes
   |    2 bug fixes from Mike Qiu
   |
   +->  The current patchset

Except the following 2 patches, all patches are for cleanup:
Refactoring EEH log, replacing pr_warning() with pr_warn(),
reducing length of EEH log dump etc:

PATCH[2/6]: We have to enable I/O path before collecting EEH log.
            Otherwise, 0xFF is always returned from PCI config
            of devices in frozen PE. the problem is only existing
            on PHB3.
PATCH[6/6]: It's something related to EEH guest log retrieval.
	    Currently, all PEs in one specific PHB are sharing
	    diag-data blob for storing EEH log. It's possible
	    for diag-data blob overwritten before being collected
            by guest. The patch introduce auxillary data for PE,
            which is maintained by backend. On PowerNV, that's used
            for EEH log.

Gavin Shan (6):
  powerpc/eeh: Refactor EEH flag accessors
  powerpc/eeh: Selectively enable IO for error log
  powerpc/eeh: Reduce lines of log dump
  powerpc/eeh: Replace pr_warning() with pr_warn()
  powerpc/eeh: Make diag-data not endian dependent
  powerpc/eeh: Aux PE data for error log

 arch/powerpc/include/asm/eeh.h               |  43 ++++-----
 arch/powerpc/include/asm/opal.h              | 128 +++++++++++++--------------
 arch/powerpc/kernel/eeh.c                    |  73 ++++++++++-----
 arch/powerpc/kernel/eeh_cache.c              |   9 +-
 arch/powerpc/kernel/eeh_dev.c                |   3 +-
 arch/powerpc/kernel/eeh_driver.c             |  16 ++--
 arch/powerpc/kernel/eeh_pe.c                 |  29 +++++-
 arch/powerpc/platforms/powernv/eeh-ioda.c    | 103 +++++++++++++--------
 arch/powerpc/platforms/powernv/eeh-powernv.c |  32 +++++--
 arch/powerpc/platforms/powernv/pci-ioda.c    |   1 -
 arch/powerpc/platforms/powernv/pci.c         |  68 ++++++++------
 arch/powerpc/platforms/pseries/eeh_pseries.c |  32 +++----
 12 files changed, 323 insertions(+), 214 deletions(-)

-- 
1.8.3.2

             reply	other threads:[~2014-07-16  5:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  5:50 Gavin Shan [this message]
2014-07-16  5:50 ` [PATCH 1/6] powerpc/eeh: Refactor EEH flag accessors Gavin Shan
2014-07-16  8:24   ` David Laight
2014-07-16 12:10     ` Gavin Shan
2014-07-16  5:50 ` [PATCH 2/6] powerpc/eeh: Selectively enable IO for error log Gavin Shan
2014-07-16  5:50 ` [PATCH 3/6] powerpc/eeh: Reduce lines of log dump Gavin Shan
2014-07-16  8:30   ` David Laight
2014-07-16 12:26     ` Gavin Shan
2014-07-16  5:50 ` [PATCH 4/6] powerpc/eeh: Replace pr_warning() with pr_warn() Gavin Shan
2014-07-16  5:50 ` [PATCH 5/6] powerpc/eeh: Make diag-data not endian dependent Gavin Shan
2014-07-16  5:50 ` [PATCH 6/6] powerpc/eeh: Aux PE data for error log Gavin Shan

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=1405489819-26211-1-git-send-email-gwshan@linux.vnet.ibm.com \
    --to=gwshan@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).