Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Cc: dan.carpenter@linaro.org
Subject: Re: [PATCH] drm/xe: Remove fence check from send_tlb_invalidation
Date: Wed, 24 Jul 2024 10:33:20 +0200	[thread overview]
Message-ID: <1119d480-49bc-498c-8f75-a6c3f63a5438@linux.intel.com> (raw)
In-Reply-To: <20240723190714.1744653-1-matthew.brost@intel.com>


On 7/23/2024 9:07 PM, Matthew Brost wrote:
> 'fence' argument in send_tlb_invalidation cannot be NULL, remove
> non-NULL check from send_tlb_invalidation.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Closes: https://lore.kernel.org/r/202407231049.esig0Fkb-lkp@intel.com/
> Fixes: 61ac035361ae ("drm/xe: Drop xe_gt_tlb_invalidation_wait")
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>


> ---
>   drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> index 481d83d07367..87cb76a8718c 100644
> --- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> +++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> @@ -182,7 +182,7 @@ static int send_tlb_invalidation(struct xe_guc *guc,
>   	action[1] = seqno;
>   	ret = xe_guc_ct_send_locked(&guc->ct, action, len,
>   				    G2H_LEN_DW_TLB_INVALIDATE, 1);
> -	if (!ret && fence) {
> +	if (!ret) {
>   		spin_lock_irq(&gt->tlb_invalidation.pending_lock);
>   		/*
>   		 * We haven't actually published the TLB fence as per
> @@ -203,7 +203,7 @@ static int send_tlb_invalidation(struct xe_guc *guc,
>   						   tlb_timeout_jiffies(gt));
>   		}
>   		spin_unlock_irq(&gt->tlb_invalidation.pending_lock);
> -	} else if (ret < 0 && fence) {
> +	} else if (ret < 0) {
>   		__invalidation_fence_signal(xe, fence);
>   	}
>   	if (!ret) {

      parent reply	other threads:[~2024-07-24  8:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 19:07 [PATCH] drm/xe: Remove fence check from send_tlb_invalidation Matthew Brost
2024-07-23 19:12 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-23 19:12 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-23 19:13 ` ✓ CI.KUnit: success " Patchwork
2024-07-23 19:25 ` ✓ CI.Build: " Patchwork
2024-07-23 19:27 ` ✓ CI.Hooks: " Patchwork
2024-07-23 19:29 ` ✓ CI.checksparse: " Patchwork
2024-07-23 20:11 ` ✓ CI.BAT: " Patchwork
2024-07-23 21:09 ` ✗ CI.FULL: failure " Patchwork
2024-07-24  9:16   ` Nirmoy Das
2024-07-24  8:33 ` Nirmoy Das [this message]

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=1119d480-49bc-498c-8f75-a6c3f63a5438@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=dan.carpenter@linaro.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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