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

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>

diff --git a/drivers/net/ethernet/mellanox/mlx5/core/diag/crdump.c b/drivers/net/ethernet/mellanox/mlx5/core/diag/crdump.c
index 28d02749d3c4059365a8ecf8aea9bcf7f6215e31..7659ad21e6e5adae004f39b8f4561b860fe49457 100644 (file)
--- a/drivers/net/ethernet/mellanox/mlx5/core/diag/crdump.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/diag/crdump.c
@@ -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;
        }