diff options
| author | Chris Wilson <[email protected]> | 2020-02-27 08:57:05 +0000 |
|---|---|---|
| committer | Chris Wilson <[email protected]> | 2020-02-28 14:05:33 +0000 |
| commit | a5af081d012e8b0ede5b1ef59a9c143067b45af6 (patch) | |
| tree | 520b3f037771a07abaf350e2455a2cdae3a45cf0 /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 6875eb3ff5a37b73cd59bb6dcb6828ade1f62e66 (diff) | |
drm/i915/perf: Mark up the racy use of perf->exclusive_stream
Inside the general i915_oa_init_reg_state() we avoid using the
perf->mutex. However, we rely on perf->exclusive_stream being valid to
access at that point, and for that we have to control the race with
disabling perf. This relies on the disabling being a heavy barrier that
inspects all active contexts, after marking the perf->exclusive_stream
as not available. This should ensure that there are no more concurrent
accesses to the perf->exclusive_stream as we destroy it.
Mark up the races around the perf->exclusive_stream so that they stand
out much more. (And hopefully we will be running kcsan to start
validating that the only races we have are carefully controlled.)
Signed-off-by: Chris Wilson <[email protected]>
Cc: Lionel Landwerlin <[email protected]>
Reviewed-by: Mika Kuoppala <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions