From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH v3 2/3] drm/i915/gt: Double check heartbeat timeout before resetting
Date: Thu, 04 Feb 2021 14:57:46 +0200 [thread overview]
Message-ID: <87zh0kt2gl.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20210204110620.32422-2-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Check that we have actually passed the heartbeat interval since last
> checking the request before resetting the device.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2780
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c b/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
> index 48a91c0dbad6..93741a65924a 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
> @@ -31,7 +31,7 @@ static bool next_heartbeat(struct intel_engine_cs *engine)
> delay = msecs_to_jiffies_timeout(delay);
> if (delay >= HZ)
> delay = round_jiffies_up_relative(delay);
> - mod_delayed_work(system_highpri_wq, &engine->heartbeat.work, delay);
> + mod_delayed_work(system_highpri_wq, &engine->heartbeat.work, delay + 1);
>
> return true;
> }
> @@ -103,6 +103,13 @@ static void heartbeat(struct work_struct *wrk)
> goto out;
>
> if (engine->heartbeat.systole) {
> + long delay = READ_ONCE(engine->props.heartbeat_interval_ms);
> +
> + /* Safeguard against too-fast worker invocations */
> + if (!time_after(jiffies,
> + rq->emitted_jiffies + msecs_to_jiffies(delay)))
> + goto out;
> +
> if (!i915_sw_fence_signaled(&rq->submit)) {
> /*
> * Not yet submitted, system is stalled.
> @@ -139,6 +146,8 @@ static void heartbeat(struct work_struct *wrk)
> "stopped heartbeat on %s",
> engine->name);
> }
> +
> + rq->emitted_jiffies = jiffies;
Would possibly interfere with throttle. But who would get handle to
internal request.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> goto out;
> }
>
> --
> 2.20.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-02-04 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 11:06 [Intel-gfx] [PATCH v3 1/3] drm/i915/selftests: Restore previous heartbeat interval Chris Wilson
2021-02-04 11:06 ` [Intel-gfx] [PATCH v3 2/3] drm/i915/gt: Double check heartbeat timeout before resetting Chris Wilson
2021-02-04 12:57 ` Mika Kuoppala [this message]
2021-02-04 13:02 ` Chris Wilson
2021-02-04 11:06 ` [Intel-gfx] [PATCH v3 3/3] drm/i915/gt: Ratelimit heartbeat completion probing Chris Wilson
2021-02-04 12:45 ` [Intel-gfx] [PATCH v3 1/3] drm/i915/selftests: Restore previous heartbeat interval Mika Kuoppala
2021-02-04 17:12 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v3,1/3] " 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=87zh0kt2gl.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.