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 v3 3/5] drm/xe/gt: tweak placement for signalling TLB fences after GT reset
Date: Tue,  4 Jul 2023 14:45:28 +0100	[thread overview]
Message-ID: <20230704134524.138377-10-matthew.auld@intel.com> (raw)
In-Reply-To: <20230704134524.138377-7-matthew.auld@intel.com>

Assumption here is that submission is disabled along with CT, and full
GT reset will also nuke TLBs, so should be safe to signal all in-flight
TLB fences, but only after the actual reset so move the placement
slightly.

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>
---
 drivers/gpu/drm/xe/xe_gt.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/xe/xe_gt.c b/drivers/gpu/drm/xe/xe_gt.c
index bc76678a8276..a21d44bfe9e8 100644
--- a/drivers/gpu/drm/xe/xe_gt.c
+++ b/drivers/gpu/drm/xe/xe_gt.c
@@ -519,7 +519,6 @@ static int gt_reset(struct xe_gt *gt)
 
 	xe_uc_stop_prepare(&gt->uc);
 	xe_gt_pagefault_reset(gt);
-	xe_gt_tlb_invalidation_reset(gt);
 
 	err = xe_uc_stop(&gt->uc);
 	if (err)
@@ -529,6 +528,8 @@ static int gt_reset(struct xe_gt *gt)
 	if (err)
 		goto err_out;
 
+	xe_gt_tlb_invalidation_reset(gt);
+
 	err = do_gt_restart(gt);
 	if (err)
 		goto err_out;
-- 
2.41.0


  parent reply	other threads:[~2023-07-04 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 13:45 [Intel-xe] [PATCH v3 0/5] Try to handle TLB invalidations from CT fast-path Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 1/5] drm/xe: hold mem_access.ref for " Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 2/5] drm/xe/ct: serialise fast_lock during CT disable Matthew Auld
2023-07-04 13:45 ` Matthew Auld [this message]
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 4/5] drm/xe/tlb: also update seqno_recv during reset Matthew Auld
2023-07-04 13:45 ` [Intel-xe] [PATCH v3 5/5] drm/xe: handle TLB invalidations from CT fast-path Matthew Auld
2023-07-04 13:48 ` [Intel-xe] ✓ CI.Patch_applied: success for Try to " Patchwork
2023-07-04 13:49 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-04 13:50 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-04 13:54 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-04 13:54 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-04 13:55 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-04 14:42 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-07-04 18:19 ` [Intel-xe] [PATCH v3 0/5] " Souza, Jose
2023-07-04 18:42   ` 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=20230704134524.138377-10-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