summaryrefslogtreecommitdiff
path: root/include/acpi
diff options
context:
space:
mode:
authorJacob Keller <jacob.e.keller@intel.com>2023-02-22 20:09:10 +0300
committerTony Nguyen <anthony.l.nguyen@intel.com>2023-03-13 20:32:32 +0300
commit8cd8a6b17d275a45e3722d0215f6115b687c8c3e (patch)
treec448845ca4beb11c5184a14aa3479da28ce7a2eb /include/acpi
parente4eaf8938852d092fa447b32adb8ec233621d86a (diff)
downloadlinux-8cd8a6b17d275a45e3722d0215f6115b687c8c3e.tar.xz
ice: move VF overflow message count into struct ice_mbx_vf_info
The ice driver has some logic in ice_vf_mbx.c used to detect potentially malicious VF behavior with regards to overflowing the PF mailbox. This logic currently stores message counts in struct ice_mbx_vf_counter.vf_cntr as an array. This array is allocated during initialization with ice_mbx_init_snapshot. This logic makes sense for SR-IOV where all VFs are allocated at once up front. However, in the future with Scalable IOV this logic will not work. VFs can be added and removed dynamically. We could try to keep the vf_cntr array for the maximum possible number of VFs, but this is a waste of memory. Use the recently introduced struct ice_mbx_vf_info structure to store the message count. Pass a pointer to the mbx_info for a VF instead of using its VF ID. Replace the array of VF message counts with a linked list that tracks all currently active mailbox tracking info structures. Signed-off-by: Jacob Keller <jacob.e.keller@intel.com> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com> Tested-by: Marek Szlosek <marek.szlosek@intel.com> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Diffstat (limited to 'include/acpi')
0 files changed, 0 insertions, 0 deletions