drm/i915: Add a tracepoint for the shrinker
authorChris Wilson <chris@chris-wilson.co.uk>
Thu, 1 Oct 2015 11:18:26 +0000 (12:18 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Wed, 7 Oct 2015 14:05:38 +0000 (16:05 +0200)
commit3abafa539d2c17d46df3f47b35eb784fdf3020a1
tree751ea6d6485daaf248c374abb0398af4b2a770a5
parentcb422619976f3f1b71f68f0c1b5a764e9f90fb0c
drm/i915: Add a tracepoint for the shrinker

Often it is very useful to know why we suddenly purge vast tracts of
memory and surprisingly up until now we didn't even have a tracepoint
for when we shrink our memory.

Note that there are slab_start/end tracepoints already, but those
don't cover the internal recursion when we directly call into our
shrinker code. Hence a separate tracepoint seems justified. Also note
that we don't really need a separate tracepoint for the actual amount
of pages freed since we already have an unbind tracpoint for that.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
[danvet: Add a note that there's also slab_start/end and why they're
insufficient.]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/gpu/drm/i915/i915_gem_shrinker.c
drivers/gpu/drm/i915/i915_trace.h