[Intel-gfx] [PATCH 1/1] drm/i915: track pid of GEM object creators

Eric Anholt eric at anholt.net
Fri Feb 3 10:57:38 CET 2012

On Thu,  2 Feb 2012 14:52:22 -0200, Eugeni Dodonov <eugeni.dodonov at intel.com> wrote:
> This allows to hopefully find out who was responsible for the GPU death.
> To simplify post-portem analysis, we also search for the the processes
> names when gathering the i915_error_state and when peeking at the list of
> active gem objects in debugfs.

I think just recording pid at create as opposed to the last exec would
be fine -- my DRI2 buffers are charged to the X Server, my 3D client
buffers are always charged to it, and batchbuffers are always the client
that execced it because they're not shared.

I've definitely wanted this in the debug info, and written a hack like
this (but worse) before.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20120203/b3d4649a/attachment.sig>

More information about the Intel-gfx mailing list