Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH v6 02/11] drm/xe/tlb: ensure we access seqno_recv once
Date: Mon, 10 Jul 2023 10:40:40 +0100	[thread overview]
Message-ID: <20230710094037.28179-15-matthew.auld@intel.com> (raw)
In-Reply-To: <20230710094037.28179-13-matthew.auld@intel.com>

Ensure we load gt->tlb_invalidation.seqno_recv once, and use that for
our seqno checking. The gt->tlb_invalidation_seqno_past is a shared
global variable and can potentially change at any point here.  However
the checks here need to operate on a stable version of seqno_recv for
this to make any sense.

Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 12 ++++++------
 1 file 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 08432f472e2d..c67abc67d9fc 100644
--- a/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
+++ b/drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c
@@ -257,15 +257,15 @@ int xe_gt_tlb_invalidation_vma(struct xe_gt *gt,
 
 static bool tlb_invalidation_seqno_past(struct xe_gt *gt, int seqno)
 {
-	if (seqno - gt->tlb_invalidation.seqno_recv <
-	    -(TLB_INVALIDATION_SEQNO_MAX / 2))
+	int seqno_recv = READ_ONCE(gt->tlb_invalidation.seqno_recv);
+
+	if (seqno - seqno_recv < -(TLB_INVALIDATION_SEQNO_MAX / 2))
 		return false;
 
-	if (seqno - gt->tlb_invalidation.seqno_recv >
-	    (TLB_INVALIDATION_SEQNO_MAX / 2))
+	if (seqno - seqno_recv > (TLB_INVALIDATION_SEQNO_MAX / 2))
 		return true;
 
-	return gt->tlb_invalidation.seqno_recv >= seqno;
+	return seqno_recv >= seqno;
 }
 
 /**
@@ -337,7 +337,7 @@ int xe_guc_tlb_invalidation_done_handler(struct xe_guc *guc, u32 *msg, u32 len)
 	 * wake_up_all() and wait_event_timeout() already have the correct
 	 * barriers.
 	 */
-	gt->tlb_invalidation.seqno_recv = msg[0];
+	WRITE_ONCE(gt->tlb_invalidation.seqno_recv, msg[0]);
 	wake_up_all(&guc->ct.wq);
 
 	fence = list_first_entry_or_null(&gt->tlb_invalidation.pending_fences,
-- 
2.41.0


  parent reply	other threads:[~2023-07-10  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  9:40 [Intel-xe] [PATCH v6 00/11] Try to handle TLB invalidations from CT fast-path Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 01/11] drm/xe/tlb: drop unnecessary smp_wmb() Matthew Auld
2023-07-10  9:40 ` Matthew Auld [this message]
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 03/11] drm/xe: hold mem_access.ref for CT fast-path Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 04/11] drm/xe/ct: hold fast_lock when reserving space for g2h Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 05/11] drm/xe/tlb: increment next seqno after successful CT send Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 06/11] drm/xe/ct: serialise fast_lock during CT disable Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 07/11] drm/xe/gt: tweak placement for signalling TLB fences after GT reset Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 08/11] drm/xe/tlb: also update seqno_recv during reset Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 09/11] drm/xe/tlb: print seqno_recv on fence TLB timeout Matthew Auld
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 10/11] drm/xe/ct: update g2h outstanding for CTB capture Matthew Auld
2023-07-10 13:42   ` Matthew Brost
2023-07-10  9:40 ` [Intel-xe] [PATCH v6 11/11] drm/xe: handle TLB invalidations from CT fast-path Matthew Auld
2023-07-10 10:13 ` [Intel-xe] ✓ CI.Patch_applied: success for Try to handle TLB invalidations from CT fast-path (rev4) Patchwork
2023-07-10 10:13 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-10 10:15 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-10 10:19 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-10 10:19 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-10 10:20 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-10 11:06 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-07-10 14:41 ` [Intel-xe] [PATCH v6 00/11] Try to handle TLB invalidations from CT fast-path Souza, Jose

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=20230710094037.28179-15-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@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