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/5] powerpc: EEH fixes
Date: Sun, 17 Aug 2014 13:02:24 +1000 [thread overview]
Message-ID: <1408244549-10221-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
The series of patches is to fix recursive EEH error during recovery
for VFIO-PCI except some cleanup. The recursive EEH error is caused
by MMIO access when the PE is under reset or the PCI device isn't
enabled yet. The solution is to freeze the PE until the PCI device
is enabled after PE reset.
Another issue is that one specific PE is frozen when being passed
through. It caused the device can't work properly in userland (e.g.
QEMU). The fix is to clear the frozen state when passing PE to
userland.
Gavin Shan (5):
powerpc/eeh: Drop unused argument in eeh_check_failure()
powerpc/eeh: Add eeh_pe_state sysfs entry
powerpc/eeh: Freeze PE before PE reset
powerpc/eeh: Reenable PCI devices after reset
powerpc/eeh: Clear frozen state on passing device
arch/powerpc/include/asm/eeh.h | 30 +++----
arch/powerpc/kernel/eeh.c | 116 +++++++++++++++++++++------
arch/powerpc/kernel/eeh_sysfs.c | 61 +++++++++++++-
arch/powerpc/platforms/powernv/eeh-ioda.c | 43 +++++++---
arch/powerpc/platforms/pseries/eeh_pseries.c | 4 +-
5 files changed, 203 insertions(+), 51 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-08-17 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 3:02 Gavin Shan [this message]
2014-08-17 3:02 ` [PATCH 1/5] powerpc/eeh: Drop unused argument in eeh_check_failure() Gavin Shan
2014-08-17 3:02 ` [PATCH 2/5] powerpc/eeh: Add eeh_pe_state sysfs entry Gavin Shan
2014-09-25 4:09 ` [2/5] " Michael Ellerman
2014-09-25 4:47 ` Gavin Shan
2014-08-17 3:02 ` [PATCH 3/5] powerpc/eeh: Freeze PE before PE reset Gavin Shan
2014-08-17 3:02 ` [PATCH 4/5] powerpc/eeh: Reenable PCI devices after reset Gavin Shan
2014-08-17 3:02 ` [PATCH 5/5] powerpc/eeh: Clear frozen state on passing device 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=1408244549-10221-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).