diff options
| author | Feras Daoud | 2018-12-02 13:41:22 +0100 |
|---|---|---|
| committer | Saeed Mahameed | 2019-06-13 22:23:17 +0200 |
| commit | 1ef6f1a17e56f9126472d2c50818f468f1fc43d2 (patch) | |
| tree | 8c6b27e64c0cba03e9eb3e65af1711535ccab94e /include/linux/mlx5/device.h | |
| parent | net/mlx5: Handle SW reset of FW in error flow (diff) | |
| download | kernel-qcow2-linux-1ef6f1a17e56f9126472d2c50818f468f1fc43d2.tar.gz kernel-qcow2-linux-1ef6f1a17e56f9126472d2c50818f468f1fc43d2.tar.xz kernel-qcow2-linux-1ef6f1a17e56f9126472d2c50818f468f1fc43d2.zip | |
net/mlx5: Control CR-space access by different PFs
Since the FW can be shared between different PFs/VFs it is common
that more than one health poll will detected a failure, this can
lead to multiple resets which are unneeded.
The solution is to use a FW locking mechanism using semaphore space
to provide a way to allow only one device to collect the cr-dump and
to issue a sw-reset.
Signed-off-by: Feras Daoud <ferasda@mellanox.com>
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
Diffstat (limited to 'include/linux/mlx5/device.h')
0 files changed, 0 insertions, 0 deletions