diff options
author | David Herrmann <dh.herrmann@gmail.com> | 2013-10-02 10:15:17 +0200 |
---|---|---|
committer | Dave Airlie <airlied@redhat.com> | 2013-10-09 14:37:55 +1000 |
commit | 55fb74adc628b99424360b0123f47ea4484c56fd (patch) | |
tree | 3c8b51cc6047af2a59a40989e18c4844afa0a23e /drivers/gpu/drm/cirrus | |
parent | 51bbd276015661a28b69450e104632bc2b633311 (diff) | |
download | op-kernel-dev-55fb74adc628b99424360b0123f47ea4484c56fd.zip op-kernel-dev-55fb74adc628b99424360b0123f47ea4484c56fd.tar.gz |
drm/nouveau: embed gem object in nouveau_bo
There is no reason to keep the gem object separately allocated. nouveau is
the last user of gem_obj->driver_private, so if we embed it, we can get
rid of 8bytes per gem-object.
The implementation follows the radeon driver. bo->gem is only valid, iff
the bo was created via the gem helpers _and_ iff the user holds a valid
gem reference. That is, as the gem object holds a reference to the
nouveau_bo. If you use nouveau_ref() to gain a bo reference, you are not
guaranteed to also hold a gem reference. The gem object might get
destroyed after the last user drops the gem-ref via
drm_gem_object_unreference(). Use drm_gem_object_reference() to gain a
gem-reference.
For debugging, we can use bo->gem.filp != NULL to test whether a gem-bo is
valid. However, this shouldn't be used for real functionality to avoid
gem-internal dependencies.
Note that the implementation follows the previous style. However, we no
longer can check for bo->gem != NULL to test for a valid gem object. This
wasn't done before, so we should be safe now.
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Acked-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Reviewed-by: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/cirrus')
0 files changed, 0 insertions, 0 deletions