From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t 2/2] i915/gem_eio: Allow older platforms more leniency in reset latency
Date: Fri, 15 Feb 2019 16:43:24 +0200 [thread overview]
Message-ID: <87ef89yuwj.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190212205740.20368-2-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Older platforms need to clobber the display around a reset (incl. a
> modeset to off, and a modeset back on), which can be much slower than
> the reset itself. Give these platforms (gen2-4) some leniency and allow
> them a higher limit before declaring them a failure.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> tests/i915/gem_eio.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/tests/i915/gem_eio.c b/tests/i915/gem_eio.c
> index bd5266104..ac85a2eff 100644
> --- a/tests/i915/gem_eio.c
> +++ b/tests/i915/gem_eio.c
> @@ -259,7 +259,7 @@ static void check_wait(int fd, uint32_t bo, unsigned int wait, igt_stats_t *st)
>
> static void check_wait_elapsed(int fd, igt_stats_t *st)
> {
> - double med, max;
> + double med, max, limit;
>
> igt_info("Completed %d resets, wakeups took %.3f+-%.3fms (min:%.3fms, median:%.3fms, max:%.3fms)\n",
> st->n_values,
> @@ -272,15 +272,24 @@ static void check_wait_elapsed(int fd, igt_stats_t *st)
> if (st->n_values < 9)
> return; /* too few for stable median */
>
> + /*
> + * Older platforms need to reset the display (incl. modeset to off,
> + * modeset back on) around resets, so may take a lot longer.
> + */
> + limit = 250e6;
> + if (intel_gen(intel_get_drm_devid(fd)) < 5)
> + limit += 300e6; /* guestimate for 2x worstcase modeset */
Don't have any insight to offer for the hard cap. 550ms sounds
reasonable!
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> +
> med = igt_stats_get_median(st);
> max = igt_stats_get_max(st);
> - igt_assert_f(med < 250e6 && max < 1250e6,
> - "Wake up following reset+wedge took %.3f+-%.3fms (min:%.3fms, median:%.3fms, max:%.3fms)\n",
> + igt_assert_f(med < limit && max < 5 * limit,
> + "Wake up following reset+wedge took %.3f+-%.3fms (min:%.3fms, median:%.3fms, max:%.3fms); limit set to %.0fms on average and %.0fms maximum\n",
> igt_stats_get_mean(st)*1e-6,
> igt_stats_get_std_deviation(st)*1e-6,
> igt_stats_get_min(st)*1e-6,
> igt_stats_get_median(st)*1e-6,
> - igt_stats_get_max(st)*1e-6);
> + igt_stats_get_max(st)*1e-6,
> + limit*1e-6, limit*5e-6);
> }
>
> static void __test_banned(int fd)
> --
> 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:[~2019-02-15 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 20:57 [igt-dev] [PATCH i-g-t 1/2] i915/gem_eio: Check average reset times Chris Wilson
2019-02-12 20:57 ` [igt-dev] [PATCH i-g-t 2/2] i915/gem_eio: Allow older platforms more leniency in reset latency Chris Wilson
2019-02-15 14:43 ` Mika Kuoppala [this message]
2019-02-12 21:22 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] i915/gem_eio: Check average reset times Patchwork
2019-02-12 23:12 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-15 14:40 ` [Intel-gfx] [PATCH i-g-t 1/2] " Mika Kuoppala
2019-02-15 14:52 ` [igt-dev] " Chris Wilson
2019-02-15 15:02 ` Mika Kuoppala via igt-dev
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=87ef89yuwj.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--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