From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH V2 00/16] powerpc/eeh: PE support
Date: Thu, 28 Jun 2012 00:05:25 +0800 [thread overview]
Message-ID: <20120627160525.GA7030@shangw> (raw)
In-Reply-To: <1340812911-6793-1-git-send-email-shangw@linux.vnet.ibm.com>
I'm sorry that the subject should be:
[PATCH V2 00/21] powerpc/eeh: PE support
I forgot got change that when pulling it from V1 :-)
Thanks,
Gavin
>The series of patches address explicit PE support as well as probe type
>support. For explicit PE support, struct eeh_pe has been introduced.
>While designing the struct, following factors have been taken into
>account.
>
> * For one particular PE, it might be composed of single PCI device,
> or multiple PCI devices and its educed children PCI devices (e.g.
> by PCIe bridges). The PE struct has included a linked list to refer
> the included PCI devices. Also, the linked list of devices has relected
> top-to-bottom fasion of the PCI subtree. That's to say, the first device
> in the linked list should be the toppest element in the PCI subtree which
> is being managed by the PE.
> * PEs correlate to each other. So the existing PEs have to form hierarchy
> levels. There're some fields in PE struct (e.g. parent/child/silbing)
> have been introduced for the purpose.
> * For one PE, it's only meaningful in the PHB domain.
>
>In addition, the mechniasm used to do memory bars restore, error report have
>been reworked based on PE. The eeh cache has been reworked for a little bit
>based on Ben's suggestion to trace eeh device.
>
>In order for explicit probe support, either OF node or pci device, global
>variable and some inline functions are introduced. For pSeries platform, it's
>going to support OF node probe and figure out PEs from the corresponding OF
>nodes. In contrast, powernv platform has to use pci device probe type since
>the PEs are being constructed at PHB fixup time.
>
>The series of patches have been verified on Firebird-L machine using "errinjct"
>utility. Here's the command used for that.
>
>errinjct eeh -v -f 0 -p U78AE.001.WZS00M9-P1-C18-L1-T2 -a 0x0 -m 0x0
>
>V1 -> V2
> * Rebase to 3.5.RC4.
> * Use the link list to trace the relationships of PEs, PE and eeh
> devices according to Ram's suggestion.
> * Simplify the PE tranverse function according to Ram's example.
> * Move EEH initialization around according to Ben's suggestion so
> that we can do memory allocation through slab.
> * Use kzmalloc() to allocate memory chunks for PE and eeh devices.
> * More booting messages for EEH initialization functions.
> * Introduce global EEH mutex to protect the PEs and eeh devices.
> * Added functions to support PE removal.
> * Comments cleanup
> * Change on the comparison of PE or BDF (Bus/Device/Function)
> address so that code looks more readable.
>
>arch/powerpc/include/asm/eeh.h | 132 ++++--
>arch/powerpc/include/asm/eeh_event.h | 6 +-
>arch/powerpc/include/asm/pci-bridge.h | 2 +
>arch/powerpc/include/asm/ppc-pci.h | 15 +-
>arch/powerpc/kernel/rtas_pci.c | 5 +-
>arch/powerpc/platforms/pseries/Makefile | 5 +-
>arch/powerpc/platforms/pseries/eeh.c | 527 +++++------------------
>arch/powerpc/platforms/pseries/eeh_cache.c | 19 +-
>arch/powerpc/platforms/pseries/eeh_dev.c | 14 +-
>arch/powerpc/platforms/pseries/eeh_driver.c | 235 +++++------
>arch/powerpc/platforms/pseries/eeh_event.c | 53 +--
>arch/powerpc/platforms/pseries/eeh_pe.c | 583 ++++++++++++++++++++++++++
>arch/powerpc/platforms/pseries/eeh_pseries.c | 246 +++++++----
>arch/powerpc/platforms/pseries/eeh_sysfs.c | 9 -
>arch/powerpc/platforms/pseries/msi.c | 6 +-
>arch/powerpc/platforms/pseries/setup.c | 2 -
>16 files changed, 1119 insertions(+), 740 deletions(-)
>create mode 100644 arch/powerpc/platforms/pseries/eeh_pe.c
>
>Thanks,
>Gavin
>
prev parent reply other threads:[~2012-06-27 16:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 16:01 [PATCH V2 00/16] powerpc/eeh: PE support Gavin Shan
2012-06-27 16:01 ` [PATCH 01/21] ppc/eeh: move EEH initialization around Gavin Shan
2012-06-27 16:01 ` [PATCH 02/21] ppc/eeh: use slab to allocate eeh devices Gavin Shan
2012-06-27 16:01 ` [PATCH 03/21] ppc/eeh: more logs for EEH initialization Gavin Shan
2012-06-27 23:45 ` Michael Ellerman
2012-06-28 2:40 ` Gavin Shan
2012-06-27 16:01 ` [PATCH 04/21] ppc/eeh: Introduce eeh_pe struct Gavin Shan
2012-06-27 16:01 ` [PATCH 05/21] ppc/eeh: introduce global mutex Gavin Shan
2012-06-27 16:01 ` [PATCH 06/21] ppc/eeh: Create PEs for PHBs Gavin Shan
2012-06-27 16:01 ` [PATCH 07/21] ppc/eeh: Search PE based on requirement Gavin Shan
2012-06-27 16:01 ` [PATCH 08/21] ppc/eeh: create PEs duing EEH initialization Gavin Shan
2012-06-27 16:01 ` [PATCH 09/21] ppc/eeh: remove PE at appropriate time Gavin Shan
2012-06-27 16:01 ` [PATCH 10/21] ppc/eeh: build EEH event based on PE Gavin Shan
2012-06-27 16:01 ` [PATCH 11/21] ppc/eeh: trace EEH state " Gavin Shan
2012-06-27 16:01 ` [PATCH 12/21] ppc/eeh: trace error based on PE from beginning Gavin Shan
2012-06-27 16:01 ` [PATCH 13/21] ppc/eeh: eeh options based on PE Gavin Shan
2012-06-27 16:01 ` [PATCH 14/21] ppc/eeh: device bars restore " Gavin Shan
2012-06-27 16:01 ` [PATCH 15/21] ppc/eeh: I/O enable and log retrival " Gavin Shan
2012-06-27 16:01 ` [PATCH 16/21] ppc/eeh: do reset " Gavin Shan
2012-06-27 16:01 ` [PATCH 17/21] ppc/eeh: make EEH handler PE sensitive Gavin Shan
2012-06-27 16:01 ` [PATCH 18/21] ppc/eeh: handle EEH error based on PE Gavin Shan
2012-06-27 16:01 ` [PATCH 19/21] ppc/eeh: move stats to PE Gavin Shan
2012-06-27 16:01 ` [PATCH 20/21] ppc/eeh: probe mode support Gavin Shan
2012-06-27 16:01 ` [PATCH 21/21] ppc/eeh: trace eeh device from I/O cache Gavin Shan
2012-06-27 16:05 ` Gavin Shan [this message]
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=20120627160525.GA7030@shangw \
--to=shangw@linux.vnet.ibm.com \
--cc=linuxppc-dev@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).