Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Check empty pinned BO list with lock held.
Date: Tue, 28 May 2024 20:56:05 +0000	[thread overview]
Message-ID: <ZlZE5Sf4ambwtrIo@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240528115408.22094-1-nirmoy.das@intel.com>

On Tue, May 28, 2024 at 01:54:08PM +0200, Nirmoy Das wrote:
> Use lock that is meant to use for accessing the BO pin list.
> 
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>

Agree with this patch removing removing micro optimization of bypassing
&xe->pinned.lock, we should avoid thing like this.

Curious if this was an actual problem (i.e. was their a bug report which
lead to this change)?

Anyways the patch LGTM. With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_bo.c | 10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index 03f7fe7acf8c..2bae01ce4e5b 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -1758,11 +1758,10 @@ void xe_bo_unpin_external(struct xe_bo *bo)
>  	xe_assert(xe, xe_bo_is_pinned(bo));
>  	xe_assert(xe, xe_bo_is_user(bo));
>  
> -	if (bo->ttm.pin_count == 1 && !list_empty(&bo->pinned_link)) {
> -		spin_lock(&xe->pinned.lock);
> +	spin_lock(&xe->pinned.lock);
> +	if (bo->ttm.pin_count == 1 && !list_empty(&bo->pinned_link))
>  		list_del_init(&bo->pinned_link);
> -		spin_unlock(&xe->pinned.lock);
> -	}
> +	spin_unlock(&xe->pinned.lock);
>  
>  	ttm_bo_unpin(&bo->ttm);
>  
> @@ -1785,9 +1784,8 @@ void xe_bo_unpin(struct xe_bo *bo)
>  		struct ttm_place *place = &(bo->placements[0]);
>  
>  		if (mem_type_is_vram(place->mem_type)) {
> -			xe_assert(xe, !list_empty(&bo->pinned_link));
> -
>  			spin_lock(&xe->pinned.lock);
> +			xe_assert(xe, !list_empty(&bo->pinned_link));
>  			list_del_init(&bo->pinned_link);
>  			spin_unlock(&xe->pinned.lock);
>  		}
> -- 
> 2.42.0
> 

  parent reply	other threads:[~2024-05-28 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 11:54 [PATCH] drm/xe: Check empty pinned BO list with lock held Nirmoy Das
2024-05-28 12:14 ` ✓ CI.Patch_applied: success for " Patchwork
2024-05-28 12:14 ` ✓ CI.checkpatch: " Patchwork
2024-05-28 12:15 ` ✗ CI.KUnit: failure " Patchwork
2024-05-28 20:56 ` Matthew Brost [this message]
2024-05-29  8:35   ` [PATCH] " Nirmoy Das
2024-05-29  9:12 ` ✗ CI.Patch_applied: failure for drm/xe: Check empty pinned BO list with lock held. (rev2) Patchwork

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=ZlZE5Sf4ambwtrIo@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=nirmoy.das@intel.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