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] drm/i915/selftests: Bump the scheduling threshold for fast heartbeats
Date: Wed, 13 Jan 2021 16:13:57 +0200 [thread overview]
Message-ID: <87czy8lyai.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20210113125939.10205-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Since we are system_highpri_wq, we expected the heartbeat to be
> scheduled promptly. However, we see delays of over 10ms upsetting our
> assertions. Accept this as inevitable and bump the error threshold to
> 20ms (from 6ms).
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/gt/selftest_engine_heartbeat.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/selftest_engine_heartbeat.c b/drivers/gpu/drm/i915/gt/selftest_engine_heartbeat.c
> index b88aa35ad75b..e88a01390dc5 100644
> --- a/drivers/gpu/drm/i915/gt/selftest_engine_heartbeat.c
> +++ b/drivers/gpu/drm/i915/gt/selftest_engine_heartbeat.c
> @@ -197,6 +197,7 @@ static int cmp_u32(const void *_a, const void *_b)
>
> static int __live_heartbeat_fast(struct intel_engine_cs *engine)
> {
> + const int error_threshold = max(20000, jffies_to_usecs(6));
s/jffies/jiffies
Also for the commit message, 6 jiffies are not 6ms so it needs
some mending.
-Mika
> struct intel_context *ce;
> struct i915_request *rq;
> ktime_t t0, t1;
> @@ -254,12 +255,18 @@ static int __live_heartbeat_fast(struct intel_engine_cs *engine)
> times[0],
> times[ARRAY_SIZE(times) - 1]);
>
> - /* Min work delay is 2 * 2 (worst), +1 for scheduling, +1 for slack */
> - if (times[ARRAY_SIZE(times) / 2] > jiffies_to_usecs(6)) {
> + /*
> + * Ideally, the upper bound on min work delay would be something like
> + * 2 * 2 (worst), +1 for scheduling, +1 for slack. In practice, we
> + * are, even with system_wq_highpri, at the mercy of the CPU scheduler
> + * and may be stuck behind some slow work for many millisecond. Such
> + * as our very own display workers.
> + */
> + if (times[ARRAY_SIZE(times) / 2] > error_threshold) {
> pr_err("%s: Heartbeat delay was %uus, expected less than %dus\n",
> engine->name,
> times[ARRAY_SIZE(times) / 2],
> - jiffies_to_usecs(6));
> + error_threshold);
> err = -EINVAL;
> }
>
> --
> 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-01-13 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 12:51 [Intel-gfx] [PATCH] drm/i915/selftests: Bump the scheduling threshold for fast heartbeats Chris Wilson
2021-01-13 12:59 ` Chris Wilson
2021-01-13 14:13 ` Mika Kuoppala [this message]
2021-01-13 14:20 ` Chris Wilson
2021-01-13 14:23 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/selftests: Bump the scheduling threshold for fast heartbeats (rev2) Patchwork
2021-01-13 14:45 ` [Intel-gfx] [PATCH v2] drm/i915/selftests: Bump the scheduling error threshold for fast heartbeats Chris Wilson
2021-01-13 16:00 ` Mika Kuoppala
2021-01-13 18:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Bump the scheduling threshold for fast heartbeats (rev3) Patchwork
2021-01-13 19:04 ` [Intel-gfx] ✗ Fi.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=87czy8lyai.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox