diff options
author | 2025-08-25 17:34:28 +0300 | |
---|---|---|
committer | 2025-08-26 18:00:26 -0700 | |
commit | 34cc6a54914f478c93e176450fae6313404f9f74 (patch) | |
tree | 9587e7843a4229d51950781a9aed9b39b431a283 /tools/perf/scripts/python | |
parent | net/mlx5: HWS, Fix pattern destruction in mlx5hws_pat_get_pattern error path (diff) | |
download | wireguard-linux-34cc6a54914f478c93e176450fae6313404f9f74.tar.xz wireguard-linux-34cc6a54914f478c93e176450fae6313404f9f74.zip |
net/mlx5: Reload auxiliary drivers on fw_activate
The devlink reload fw_activate command performs firmware activation
followed by driver reload, while devlink reload driver_reinit triggers
only driver reload. However, the driver reload logic differs between the
two modes, as on driver_reinit mode mlx5 also reloads auxiliary drivers,
while in fw_activate mode the auxiliary drivers are suspended where
applicable.
Additionally, following the cited commit, if the device has multiple PFs,
the behavior during fw_activate may vary between PFs: one PF may suspend
auxiliary drivers, while another reloads them.
Align devlink dev reload fw_activate behavior with devlink dev reload
driver_reinit, to reload all auxiliary drivers.
Fixes: 72ed5d5624af ("net/mlx5: Suspend auxiliary devices only in case of PCI device suspend")
Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
Reviewed-by: Akiva Goldberger <agoldberger@nvidia.com>
Signed-off-by: Mark Bloch <mbloch@nvidia.com>
Link: https://patch.msgid.link/20250825143435.598584-6-mbloch@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions