diff options
| author | Chris Wilson | 2016-10-12 13:48:27 +0200 |
|---|---|---|
| committer | Chris Wilson | 2016-10-12 17:27:14 +0200 |
| commit | 8baa1f04b9ed8afe8d2d9f3884b335b1bab984d0 (patch) | |
| tree | c3f7529de887f8f71cd425812be4a662878b4a6e /drivers/gpu/drm/drm_platform.c | |
| parent | drm/i915: Use fence_write() from rpm resume (diff) | |
| download | kernel-qcow2-linux-8baa1f04b9ed8afe8d2d9f3884b335b1bab984d0.tar.gz kernel-qcow2-linux-8baa1f04b9ed8afe8d2d9f3884b335b1bab984d0.tar.xz kernel-qcow2-linux-8baa1f04b9ed8afe8d2d9f3884b335b1bab984d0.zip | |
drm/i915: Update debugfs describe_obj() to show fault-mappable
The current meaning of whether an object has a GGTT vma is very
ill-defined (and note we don't check for any partials either), it just
means that at some point it was in the GGTT but it may not be now. The
information we really care about here is whether it is taking up
precious mappable aperture space. This is the obj->fault_mappable flag.
We have a redundant long form reprinting of this information, so remove
that in favour of the compact flag.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20161012114827.17031-2-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/drm_platform.c')
0 files changed, 0 insertions, 0 deletions