From: Russell Currey <ruscur@russell.cc>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/3] powerpc/eeh: Enhancement to EEH for VF
Date: Wed, 02 Mar 2016 12:04:42 +1100 [thread overview]
Message-ID: <1456880682.4528.5.camel@russell.cc> (raw)
In-Reply-To: <1456445092-18337-1-git-send-email-gwshan@linux.vnet.ibm.com>
On Fri, 2016-02-26 at 11:04 +1100, Gavin Shan wrote:
> 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
>
> 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(-)
>
For the whole series (incorporating my comments on patch 3):
Reviewed-by: Russell Currey <ruscur@russell.cc>
prev parent reply other threads:[~2016-03-02 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 0:04 [PATCH 0/3] powerpc/eeh: Enhancement to EEH for VF Gavin Shan
2016-02-26 0:04 ` [PATCH 1/3] powerpc/eeh: Don't propagate error to guest Gavin Shan
2016-02-26 0:04 ` [PATCH 2/3] powerpc/eeh: Don't remove passed VFs Gavin Shan
2016-02-26 0:04 ` [PATCH 3/3] powerpc/eeh: Synchronize recovery in host/guest Gavin Shan
2016-03-02 1:03 ` Russell Currey
2016-03-02 2:13 ` Gavin Shan
2016-03-02 1:04 ` Russell Currey [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=1456880682.4528.5.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=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).