aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorMichel Thierry <michel.thierry@intel.com>2014-08-06 15:04:44 +0200
committerDaniel Vetter <daniel.vetter@ffwll.ch>2014-08-12 15:22:26 +0200
commitb9d06dd9d1dd3672b391e6387d62aa8dc4e377bd (patch)
tree3d9185f91583b1f061d5744d17d9f6c25f485025 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentdrm/i915/bdw: Always use MMIO flips with Execlists (diff)
downloadlinux-dev-b9d06dd9d1dd3672b391e6387d62aa8dc4e377bd.tar.xz
linux-dev-b9d06dd9d1dd3672b391e6387d62aa8dc4e377bd.zip
drm/i915: vma/ppgtt lifetime rules
VMAs should take a reference of the address space they use. Now, when the fd is closed, it will release the ref that the context was holding, but it will still be referenced by any vmas that are still active. ppgtt_release() should then only be called when the last thing referencing it releases the ref, and it can just call the base cleanup and free the ppgtt. Note that with this we will extend the lifetime of ppgtts which contain shared objects. But all the non-shared objects will get removed as soon as they drop of the active list and for the shared ones the shrinker can eventually reap them. Since we currently can't evict ppgtt pagetables either I don't think that temporary leak is important. Signed-off-by: Michel Thierry <michel.thierry@intel.com> [danvet: Add note about potential ppgtt leak with this approach.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions