From: Shannon Nelson <shannon.nelson@amd.com>
To: <netdev@vger.kernel.org>, <davem@davemloft.net>,
<kuba@kernel.org>, <idosch@idosch.org>
Cc: <brett.creeley@amd.com>, <drivers@pensando.io>,
Shannon Nelson <shannon.nelson@amd.com>
Subject: [PATCH v2 net-next 0/5] ionic: add FLR support
Date: Thu, 13 Jul 2023 12:29:31 -0700 [thread overview]
Message-ID: <20230713192936.45152-1-shannon.nelson@amd.com> (raw)
Add support for handing and recovering from a PCI FLR event.
This patchset first moves some code around to make it usable
from multiple paths, then adds the PCI error handler callbacks
for reset_prepare and reset_done.
Example test:
echo 1 > /sys/bus/pci/devices/0000:2a:00.0/reset
v2:
- removed redundant pci_save/restore_state() calls
Shannon Nelson (5):
ionic: remove dead device fail path
ionic: extract common bits from ionic_remove
ionic: extract common bits from ionic_probe
ionic: pull out common bits from fw_up
ionic: add FLR recovery support
.../ethernet/pensando/ionic/ionic_bus_pci.c | 167 ++++++++++++------
.../net/ethernet/pensando/ionic/ionic_lif.c | 72 +++++---
.../net/ethernet/pensando/ionic/ionic_lif.h | 5 +
3 files changed, 165 insertions(+), 79 deletions(-)
--
2.17.1
next reply other threads:[~2023-07-13 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 19:29 Shannon Nelson [this message]
2023-07-13 19:29 ` [PATCH v2 net-next 1/5] ionic: remove dead device fail path Shannon Nelson
2023-07-14 2:57 ` Jakub Kicinski
2023-07-14 4:38 ` Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 2/5] ionic: extract common bits from ionic_remove Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 3/5] ionic: extract common bits from ionic_probe Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 4/5] ionic: pull out common bits from fw_up Shannon Nelson
2023-07-13 19:29 ` [PATCH v2 net-next 5/5] ionic: add FLR recovery support Shannon Nelson
2023-07-14 2:21 ` [PATCH v2 net-next 0/5] ionic: add FLR support patchwork-bot+netdevbpf
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=20230713192936.45152-1-shannon.nelson@amd.com \
--to=shannon.nelson@amd.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--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).