From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: ruscur@russell.cc, mpe@ellerman.id.au,
Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH v2 0/3] powerpc/eeh: Enhancement to EEH for VF
Date: Wed, 2 Mar 2016 13:28:49 +1100 [thread overview]
Message-ID: <1456885732-23070-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
Those patches are based on the series of patches supporting EEH for VF,
which is pending for merging: https://patchwork.ozlabs.org/patch/581315/
This series of patches fixes couple of issue that resides in previous
patchset:
* The error handlers provided by vfio-pci driver shouldn't be called.
Otherwise, the guest is simply killed.
* When we have partially hoplug in error recovery, we shouldn't remove
those passed-through devices. Otherwise, the guest will be brought
to undefined situation.
* When we have errors detected on PF PE, hold VF PE that has been passed
through to guest until the recovery on PF PE is done
Changelog
=========
v2:
* Add Russell's comments to eeh_pe_get_state().
Gavin Shan (3):
powerpc/eeh: Don't propagate error to guest
powerpc/eeh: Don't remove passed VFs
powerpc/eeh: Synchronize recovery in host/guest
arch/powerpc/kernel/eeh.c | 11 +++++++++++
arch/powerpc/kernel/eeh_driver.c | 13 ++++++++-----
2 files changed, 19 insertions(+), 5 deletions(-)
--
2.1.0
next reply other threads:[~2016-03-02 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 2:28 Gavin Shan [this message]
2016-03-02 2:28 ` [PATCH v2 1/3] powerpc/eeh: Don't propagate error to guest Gavin Shan
2016-03-02 2:28 ` [PATCH v2 2/3] powerpc/eeh: Don't remove passed VFs Gavin Shan
2016-03-02 2:28 ` [PATCH v2 3/3] powerpc/eeh: Synchronize recovery in host/guest Gavin Shan
2016-03-02 3:03 ` [PATCH v2 0/3] powerpc/eeh: Enhancement to EEH for VF Michael Ellerman
2016-03-02 6:33 ` Gavin Shan
2016-03-04 0:01 ` Gavin Shan
2016-03-04 0:09 ` 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=1456885732-23070-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=ruscur@russell.cc \
/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).