From: David Miller <davem@davemloft.net>
To: michal.kalderon@cavium.com
Cc: ariel.elior@cavium.com, netdev@vger.kernel.org, natechancellor@gmail.com
Subject: Re: [PATCH v2 net-next 0/3] qed*: Error recovery process
Date: Mon, 28 Jan 2019 10:58:56 -0800 (PST) [thread overview]
Message-ID: <20190128.105856.425508372742746977.davem@davemloft.net> (raw)
In-Reply-To: <20190128172756.27361-1-michal.kalderon@cavium.com>
From: Michal Kalderon <michal.kalderon@cavium.com>
Date: Mon, 28 Jan 2019 19:27:53 +0200
> Parity errors might happen in the device's memories due to momentary bit
> flips which are caused by radiation.
> Errors that are not correctable initiate a process kill event, which blocks
> the device access towards the host and the network, and a recovery process
> is started in the management FW and in the driver.
>
> This series adds the support of this process in the qed core module and in
> the qede driver (patches 2 & 3).
> Patch 1 in the series revises the load sequence, to avoid PCI errors that
> might be observed during a recovery process.
>
> Changes in v2:
> - Addressed issue found in https://patchwork.ozlabs.org/patch/1030545/
> The change was done be removing the enum and passing a boolean to
> the related functions.
Series applied to net-next, thanks.
prev parent reply other threads:[~2019-01-28 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 17:27 [PATCH v2 net-next 0/3] qed*: Error recovery process Michal Kalderon
2019-01-28 17:27 ` [PATCH v2 net-next 1/3] qed: Revise load sequence to avoid PCI errors Michal Kalderon
2019-01-28 17:27 ` [PATCH v2 net-next 2/3] qed: Add infrastructure for error detection and recovery Michal Kalderon
2019-01-28 17:27 ` [PATCH v2 net-next 3/3] qede: Error recovery process Michal Kalderon
2019-01-28 18:58 ` David Miller [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=20190128.105856.425508372742746977.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariel.elior@cavium.com \
--cc=michal.kalderon@cavium.com \
--cc=natechancellor@gmail.com \
--cc=netdev@vger.kernel.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).