From: Thomas Hellstrom <thellstrom@vmware.com>
To: Maarten Lankhorst <m.b.lankhorst@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 02/10] drm/ttm: remove ttm_bo_cleanup_memtype_use
Date: Mon, 19 Nov 2012 14:26:10 +0100 [thread overview]
Message-ID: <50AA3372.1070004@vmware.com> (raw)
In-Reply-To: <1352728811-21860-2-git-send-email-maarten.lankhorst@canonical.com>
Hi,
On 11/12/2012 03:00 PM, Maarten Lankhorst wrote:
> move to release_list instead
Can you describe why this change is made? cleanup? reorder locks in a
later patch?
Also please describe why you need move_notify and ttm unbind / destroy
to be outside of
reservation, because that's the main change in this patch and it's not
even mentioned in the
commit message.
Thanks,
Thomas
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
> ---
> drivers/gpu/drm/ttm/ttm_bo.c | 47 +++++++++++++-------------------------------
> 1 file changed, 14 insertions(+), 33 deletions(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index 9c48e8f..74d6e7c 100644
> --- a/drivers/gpu/drm/ttm/ttm_bo.c
> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> @@ -143,12 +143,20 @@ static void ttm_bo_release_list(struct kref *list_kref)
> BUG_ON(atomic_read(&bo->kref.refcount));
> BUG_ON(atomic_read(&bo->cpu_writers));
> BUG_ON(bo->sync_obj != NULL);
> - BUG_ON(bo->mem.mm_node != NULL);
> BUG_ON(!list_empty(&bo->lru));
> BUG_ON(!list_empty(&bo->ddestroy));
>
> - if (bo->ttm)
> + if (bo->bdev->driver->move_notify)
> + bo->bdev->driver->move_notify(bo, NULL);
> +
> + if (bo->ttm) {
> + ttm_tt_unbind(bo->ttm);
> ttm_tt_destroy(bo->ttm);
> + bo->ttm = NULL;
> + }
> + ttm_bo_mem_put(bo, &bo->mem);
> + BUG_ON(bo->mem.mm_node != NULL);
> +
> atomic_dec(&bo->glob->bo_count);
> if (bo->destroy)
> bo->destroy(bo);
> @@ -466,35 +474,6 @@ out_err:
> return ret;
> }
>
> -/**
> - * Call bo::reserved.
> - * Will release GPU memory type usage on destruction.
> - * This is the place to put in driver specific hooks to release
> - * driver private resources.
> - * Will release the bo::reserved lock.
> - */
> -
> -static void ttm_bo_cleanup_memtype_use(struct ttm_buffer_object *bo)
> -{
> - if (bo->bdev->driver->move_notify)
> - bo->bdev->driver->move_notify(bo, NULL);
> -
> - if (bo->ttm) {
> - ttm_tt_unbind(bo->ttm);
> - ttm_tt_destroy(bo->ttm);
> - bo->ttm = NULL;
> - }
> - ttm_bo_mem_put(bo, &bo->mem);
> -
> - atomic_set(&bo->reserved, 0);
> -
> - /*
> - * Make processes trying to reserve really pick it up.
> - */
> - smp_mb__after_atomic_dec();
> - wake_up_all(&bo->event_queue);
> -}
> -
> static void ttm_bo_cleanup_refs_or_queue(struct ttm_buffer_object *bo)
> {
> struct ttm_bo_device *bdev = bo->bdev;
> @@ -523,8 +502,9 @@ static void ttm_bo_cleanup_refs_or_queue(struct ttm_buffer_object *bo)
> spin_unlock(&bdev->fence_lock);
> put_count = ttm_bo_del_from_lru(bo);
>
> + atomic_set(&bo->reserved, 0);
> + wake_up_all(&bo->event_queue);
> spin_unlock(&glob->lru_lock);
> - ttm_bo_cleanup_memtype_use(bo);
>
> ttm_bo_list_ref_sub(bo, put_count, true);
>
> @@ -619,8 +599,9 @@ retry_reserve:
> list_del_init(&bo->ddestroy);
> ++put_count;
>
> + atomic_set(&bo->reserved, 0);
> + wake_up_all(&bo->event_queue);
> spin_unlock(&glob->lru_lock);
> - ttm_bo_cleanup_memtype_use(bo);
>
> ttm_bo_list_ref_sub(bo, put_count, true);
>
next prev parent reply other threads:[~2012-11-19 13:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 14:00 [PATCH 01/10] drm/radeon: allow move_notify to be called without reservation Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 02/10] drm/ttm: remove ttm_bo_cleanup_memtype_use Maarten Lankhorst
2012-11-19 13:26 ` Thomas Hellstrom [this message]
2012-11-19 14:03 ` Maarten Lankhorst
2012-11-19 14:12 ` Thomas Hellstrom
2012-11-12 14:00 ` [PATCH 03/10] drm/ttm: do not check if list is empty in ttm_bo_force_list_clean Maarten Lankhorst
2012-11-19 13:33 ` Thomas Hellstrom
2012-11-19 14:10 ` Maarten Lankhorst
2012-11-20 7:42 ` Thomas Hellstrom
2012-11-12 14:00 ` [PATCH 04/10] drm/ttm: change fence_lock to inner lock, v3 Maarten Lankhorst
2012-11-19 14:17 ` Thomas Hellstrom
2012-11-19 15:04 ` Thomas Hellstrom
2012-11-19 15:33 ` Maarten Lankhorst
2012-11-20 7:48 ` Thomas Hellstrom
2012-11-20 11:33 ` Maarten Lankhorst
2012-11-20 11:59 ` Maarten Lankhorst
2012-11-20 12:03 ` Thomas Hellstrom
2012-11-20 13:13 ` Maarten Lankhorst
2012-11-20 15:08 ` Thomas Hellstrom
2012-11-21 11:38 ` Maarten Lankhorst
2012-11-21 12:42 ` Thomas Hellstrom
2012-11-21 13:12 ` Maarten Lankhorst
2012-11-21 13:27 ` Thomas Hellstrom
2012-11-22 15:51 ` Maarten Lankhorst
2012-11-22 20:29 ` Thomas Hellstrom
2012-11-27 12:35 ` Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 05/10] drm/ttm: add sense to ttm_bo_cleanup_refs, v4 Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 06/10] drm/ttm: remove no_wait_reserve, v2 Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 07/10] drm/ttm: cope with reserved buffers on swap list in ttm_bo_swapout Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 08/10] drm/ttm: cope with reserved buffers on lru list in ttm_mem_evict_first Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 09/10] drm/ttm: remove lru_lock around ttm_bo_reserve Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 10/10] drm/ttm: remove reliance on ttm_bo_wait_unreserved Maarten Lankhorst
2012-11-12 14:03 ` [PATCH 01/10] drm/radeon: allow move_notify to be called without reservation Maarten Lankhorst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50AA3372.1070004@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=m.b.lankhorst@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox