drm/sman: rip out owner tracking
authorDaniel Vetter <daniel.vetter@ffwll.ch>
Wed, 26 Oct 2011 20:28:07 +0000 (22:28 +0200)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Wed, 21 Dec 2011 23:33:20 +0000 (00:33 +0100)
commit763240deb423c477b4d46c23e0b582099d4b8753
tree724f804e38eb00a23f6d1e3ca4b50ec89d1e9208
parentaa38e2e01521f88e9b0230c0236d2bd89d0af0ed
drm/sman: rip out owner tracking

In contrast to kms drivers, sis/via _always_ associated a buffer with
a drm fd. So by the time we reach lastclose, all open drm fds are gone
and with them their associated objects.

So when sis/via call drm_sman_cleanup in their lastclose funcs, that
will free 0 objects.

The owner tracking now serves no purpose at all, hence rip it ou. We
can't kill the corresponding fields in struct drm_memblock_item yet
because we hijack these in the new driver private owner tracking. But
now that drm_sman.c doesn't touch ->owner_list anymore, we need to
kill the list_move hack and properly add the item to the file_priv
list.

Also leave the list_del(&obj->owner_list) in drm_sman_free for the
moment, it will move to the drivers when sman disappears completely.

v2: Remove the redundant INIT_LIST_HEAD as noted by Chris Wilson

Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
drivers/gpu/drm/drm_sman.c
drivers/gpu/drm/sis/sis_mm.c
drivers/gpu/drm/via/via_mm.c
include/drm/drm_sman.h
This page took 0.027375 seconds and 5 git commands to generate.