From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: alex.zuo@intel.com, jonathan.cavitt@intel.com,
jani.nikula@linux.intel.com, andi.shyti@intel.com,
krzysztof.karas@intel.com
Subject: [PATCH v4] drm/i915/gt: Use poll_timeout_us in place of sliding sleep window
Date: Mon, 6 Jul 2026 23:35:10 +0800 [thread overview]
Message-ID: <20260706153510.1466259-1-jonathan.cavitt@intel.com> (raw)
The functions intel_guc_send_busy_loop and ct_send can theoretically
loop forever. In the former case, intel_guc_send_busy_loop can iterate
forever if intel_guc_send_nb repeatedly returns -EBUSY. In the latter
case, ct_send can loop forever if the guc-to-host or host-to-guc buffers
get stuck in a full state.
Rework the functions to use the poll_timeout_us family of functions
instead of calculating sleep_period_ms repeatedly. In both cases now,
if the loop condition is not met after 10 minutes, the function will
report it as a failure.
This also resolves a static analysis issue involving sleep_period_ms
overflowing after several shift-left-logical calls.
v2:
- Reduce default sleep/udelay duration (jcavitt)
v3:
- Use atomic in ct_send (jcavitt)
v4:
- Rework ct_send reimplementation to better preserve original logic
(Andi)
- Define 10 minutes to remove magic numbers (Krzysztof)
Suggested-by: Jani Nikula <jani.nikula@linux.intel.com>
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: Andi Shyti <andi.shyti@intel.com>
Cc: Krzysztof Karas <krzysztof.karas@intel.com>
---
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 33 +++++----
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 90 ++++++++++++++---------
2 files changed, 71 insertions(+), 52 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc.h b/drivers/gpu/drm/i915/gt/uc/intel_guc.h
index 053780f562c1..2d3adfbcd163 100644
--- a/drivers/gpu/drm/i915/gt/uc/intel_guc.h
+++ b/drivers/gpu/drm/i915/gt/uc/intel_guc.h
@@ -7,6 +7,7 @@
#define _INTEL_GUC_H_
#include <linux/delay.h>
+#include <linux/iopoll.h>
#include <linux/iosys-map.h>
#include <linux/xarray.h>
@@ -354,14 +355,14 @@ intel_guc_send_and_receive(struct intel_guc *guc, const u32 *action, u32 len,
response_buf, response_buf_size, 0);
}
+#define POLL_TIMEOUT_DUR (600 * USEC_PER_SEC)
static inline int intel_guc_send_busy_loop(struct intel_guc *guc,
const u32 *action,
u32 len,
u32 g2h_len_dw,
bool loop)
{
- int err;
- unsigned int sleep_period_ms = 1;
+ int err, timedout;
bool not_atomic = !in_atomic() && !irqs_disabled();
/*
@@ -374,20 +375,20 @@ static inline int intel_guc_send_busy_loop(struct intel_guc *guc,
/* No sleeping with spin locks, just busy loop */
might_sleep_if(loop && not_atomic);
-retry:
- err = intel_guc_send_nb(guc, action, len, g2h_len_dw);
- if (unlikely(err == -EBUSY && loop)) {
- if (likely(not_atomic)) {
- if (msleep_interruptible(sleep_period_ms))
- return -EINTR;
- sleep_period_ms = sleep_period_ms << 1;
- } else {
- cpu_relax();
- }
- goto retry;
- }
-
- return err;
+ if (!loop)
+ return intel_guc_send_nb(guc, action, len, g2h_len_dw);
+
+ if (not_atomic)
+ timedout = poll_timeout_us(err = intel_guc_send_nb(guc, action,
+ len, g2h_len_dw),
+ err != -EBUSY, USEC_PER_MSEC,
+ POLL_TIMEOUT_DUR, false);
+ else
+ timedout = poll_timeout_us_atomic(err = intel_guc_send_nb(guc, action,
+ len, g2h_len_dw),
+ err != -EBUSY, USEC_PER_MSEC,
+ POLL_TIMEOUT_DUR, false);
+ return timedout ?: err;
}
/* Only call this from the interrupt handler code */
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
index 1c455d84bf9d..9f9fb5b10ed4 100644
--- a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
+++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
@@ -706,37 +706,19 @@ static int ct_send_nb(struct intel_guc_ct *ct,
return ret;
}
-static int ct_send(struct intel_guc_ct *ct,
- const u32 *action,
- u32 len,
- u32 *response_buf,
- u32 response_buf_size,
- u32 *status)
+static int ct_lazy_spin(struct intel_guc_ct *ct,
+ struct ct_request *request,
+ const u32 *action,
+ u32 len,
+ u32 *response_buf,
+ u32 response_buf_size,
+ u32 *status)
{
struct intel_guc_ct_buffer *ctb = &ct->ctbs.send;
- struct ct_request request;
unsigned long flags;
- unsigned int sleep_period_ms = 1;
- bool send_again;
u32 fence;
int err;
- GEM_BUG_ON(!ct->enabled);
- GEM_BUG_ON(!len);
- GEM_BUG_ON(len > GUC_CTB_HXG_MSG_MAX_LEN - GUC_CTB_HDR_LEN);
- GEM_BUG_ON(!response_buf && response_buf_size);
- might_sleep();
-
-resend:
- send_again = false;
-
- /*
- * We use a lazy spin wait loop here as we believe that if the CT
- * buffers are sized correctly the flow control condition should be
- * rare. Reserving the maximum size in the G2H credits as we don't know
- * how big the response is going to be.
- */
-retry:
spin_lock_irqsave(&ctb->lock, flags);
if (unlikely(!h2g_has_room(ct, len + GUC_CTB_HDR_LEN) ||
!g2h_has_room(ct, GUC_CTB_HXG_MSG_MAX_LEN))) {
@@ -746,31 +728,67 @@ static int ct_send(struct intel_guc_ct *ct,
if (unlikely(ct_deadlocked(ct)))
return -EPIPE;
-
- if (msleep_interruptible(sleep_period_ms))
- return -EINTR;
- sleep_period_ms = sleep_period_ms << 1;
-
- goto retry;
+ return -EBUSY;
}
ct->stall_time = KTIME_MAX;
fence = ct_get_next_fence(ct);
- request.fence = fence;
- request.status = 0;
- request.response_len = response_buf_size;
- request.response_buf = response_buf;
+ request->fence = fence;
+ request->status = 0;
+ request->response_len = response_buf_size;
+ request->response_buf = response_buf;
spin_lock(&ct->requests.lock);
- list_add_tail(&request.link, &ct->requests.pending);
+ list_add_tail(&request->link, &ct->requests.pending);
spin_unlock(&ct->requests.lock);
err = ct_write(ct, action, len, fence, 0);
g2h_reserve_space(ct, GUC_CTB_HXG_MSG_MAX_LEN);
spin_unlock_irqrestore(&ctb->lock, flags);
+ return err;
+}
+static int ct_send(struct intel_guc_ct *ct,
+ const u32 *action,
+ u32 len,
+ u32 *response_buf,
+ u32 response_buf_size,
+ u32 *status)
+{
+ struct ct_request request;
+ unsigned long flags;
+ bool send_again;
+ int err, timedout;
+
+ GEM_BUG_ON(!ct->enabled);
+ GEM_BUG_ON(!len);
+ GEM_BUG_ON(len > GUC_CTB_HXG_MSG_MAX_LEN - GUC_CTB_HDR_LEN);
+ GEM_BUG_ON(!response_buf && response_buf_size);
+ might_sleep();
+
+resend:
+ send_again = false;
+
+ /*
+ * We use a lazy spin wait loop here as we believe that if the CT
+ * buffers are sized correctly the flow control condition should be
+ * rare. Reserving the maximum size in the G2H credits as we don't know
+ * how big the response is going to be.
+ */
+ timedout = poll_timeout_us_atomic(err = ct_lazy_spin(ct, &request, action,
+ len, response_buf,
+ response_buf_size,
+ status),
+ err != -EBUSY, USEC_PER_MSEC,
+ POLL_TIMEOUT_DUR, false);
+
+ /* This is only the case if ct is deadlocked or we time out */
+ if (ct->stall_time != KTIME_MAX)
+ return timedout ?: err;
+
+ /* Otherwise, ct_write failed and we need to clean up */
if (unlikely(err))
goto unlink;
--
2.53.0
next reply other threads:[~2026-07-06 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 15:35 Jonathan Cavitt [this message]
2026-07-07 0:30 ` ✗ i915.CI.BAT: failure for drm/i915/gt: Use poll_timeout_us in place of sliding sleep window (rev4) Patchwork
2026-07-09 9:15 ` [PATCH v4] drm/i915/gt: Use poll_timeout_us in place of sliding sleep window Krzysztof Karas
2026-07-24 12:50 ` Andi Shyti
2026-07-27 14:21 ` Cavitt, Jonathan
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=20260706153510.1466259-1-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=andi.shyti@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=krzysztof.karas@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