From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, Gavin Shan <shangw@linux.vnet.ibm.com>
Subject: Re: [PATCH v1 00/22] powerpc/eeh: Enhance converting EEH dev
Date: Wed, 15 May 2013 13:30:49 +0800 [thread overview]
Message-ID: <20130515053049.GA28780@shangw.(null)> (raw)
In-Reply-To: <1368590264.31689.69.camel@pasglop>
On Wed, May 15, 2013 at 01:57:44PM +1000, Benjamin Herrenschmidt wrote:
>On Wed, 2013-05-15 at 11:34 +0800, Gavin Shan wrote:
>> e don't have existing utility (e.g. errinjct) to test the patchset. In order
>> to conduct the test, you need copy over the eeh-debug.c to PowerNV platform
>> directory and change the makefile accordingly. Please contact me to get the
>> eeh-debug.c if you want run the test case. After that, you need write P7IOC
>> registers explicitly to trigger frozen PE or fenced PHB explicitly as the
>> following example shows. The patchset has been verified on Firebird-L machine
>> where I have 2 Emulex ethernet card on PHB#6. I keep pinging to one of the
>> ethernet cards from external and then use following commands to produce frozen
>> PE or fenced PHB errors. Eventually, the errors can be recovered and the ethernet
>> card is reachable after temporary connection lost.
>
>There is an error injection framework we can use nowadays, or maybe you can
>put this in tools/powerpc ?
>
Ben, we don't have error injection framework yet. I have one source file "eeh-debug.c"
which exports P7IOC registers through procfs. In order to force EEH errors (frozen PE
or fenced PHB), we need change the specific bits of corresponding HW registers through
the procfs entries (e.g. /proc/IODA/PHBx/REG).
Thanks,
Gavin
next prev parent reply other threads:[~2013-05-15 5:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 3:34 [PATCH v1 00/22] powerpc/eeh: Enhance converting EEH dev Gavin Shan
2013-05-15 3:34 ` [PATCH 01/22] " Gavin Shan
2013-05-15 3:34 ` [PATCH 02/22] powerpc/eeh: Function to tranverse PCI devices Gavin Shan
2013-05-15 3:34 ` [PATCH 03/22] powerpc/eeh: Make eeh_phb_pe_get() public Gavin Shan
2013-05-15 3:34 ` [PATCH 04/22] powerpc/eeh: Make eeh_pe_get() public Gavin Shan
2013-05-15 3:34 ` [PATCH 05/22] powerpc/eeh: Trace PCI bus from PE Gavin Shan
2013-05-15 3:34 ` [PATCH 06/22] powerpc/eeh: Make eeh_init() public Gavin Shan
2013-05-15 3:34 ` [PATCH 07/22] powerpc/eeh: EEH post initialization operation Gavin Shan
2013-05-15 3:34 ` [PATCH 08/22] powerpc/eeh: Refactor eeh_reset_pe_once() Gavin Shan
2013-05-15 3:34 ` [PATCH 09/22] powerpc/eeh: Delay EEH probe during hotplug Gavin Shan
2013-05-15 3:34 ` [PATCH 10/22] powerpc/eeh: Differentiate EEH events Gavin Shan
2013-05-15 3:34 ` [PATCH 11/22] powerpc/eeh: Sync OPAL API with firmware Gavin Shan
2013-05-15 3:34 ` [PATCH 12/22] powerpc/eeh: EEH backend for P7IOC Gavin Shan
2013-05-15 3:34 ` [PATCH 13/22] powerpc/eeh: I/O chip post initialization Gavin Shan
2013-05-15 3:34 ` [PATCH 14/22] powerpc/eeh: I/O chip EEH enable option Gavin Shan
2013-05-15 3:34 ` [PATCH 15/22] powerpc/eeh: I/O chip EEH state retrieval Gavin Shan
2013-05-15 3:34 ` [PATCH 16/22] powerpc/eeh: I/O chip PE reset Gavin Shan
2013-05-15 3:34 ` [PATCH 17/22] powerpc/eeh: I/O chip PE log and bridge setup Gavin Shan
2013-05-15 3:34 ` [PATCH 18/22] powerpc/eeh: PowerNV EEH backends Gavin Shan
2013-05-15 3:34 ` [PATCH 19/22] powerpc/eeh: Initialization for PowerNV Gavin Shan
2013-05-15 3:34 ` [PATCH 20/22] powerpc/eeh: Enable EEH check for config access Gavin Shan
2013-05-15 3:34 ` [PATCH 21/22] powerpc/eeh: Process interrupts caused by EEH Gavin Shan
2013-05-15 3:34 ` [PATCH 22/22] powerpc/eeh: Connect EEH error interrupt handle Gavin Shan
2013-05-15 3:57 ` [PATCH v1 00/22] powerpc/eeh: Enhance converting EEH dev Benjamin Herrenschmidt
2013-05-15 5:30 ` Gavin Shan [this message]
2013-05-15 5:58 ` Benjamin Herrenschmidt
2013-05-15 8:47 ` Gavin Shan
2013-05-15 9:48 ` Benjamin Herrenschmidt
2013-05-16 2:44 ` 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='20130515053049.GA28780@shangw.(null)' \
--to=shangw@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--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).