diff options
| author | Maarten Lankhorst <[email protected]> | 2021-03-23 16:50:14 +0100 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2021-03-24 17:27:20 +0100 |
| commit | 7d1c2618eac590d948eb33b9807d913ddb6e105f (patch) | |
| tree | c661f7d8bba3220389075a0baf262b88b46ee7e0 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 2a66596838592a69c3c463d06c19bee51ed15a3d (diff) | |
drm/i915: Take reservation lock around i915_vma_pin.
We previously complained when ww == NULL.
This function is now only used in selftests to pin an object,
and ww locking is now fixed.
Signed-off-by: Maarten Lankhorst <[email protected]>
Reviewed-by: Thomas Hellström <[email protected]>
[danvet: Resolve conflict because we don't have a set-domain refactor,
see
https://lore.kernel.org/intel-gfx/[email protected]/
The really worrying thing here is that the above patch had a change in
arguments for i915_gem_object_set_to_gtt_domain(), without any
explanation. I decided to just faithfully apply Maarten's change but
not the argument change which was in Maarten's context diff.]
Signed-off-by: Daniel Vetter <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions