From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: From: Gavin Shan <shangw@linux.vnet.ibm.com>
Date: Thu, 27 Jun 2013 13:51:03 +0800 [thread overview]
Message-ID: <20130627055103.GA14126@shangw.(null)> (raw)
In-Reply-To: <1372312009-13710-1-git-send-email-shangw@linux.vnet.ibm.com>
On Thu, Jun 27, 2013 at 01:46:41PM +0800, Gavin Shan wrote:
The subject went wrong. I didn't make the format correct and here's
the makeup:
[PATCH v4 00/8] Follow-up fixes for EEH on PowerNV
>The series of patches are follow-up in order to make EEH workable for PowerNV
>platform on Juno-IOC-L machine. Couple of issues have been fixed with help of
>Ben:
>
> - Check PCIe link after PHB complete reset
> - Restore config space for bridges
> - The EEH address cache wasn't built successfully
> - Misc cleanup on output messages
> - Misc cleanup on EEH flags maintained by "struct pnv_phb"
> - Misc cleanup on properties of functions to avoid build warnings
> - Let PCI config accessors rely on device node
> - Do hotplug during reset for those devices whose drivers can't
> support EEH
>
>---
>
>Trigger frozen PE:
>
> echo 0x0000000002000000 > /sys/kernel/debug/powerpc/PCI0000/err_injct
> sleep 1
> echo 0x0 > /sys/kernel/debug/powerpc/PCI0000/err_injct
>
>Trigger fenced PHB:
>
> echo 0x8000000000000000 > /sys/kernel/debug/powerpc/PCI0000/err_injct
>
>
>---
>
>Changelog:
>==========
>v3 -> v4:
> * Add more output messages in EEH core to let users know what the EEH
> core is doing.
> * Add one patch to use device node in the PCI config accessors since
> the accessors used by EEH and it's not safe enough to refer PCI device
> and bus. We instead fully utilize the information from PCI_DN.
> * Add one patch to remove those deivces whose drivers can't support EEH
> before reset, and add them to the system after reset.
>v2 -> v3:
> * Fix overwritten buffer while collecting data from PCI config space.
>v1 -> v2:
> * Remove the mechanism to block PCI-CFG and MMIO.
> * Add one patch to do cleanup on output messages.
> * Add one patch to avoid build warnings.
> * Split functions to restore BARs for PCI devices and bridges separately.
>
>---
>
>arch/powerpc/include/asm/eeh.h | 8 +-
>arch/powerpc/include/asm/pci.h | 1 +
>arch/powerpc/kernel/eeh.c | 43 +++++--
>arch/powerpc/kernel/eeh_cache.c | 4 +-
>arch/powerpc/kernel/eeh_driver.c | 157 +++++++++++++++++++++++-
>arch/powerpc/kernel/eeh_pe.c | 166 ++++++++++++++++++++++++--
>arch/powerpc/kernel/pci_hotplug.c | 8 +-
>arch/powerpc/platforms/powernv/eeh-ioda.c | 33 +++--
>arch/powerpc/platforms/powernv/eeh-powernv.c | 44 +-------
>arch/powerpc/platforms/powernv/pci-ioda.c | 1 +
>arch/powerpc/platforms/powernv/pci.c | 124 ++++++++++++--------
>arch/powerpc/platforms/powernv/pci.h | 11 ++-
>drivers/pci/probe.c | 6 +-
>13 files changed, 462 insertions(+), 144 deletions(-)
>
>Thanks,
>Gavin
>
>_______________________________________________
>Linuxppc-dev mailing list
>Linuxppc-dev@lists.ozlabs.org
>https://lists.ozlabs.org/listinfo/linuxppc-dev
>
prev parent reply other threads:[~2013-06-27 5:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 5:46 From: Gavin Shan <shangw@linux.vnet.ibm.com> Gavin Shan
2013-06-27 5:46 ` [PATCH 1/8] powerpc/eeh: Don't collect PCI-CFG data on PHB Gavin Shan
2013-06-27 5:46 ` [PATCH 2/8] powerpc/eeh: Check PCIe link after reset Gavin Shan
2013-06-27 5:46 ` [PATCH 3/8] powerpc/powernv: Replace variables with flags Gavin Shan
2013-06-27 5:46 ` [PATCH 4/8] powerpc/eeh: Fix address catch for PowerNV Gavin Shan
2013-06-27 5:46 ` [PATCH 5/8] powerpc/eeh: Refactor the output message Gavin Shan
2013-06-27 5:46 ` [PATCH 6/8] powerpc/eeh: Avoid build warnings Gavin Shan
2013-06-27 5:46 ` [PATCH 7/8] powerpc/powernv: Use dev-node in PCI config accessors Gavin Shan
2013-06-27 5:46 ` [PATCH 8/8] powernv/eeh: Do hotplug on devices without EEH aware driver Gavin Shan
2013-06-30 6:25 ` Benjamin Herrenschmidt
2013-06-27 5:51 ` 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='20130627055103.GA14126@shangw.(null)' \
--to=shangw@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).