From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: [PATCH 2/4] drm/xe: Move TLB invalidation reset before HW reset
Date: Thu, 28 Dec 2023 20:35:05 -0800 [thread overview]
Message-ID: <20231229043507.1002411-3-matthew.brost@intel.com> (raw)
In-Reply-To: <20231229043507.1002411-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>
---
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 3af2adec1295..c647f41b2751 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
next prev parent reply other threads:[~2023-12-29 4:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 4:35 [PATCH 0/4] GuC CT tweaks Matthew Brost
2023-12-29 4:35 ` [PATCH 1/4] drm/xe/guc: Add more GuC CT states Matthew Brost
2023-12-29 23:36 ` Michal Wajdeczko
2024-01-02 16:52 ` Matthew Brost
2023-12-29 4:35 ` Matthew Brost [this message]
2023-12-29 4:35 ` [PATCH 3/4] drm/xe/guc: Protect queuing of G2H handler with fast lock Matthew Brost
2023-12-29 4:35 ` [PATCH 4/4] drm/xe/guc: Flush G2H handler when turning off CTs Matthew Brost
2024-01-04 4:03 ` ✓ CI.Patch_applied: success for GuC CT tweaks Patchwork
2024-01-04 4:03 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-04 4:04 ` ✓ CI.KUnit: success " Patchwork
2024-01-04 4:11 ` ✓ CI.Build: " Patchwork
2024-01-04 4:12 ` ✓ CI.Hooks: " Patchwork
2024-01-04 4:13 ` ✓ CI.checksparse: " Patchwork
2024-01-04 4:48 ` ✓ CI.BAT: " 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=20231229043507.1002411-3-matthew.brost@intel.com \
--to=matthew.brost@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