From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: [PATCH 2/4] drm/xe: Include additional info on failed force-wake operation
Date: Mon, 10 Jun 2024 20:37:55 +0200 [thread overview]
Message-ID: <20240610183757.1812-3-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20240610183757.1812-1-michal.wajdeczko@intel.com>
For debug purposes it might be useful to look at the values of the
force-wake ack registers in case wake/sleep operations failures.
Move xe_gt_notice() from the caller to the helper function, where
we have the latest value of force-wake ack register available.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/xe/xe_force_wake.c | 35 ++++++++++++++++++++----------
1 file changed, 23 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_force_wake.c b/drivers/gpu/drm/xe/xe_force_wake.c
index 2497f0f65aa0..a1d97cce3d56 100644
--- a/drivers/gpu/drm/xe/xe_force_wake.c
+++ b/drivers/gpu/drm/xe/xe_force_wake.c
@@ -102,9 +102,17 @@ static void domain_wake(struct xe_gt *gt, struct xe_force_wake_domain *domain)
static int domain_wake_wait(struct xe_gt *gt,
struct xe_force_wake_domain *domain)
{
- return xe_mmio_wait32(gt, domain->reg_ack, domain->val, domain->val,
- XE_FORCE_WAKE_ACK_TIMEOUT_MS * USEC_PER_MSEC,
- NULL, true);
+ u32 value;
+ int ret;
+
+ ret = xe_mmio_wait32(gt, domain->reg_ack, domain->val, domain->val,
+ XE_FORCE_WAKE_ACK_TIMEOUT_MS * USEC_PER_MSEC,
+ &value, true);
+ if (ret)
+ xe_gt_notice(gt, "Force wake domain %d failed to ack wake (%pe) reg[%#x] = %#x\n",
+ domain->id, ERR_PTR(ret), domain->reg_ack.addr, value);
+
+ return ret;
}
static void domain_sleep(struct xe_gt *gt, struct xe_force_wake_domain *domain)
@@ -115,9 +123,18 @@ static void domain_sleep(struct xe_gt *gt, struct xe_force_wake_domain *domain)
static int domain_sleep_wait(struct xe_gt *gt,
struct xe_force_wake_domain *domain)
{
- return xe_mmio_wait32(gt, domain->reg_ack, domain->val, 0,
- XE_FORCE_WAKE_ACK_TIMEOUT_MS * USEC_PER_MSEC,
- NULL, true);
+ u32 value;
+ int ret;
+
+ ret = xe_mmio_wait32(gt, domain->reg_ack, domain->val, 0,
+ XE_FORCE_WAKE_ACK_TIMEOUT_MS * USEC_PER_MSEC,
+ &value, true);
+
+ if (ret)
+ xe_gt_notice(gt, "Force wake domain %d failed to ack sleep (%pe) reg[%#x] = %#x\n",
+ domain->id, ERR_PTR(ret), domain->reg_ack.addr, value);
+
+ return ret;
}
#define for_each_fw_domain_masked(domain__, mask__, fw__, tmp__) \
@@ -145,9 +162,6 @@ int xe_force_wake_get(struct xe_force_wake *fw,
for_each_fw_domain_masked(domain, woken, fw, tmp) {
ret = domain_wake_wait(gt, domain);
ret2 |= ret;
- if (ret)
- xe_gt_notice(gt, "Force wake domain (%d) failed to ack wake, ret=%d\n",
- domain->id, ret);
}
fw->awake_domains |= woken;
spin_unlock_irqrestore(&fw->lock, flags);
@@ -174,9 +188,6 @@ int xe_force_wake_put(struct xe_force_wake *fw,
for_each_fw_domain_masked(domain, sleep, fw, tmp) {
ret = domain_sleep_wait(gt, domain);
ret2 |= ret;
- if (ret)
- xe_gt_notice(gt, "Force wake domain (%d) failed to ack sleep, ret=%d\n",
- domain->id, ret);
}
fw->awake_domains &= ~sleep;
spin_unlock_irqrestore(&fw->lock, flags);
--
2.43.0
next prev parent reply other threads:[~2024-06-10 18:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 18:37 [PATCH 0/4] Prepare Xe force-wake code for VFs Michal Wajdeczko
2024-06-10 18:37 ` [PATCH 1/4] drm/xe: Prefer GT oriented messages in xe_force_wake.c Michal Wajdeczko
2024-06-10 19:44 ` Rodrigo Vivi
2024-06-10 18:37 ` Michal Wajdeczko [this message]
2024-06-10 19:47 ` [PATCH 2/4] drm/xe: Include additional info on failed force-wake operation Rodrigo Vivi
2024-06-10 18:37 ` [PATCH 3/4] drm/xe: Combine common force-wake code into helpers Michal Wajdeczko
2024-06-10 19:51 ` Rodrigo Vivi
2024-06-10 18:37 ` [PATCH 4/4] drm/xe/vf: Ignore force-wake requests if VF Michal Wajdeczko
2024-06-10 19:51 ` Rodrigo Vivi
2024-06-10 18:54 ` ✓ CI.Patch_applied: success for Prepare Xe force-wake code for VFs Patchwork
2024-06-10 18:54 ` ✓ CI.checkpatch: " Patchwork
2024-06-10 18:55 ` ✓ CI.KUnit: " Patchwork
2024-06-10 19:07 ` ✓ CI.Build: " Patchwork
2024-06-10 19:09 ` ✓ CI.Hooks: " Patchwork
2024-06-10 19:10 ` ✓ CI.checksparse: " Patchwork
2024-06-11 6:09 ` ✓ CI.Patch_applied: success for Prepare Xe force-wake code for VFs (rev2) Patchwork
2024-06-11 6:09 ` ✓ CI.checkpatch: " Patchwork
2024-06-11 6:10 ` ✓ CI.KUnit: " Patchwork
2024-06-11 6:22 ` ✓ CI.Build: " Patchwork
2024-06-11 6:24 ` ✗ CI.Hooks: failure " Patchwork
2024-06-11 6:25 ` ✓ CI.checksparse: success " Patchwork
2024-06-11 7:08 ` ✓ CI.BAT: " Patchwork
2024-06-11 8:45 ` ✓ CI.FULL: " 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=20240610183757.1812-3-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@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