summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/i915_debugfs.c
diff options
context:
space:
mode:
authorChris Wilson2017-10-13 22:26:16 +0200
committerChris Wilson2017-10-16 21:44:19 +0200
commit3d574a6bbb12a6c3bbeea807a1724b44a0f6ebbb (patch)
tree03aab19734eab1742c772553d93c71c759609ced /drivers/gpu/drm/i915/i915_debugfs.c
parentdrm/i915: Drop debugfs/i915_gem_pin_display (diff)
downloadkernel-qcow2-linux-3d574a6bbb12a6c3bbeea807a1724b44a0f6ebbb.tar.gz
kernel-qcow2-linux-3d574a6bbb12a6c3bbeea807a1724b44a0f6ebbb.tar.xz
kernel-qcow2-linux-3d574a6bbb12a6c3bbeea807a1724b44a0f6ebbb.zip
drm/i915: Remove walk over obj->vma_list for the shrinker
In the next patch, we want to reduce the lock coverage within the shrinker, and one of the dangerous walks we have is over obj->vma_list. We are only walking the obj->vma_list in order to check whether it has been permanently pinned by HW access, typically via use on the scanout. But we have a couple of other long term pins, the context objects for which we currently have to check the individual vma pin_count. If we instead mark these using obj->pin_display, we can forgo the dangerous and sometimes slow list iteration. v2: Rearrange code to try and avoid confusion from false associations due to arrangement of whitespace along with rebasing on obj->pin_global. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20171013202621.7276-4-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/i915_debugfs.c')
0 files changed, 0 insertions, 0 deletions