Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>, rodrigo.vivi@intel.com
Subject: [PATCH v3 2/3] drm/xe: Move TLB invalidation reset before HW reset
Date: Thu, 18 Jan 2024 11:24:41 -0800	[thread overview]
Message-ID: <20240118192442.1480073-3-matthew.brost@intel.com> (raw)
In-Reply-To: <20240118192442.1480073-1-matthew.brost@intel.com>

This is a software reset which can be done immediately after stopping
the UC.

Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
 drivers/gpu/drm/xe/xe_gt.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_gt.c b/drivers/gpu/drm/xe/xe_gt.c
index 0f2258dc4a00..c19fe0c02961 100644
--- a/drivers/gpu/drm/xe/xe_gt.c
+++ b/drivers/gpu/drm/xe/xe_gt.c
@@ -619,12 +619,12 @@ static int gt_reset(struct xe_gt *gt)
 	if (err)
 		goto err_out;
 
+	xe_gt_tlb_invalidation_reset(gt);
+
 	err = do_gt_reset(gt);
 	if (err)
 		goto err_out;
 
-	xe_gt_tlb_invalidation_reset(gt);
-
 	err = do_gt_restart(gt);
 	if (err)
 		goto err_out;
-- 
2.34.1


  parent reply	other threads:[~2024-01-18 19:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 19:24 [PATCH v3 0/3] GuC CT tweaks Matthew Brost
2024-01-18 19:24 ` [PATCH v3 1/3] drm/xe/guc: Add more GuC CT states Matthew Brost
2024-01-18 22:22   ` Michal Wajdeczko
2024-01-19 20:36     ` Matthew Brost
2024-01-18 19:24 ` Matthew Brost [this message]
2024-01-18 19:24 ` [PATCH v3 3/3] drm/xe/guc: Flush G2H handler when turning off CTs Matthew Brost
2024-01-18 20:02 ` ✓ CI.Patch_applied: success for GuC CT tweaks (rev3) Patchwork
2024-01-18 20:02 ` ✓ CI.checkpatch: " Patchwork
2024-01-18 20:03 ` ✓ CI.KUnit: " Patchwork
2024-01-18 20:10 ` ✓ CI.Build: " Patchwork
2024-01-18 20:10 ` ✓ CI.Hooks: " Patchwork
2024-01-18 20:12 ` ✓ CI.checksparse: " Patchwork
2024-01-18 20:32 ` ✗ CI.BAT: failure " 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=20240118192442.1480073-3-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@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