TWxSoftware/twx-linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

net/mlx5: print change on SW reset semaphore returns busy

Browse Source 
While collecting crdump as part of fw_fatal health reporter dump the PF
may fail to lock the SW reset semaphore. Change the print to indicate if
it was due to another PF locked the semaphore already and so trying to
lock the semaphore returned -EBUSY.

Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
Reviewed-by: Shay Drory <shayd@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
This commit is contained in:
Moshe Shemesh
2023-09-06 12:18:05 +03:00
committed by Saeed Mahameed
parent e316dd1cf1
commit 7b2bfd4ebf
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
drivers/net/ethernet/mellanox/mlx5/core/diag/crdump.c
+4 -1
View File
@@ -55,7 +55,10 @@ int mlx5_crdump_collect(struct mlx5_core_dev *dev, u32 *cr_data)
ret = mlx5_vsc_sem_set_space(dev, MLX5_SEMAPHORE_SW_RESET,
MLX5_VSC_LOCK);
if (ret) {
mlx5_core_warn(dev, "Failed to lock SW reset semaphore\n");
if (ret == -EBUSY)
mlx5_core_info(dev, "SW reset semaphore is already in use\n");
else
mlx5_core_warn(dev, "Failed to lock SW reset semaphore\n");
goto unlock_gw;
}