Searched hist:331815 (Results 1 - 6 of 6) sorted by relevance
/freebsd-11-stable/sys/modules/mlx5/ | ||
H A D | Makefile | diff 331815 Fri Mar 30 19:33:43 MDT 2018 hselasky MFC r331452: Add mutual exclusion mechanism for software reset of firmware in mlx5core. Since the FW can be shared between PCI functions it is common that more than one health poll will detected a failure, this can lead to multiple resets. The solution is to use a FW locking mechanism using semaphore space to provide a way to synchronize between functions. The FW semaphore is acquired via config cycle access. First the VSEC gateway must be acquired, then the semaphore can be locked by writing a value to it and confirmed it's locked by reading the same value back. The process in the same to free the semaphore, except the value written should be zero. Submitted by: slavash@ Sponsored by: Mellanox Technologies |
/freebsd-11-stable/sys/dev/mlx5/mlx5_core/ | ||
H A D | mlx5_core.h | diff 331815 Fri Mar 30 19:33:43 MDT 2018 hselasky MFC r331452: Add mutual exclusion mechanism for software reset of firmware in mlx5core. Since the FW can be shared between PCI functions it is common that more than one health poll will detected a failure, this can lead to multiple resets. The solution is to use a FW locking mechanism using semaphore space to provide a way to synchronize between functions. The FW semaphore is acquired via config cycle access. First the VSEC gateway must be acquired, then the semaphore can be locked by writing a value to it and confirmed it's locked by reading the same value back. The process in the same to free the semaphore, except the value written should be zero. Submitted by: slavash@ Sponsored by: Mellanox Technologies |
H A D | mlx5_health.c | diff 331815 Fri Mar 30 19:33:43 MDT 2018 hselasky MFC r331452: Add mutual exclusion mechanism for software reset of firmware in mlx5core. Since the FW can be shared between PCI functions it is common that more than one health poll will detected a failure, this can lead to multiple resets. The solution is to use a FW locking mechanism using semaphore space to provide a way to synchronize between functions. The FW semaphore is acquired via config cycle access. First the VSEC gateway must be acquired, then the semaphore can be locked by writing a value to it and confirmed it's locked by reading the same value back. The process in the same to free the semaphore, except the value written should be zero. Submitted by: slavash@ Sponsored by: Mellanox Technologies |
H A D | mlx5_main.c | diff 331815 Fri Mar 30 19:33:43 MDT 2018 hselasky MFC r331452: Add mutual exclusion mechanism for software reset of firmware in mlx5core. Since the FW can be shared between PCI functions it is common that more than one health poll will detected a failure, this can lead to multiple resets. The solution is to use a FW locking mechanism using semaphore space to provide a way to synchronize between functions. The FW semaphore is acquired via config cycle access. First the VSEC gateway must be acquired, then the semaphore can be locked by writing a value to it and confirmed it's locked by reading the same value back. The process in the same to free the semaphore, except the value written should be zero. Submitted by: slavash@ Sponsored by: Mellanox Technologies |
/freebsd-11-stable/sys/dev/mlx5/ | ||
H A D | driver.h | diff 331815 Fri Mar 30 19:33:43 MDT 2018 hselasky MFC r331452: Add mutual exclusion mechanism for software reset of firmware in mlx5core. Since the FW can be shared between PCI functions it is common that more than one health poll will detected a failure, this can lead to multiple resets. The solution is to use a FW locking mechanism using semaphore space to provide a way to synchronize between functions. The FW semaphore is acquired via config cycle access. First the VSEC gateway must be acquired, then the semaphore can be locked by writing a value to it and confirmed it's locked by reading the same value back. The process in the same to free the semaphore, except the value written should be zero. Submitted by: slavash@ Sponsored by: Mellanox Technologies |
/freebsd-11-stable/sys/conf/ | ||
H A D | files | diff 331815 Fri Mar 30 19:33:43 MDT 2018 hselasky MFC r331452: Add mutual exclusion mechanism for software reset of firmware in mlx5core. Since the FW can be shared between PCI functions it is common that more than one health poll will detected a failure, this can lead to multiple resets. The solution is to use a FW locking mechanism using semaphore space to provide a way to synchronize between functions. The FW semaphore is acquired via config cycle access. First the VSEC gateway must be acquired, then the semaphore can be locked by writing a value to it and confirmed it's locked by reading the same value back. The process in the same to free the semaphore, except the value written should be zero. Submitted by: slavash@ Sponsored by: Mellanox Technologies |
Completed in 156 milliseconds