From: wenxiong <wenxiong@linux.vnet.ibm.com>
To: wenxiong@linux.vnet.ibm.com
Cc: linux-nvme@lists.infradead.org, keith.busch@intel.com,
axboe@fb.com, linux-kernel@vger.kernel.org, wenxiong@us.ibm.com
Subject: Re: [PATCH V3] nvme-pci: Fixes EEH failure on ppc
Date: Wed, 28 Feb 2018 16:31:37 -0600 [thread overview]
Message-ID: <bf3a386a2b82dac84b681c14d5334632@linux.vnet.ibm.com> (raw)
In-Reply-To: <1518725110-25894-1-git-send-email-wenxiong@linux.vnet.ibm.com>
On 2018-02-15 14:05, wenxiong@linux.vnet.ibm.com wrote:
> From: Wen Xiong <wenxiong@linux.vnet.ibm.com>
>
> With b2a0eb1a0ac72869c910a79d935a0b049ec78ad9(nvme-pci: Remove watchdog
> timer), EEH recovery stops working on ppc.
>
> After removing whatdog timer routine, when trigger EEH on ppc, we hit
> EEH in nvme_timeout(). We would like to check if pci channel is offline
> or not at the beginning of nvme_timeout(), if it is already offline,
> we don't need to do future nvme timeout process.
>
> Add mrmory barrier before calling pci_channel_offline().
>
> With the patch, EEH recovery works successfuly on ppc.
>
> Signed-off-by: Wen Xiong <wenxiong@linux.vnet.ibm.com>
Hi Keith and All,
We have the newer Linux distro releases came out recently, so I got more
reports for this issue.
Test teams have verified the patch in several distro kernel
version(v4.14, v4.15).
If you have any question about the V3 patch I submitted two weeks, Let
me know.
Thanks,
Wendy
next prev parent reply other threads:[~2018-02-28 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 20:05 [PATCH V3] nvme-pci: Fixes EEH failure on ppc wenxiong
2018-02-28 22:31 ` wenxiong [this message]
2018-02-28 23:55 ` Keith Busch
[not found] ` <OFB428CB19.833F7B7C-ON00258243.005E4D59-86258243.005E7EAB@notes.na.collabserv.com>
2018-03-01 17:16 ` Keith Busch
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=bf3a386a2b82dac84b681c14d5334632@linux.vnet.ibm.com \
--to=wenxiong@linux.vnet.ibm.com \
--cc=axboe@fb.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=wenxiong@us.ibm.com \
/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).