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: nirmoy.das@intel.com, farah.kassabri@intel.com,
	michal.wajdeczko@intel.com
Subject: Re: [PATCH v2 03/11] drm/xe: s/tlb_invalidation.lock/tlb_invalidation.fence_lock
Date: Tue, 9 Jul 2024 17:57:44 +0200	[thread overview]
Message-ID: <f838e080-7c3f-4f45-9e06-b5dcfc3f1461@linux.intel.com> (raw)
In-Reply-To: <20240708040331.766264-4-matthew.brost@intel.com>


On 7/8/2024 6:03 AM, Matthew Brost wrote:
> tlb_invalidation.lock is the lock for GT TLB invalidation fences, name
> this accurately.
>
> 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 | 8 ++++----
>   drivers/gpu/drm/xe/xe_gt_types.h            | 4 ++--
>   2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> index 687214d07ac7..147840b66ba9 100644
> --- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> +++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
> @@ -80,7 +80,7 @@ int xe_gt_tlb_invalidation_init(struct xe_gt *gt)
>   	gt->tlb_invalidation.seqno = 1;
>   	INIT_LIST_HEAD(&gt->tlb_invalidation.pending_fences);
>   	spin_lock_init(&gt->tlb_invalidation.pending_lock);
> -	spin_lock_init(&gt->tlb_invalidation.lock);
> +	spin_lock_init(&gt->tlb_invalidation.fence_lock);
>   	INIT_DELAYED_WORK(&gt->tlb_invalidation.fence_tdr,
>   			  xe_gt_tlb_fence_timeout);
>   
> @@ -491,11 +491,11 @@ static const struct dma_fence_ops invalidation_fence_ops = {
>   void xe_gt_tlb_invalidation_fence_init(struct xe_gt *gt,
>   				       struct xe_gt_tlb_invalidation_fence *fence)
>   {
> -	spin_lock_irq(&gt->tlb_invalidation.lock);
> +	spin_lock_irq(&gt->tlb_invalidation.fence_lock);
>   	dma_fence_init(&fence->base, &invalidation_fence_ops,
> -		       &gt->tlb_invalidation.lock,
> +		       &gt->tlb_invalidation.fence_lock,
>   		       dma_fence_context_alloc(1), 1);
> -	spin_unlock_irq(&gt->tlb_invalidation.lock);
> +	spin_unlock_irq(&gt->tlb_invalidation.fence_lock);
>   	INIT_LIST_HEAD(&fence->link);
>   	dma_fence_get(&fence->base);
>   }
> diff --git a/drivers/gpu/drm/xe/xe_gt_types.h b/drivers/gpu/drm/xe/xe_gt_types.h
> index 6b5e0b45efb0..d190a66514c0 100644
> --- a/drivers/gpu/drm/xe/xe_gt_types.h
> +++ b/drivers/gpu/drm/xe/xe_gt_types.h
> @@ -192,8 +192,8 @@ struct xe_gt {
>   		 * xe_gt_tlb_fence_timeout after the timeut interval is over.
>   		 */
>   		struct delayed_work fence_tdr;
> -		/** @tlb_invalidation.lock: protects TLB invalidation fences */
> -		spinlock_t lock;
> +		/** @tlb_invalidation.fence_lock: protects TLB invalidation fences */
> +		spinlock_t fence_lock;
>   	} tlb_invalidation;
>   
>   	/**

  reply	other threads:[~2024-07-09 15:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08  4:03 [PATCH v2 00/11] Proper GT TLB invalidation layering and new coalescing feature Matthew Brost
2024-07-08  4:03 ` [PATCH v2 01/11] drm/xe: Add xe_gt_tlb_invalidation_fence_init helper Matthew Brost
2024-07-09 15:56   ` Nirmoy Das
2024-07-08  4:03 ` [PATCH v2 02/11] drm/xe: Drop xe_gt_tlb_invalidation_wait Matthew Brost
2024-07-09 15:57   ` Nirmoy Das
2024-07-08  4:03 ` [PATCH v2 03/11] drm/xe: s/tlb_invalidation.lock/tlb_invalidation.fence_lock Matthew Brost
2024-07-09 15:57   ` Nirmoy Das [this message]
2024-07-08  4:03 ` [PATCH v2 04/11] drm/xe: Add tlb_invalidation.seqno_lock Matthew Brost
2024-07-08  4:03 ` [PATCH v2 05/11] drm/xe: Add xe_gt_tlb_invalidation_done_handler Matthew Brost
2025-07-23 17:22   ` Summers, Stuart
2024-07-08  4:03 ` [PATCH v2 06/11] drm/xe: Add send tlb invalidation helpers Matthew Brost
2024-07-08  4:03 ` [PATCH v2 07/11] drm/xe: Add xe_guc_tlb_invalidation layer Matthew Brost
2024-07-09 21:31   ` Michal Wajdeczko
2024-07-10  4:02     ` Matthew Brost
2024-07-08  4:03 ` [PATCH v2 08/11] drm/xe: Add multi-client support for GT TLB invalidations Matthew Brost
2024-07-08  4:03 ` [PATCH v2 09/11] drm/xe: Add GT TLB invalidation coalescing Matthew Brost
2024-07-08  4:03 ` [PATCH v2 10/11] drm/xe: Add GT TLB invalidation coalesce tracepoints Matthew Brost
2024-07-08  4:03 ` [PATCH v2 11/11] drm/xe: Add GT TLB invalidation watermark debugfs Matthew Brost
2024-07-08  4:08 ` ✓ CI.Patch_applied: success for Proper GT TLB invalidation layering and new coalescing feature. (rev2) Patchwork
2024-07-08  4:09 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-08  4:10 ` ✓ CI.KUnit: success " Patchwork
2024-07-08  4:22 ` ✓ CI.Build: " Patchwork
2024-07-08  4:24 ` ✓ CI.Hooks: " Patchwork
2024-07-08  4:25 ` ✓ CI.checksparse: " Patchwork
2024-07-08  4:51 ` ✓ CI.BAT: " Patchwork
2024-07-08  5:46 ` ✗ CI.FULL: failure " Patchwork
2024-07-09  9:57 ` [PATCH v2 00/11] Proper GT TLB invalidation layering and new coalescing feature Matthew Auld
2024-07-09 16:08   ` Nirmoy Das
2024-07-09 16:35     ` Matthew Brost
2024-07-09 16:42       ` Nirmoy Das
2024-07-09 21:23         ` Matthew Brost
2024-07-09 16:31   ` Matthew Brost

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=f838e080-7c3f-4f45-9e06-b5dcfc3f1461@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=farah.kassabri@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --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