diff options
| author | Edwin Peer <edwin.peer@broadcom.com> | 2021-01-25 10:08:14 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2021-01-26 06:20:04 +0300 |
| commit | 6882c36cf82ebb210f3977be7a3a0be0c64a44cb (patch) | |
| tree | 925f7dd417c881108cac05171f2fb2d135d48a8e /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | a44daa8fcbcf572545c4c1a7908b3fbb38388048 (diff) | |
| download | linux-6882c36cf82ebb210f3977be7a3a0be0c64a44cb.tar.xz | |
bnxt_en: attempt to reinitialize after aborted reset
Drawing a hard line on aborted resets prevents a NIC open in
some scenarios that may otherwise be recoverable. For example,
if a firmware recovery happened while a PF was down and an
attempt was made to bring up an associated VF in this state,
then it was impossible to ever bring up this VF without a
rebind or reload of its driver.
Attempt to reinitialize the firmware when an aborted reset (or
failed init after a reset) is discovered during open - it may
succeed. Also take care to allow the user to retry opening the
NIC even after an aborted reset.
Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Acked-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions