diff options
| author | Yuval Mintz <[email protected]> | 2016-08-22 13:25:12 +0300 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2016-08-22 18:24:52 -0700 |
| commit | b0bccb69eba3629949eaa28017be56c8b1319b45 (patch) | |
| tree | a14ea846328b94de9f474ba9a65c79828087cb11 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace | |
| parent | d8c2c7e3404e5bcaeae4af78d6935e5b8fcc97ee (diff) | |
qed: Change locking scheme for VF channel
Each VF employees a lock that's supposed to serialize its usage of the
HW channel for communication with its PF, but the critical section is
ill-defined:
- VFs currently release the lock whenever the PF response arrives,
prior to actually processing the reply buffer [which was also supposed
to have been protected by same lock].
- The lock would be released on first response, ignoring the possibilty
the sw flow isn't over [as might be the case of the acquisition flow].
As a result, the flow would run unprotected and would cause a double
mutex release [as the additional message completion would release it
while its actually already free].
Change the flow to have a dedicated function to be called at end of each
flow and release the lock.
Signed-off-by: Yuval Mintz <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
0 files changed, 0 insertions, 0 deletions