diff options
| author | Akeem G Abodunrin <akeem.g.abodunrin@intel.com> | 2019-11-08 06:23:22 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-12-31 16:45:46 +0100 |
| commit | b533200b40334bd86caa737b0ff033ecc391d071 (patch) | |
| tree | 998a23142e38e1ba60ebed83c0b36e493b79d76c /kernel/workqueue_internal.h | |
| parent | 44d40114eecb7b3269258bed65d50bd4d2ce2aef (diff) | |
ice: Only disable VF state when freeing each VF resources
[ Upstream commit 1f9639d2fb9188a59acafae9dea626391c442a8d ]
It is wrong to set PF disable state flag for all VFs when freeing VF
resources - Instead, we should set VF disable state flag for each VF with
its resources being returned to the device. Right now, all VF opcodes,
mailbox communication to clear its resources as well fails - since we
already indicate that PF is in disable state, with all VFs not active. In
addition, we don't need to notify VF that PF is intending to reset it, if
it is already in disabled state.
Signed-off-by: Akeem G Abodunrin <akeem.g.abodunrin@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'kernel/workqueue_internal.h')
0 files changed, 0 insertions, 0 deletions