dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sinclair Yeh" <syeh@vmware.com>
To: "Christian König" <deathsimple@vodafone.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm/ttm: don't wait for BO on initial allocation
Date: Wed, 6 Apr 2016 09:06:34 -0700	[thread overview]
Message-ID: <20160406160634.GA23620@syeh-linux> (raw)
In-Reply-To: <1459933928-4663-2-git-send-email-deathsimple@vodafone.de>

I don't know much about AMD gpu.  Patches 1-6 look good to me.


On Wed, Apr 06, 2016 at 11:12:02AM +0200, Christian König wrote:
> From: Christian König <christian.koenig@amd.com>
> 
> When we use an extern reservation object that otherwise waits for every
> fence registered with it.
> 
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> ---
>  drivers/gpu/drm/ttm/ttm_bo.c | 18 ++++++++++++------
>  1 file changed, 12 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index 4cbf265..367b87b 100644
> --- a/drivers/gpu/drm/ttm/ttm_bo.c
> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> @@ -998,13 +998,19 @@ static int ttm_bo_move_buffer(struct ttm_buffer_object *bo,
>  	lockdep_assert_held(&bo->resv->lock.base);
>  
>  	/*
> -	 * FIXME: It's possible to pipeline buffer moves.
> -	 * Have the driver move function wait for idle when necessary,
> -	 * instead of doing it here.
> +	 * Don't wait for the BO on initial allocation. This is important when
> +	 * the BO has an imported reservation object.
>  	 */
> -	ret = ttm_bo_wait(bo, false, interruptible, no_wait_gpu);
> -	if (ret)
> -		return ret;
> +	if (bo->mem.mem_type != TTM_PL_SYSTEM || bo->ttm != NULL) {
> +		/*
> +		 * FIXME: It's possible to pipeline buffer moves.
> +		 * Have the driver move function wait for idle when necessary,
> +		 * instead of doing it here.
> +		 */
> +		ret = ttm_bo_wait(bo, false, interruptible, no_wait_gpu);
> +		if (ret)
> +			return ret;
> +	}
>  	mem.num_pages = bo->num_pages;
>  	mem.size = mem.num_pages << PAGE_SHIFT;
>  	mem.page_alignment = bo->mem.page_alignment;
> -- 
> 2.5.0
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-04-06 16:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  9:12 RFC: Some TTM patches Christian König
2016-04-06  9:12 ` [PATCH 1/7] drm/ttm: don't wait for BO on initial allocation Christian König
2016-04-06 16:06   ` Sinclair Yeh [this message]
2016-04-13 17:38     ` Christian König
2016-04-13 17:51       ` Sinclair Yeh
2016-04-06  9:12 ` [PATCH 2/7] drm/ttm: remove use_ticket parameter from ttm_bo_reserve Christian König
2016-04-06  9:12 ` [PATCH 3/7] drm/ttm: remove lazy parameter from ttm_bo_wait Christian König
2016-04-06  9:12 ` [PATCH 4/7] drm/ttm: remove unused validation sequence Christian König
2016-04-06  9:12 ` [PATCH 5/7] drm/ttm: add optional LRU removal callback v2 Christian König
2016-04-06  9:12 ` [PATCH 6/7] drm/ttm: implement LRU add callbacks v2 Christian König
2016-04-06  9:12 ` [PATCH 7/7] drm/amdgpu: prefer VM page tables over normal BOs Christian König

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=20160406160634.GA23620@syeh-linux \
    --to=syeh@vmware.com \
    --cc=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    /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