public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Caz Yokoyama <Caz.Yokoyama@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v3 1/1] i915_pm_rpm: gem-execbuf-stress-extra-wait faster
Date: Wed, 13 Mar 2019 15:29:08 -0700	[thread overview]
Message-ID: <1e235670d77eefa98744fb1ee7372e5fa6fff9fb.camel@intel.com> (raw)
In-Reply-To: <155251153190.30003.15303697863062228863@skylake-alporthouse-com>

Chris,

As I sai on Tue, 12 Mar 2019 09:11:14 -0700,
My intention is to remove gem-execbuf-stress-extra-wait subtest
because it does same as gem-execbuf-stress except for meaningless (10 x
5 sec) delay.

I believe the delay provides no extra coverage. It may be added as same
as other subtest such as modeset_subtest(). WAIT_EXTRA may provide
extra coverage for modeset_subtest() while it does not for gem-execbuf-
stress.
-caz

On Wed, 2019-03-13 at 21:12 +0000, Chris Wilson wrote:
> Quoting Caz Yokoyama (2019-03-14 00:46:08)
> > Replace (5sec * 10) delay by forcing to suspended state.
> > While this patch expects a corresponding patch in drm-tip,
> > the test runs successful without the corresponding patch.
> > Its runtime is 2-3 sec on my local machine, nuc.
> 
> WAIT_EXTRA is always being used in conjunction with WAIT_STATUS, so
> it
> simply is checking that things do not break with an extra sleep after
> suspending.
> 
> Removing that delay nerfs the test, you may as well simply not run
> the
> test.
> 
> Instead of removing the delay we need to be replacing the delay with
> something more likely to trigger a bug, or just remove the test as we
> believe it provides no extra coverage.
> -Chris

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-03-13 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14  0:46 [igt-dev] [PATCH i-g-t v3 1/1] i915_pm_rpm: gem-execbuf-stress-extra-wait faster Caz Yokoyama
2019-03-13 20:03 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v3,1/1] " Patchwork
2019-03-13 21:12 ` [igt-dev] [PATCH i-g-t v3 1/1] " Chris Wilson
2019-03-13 22:29   ` Caz Yokoyama [this message]
2019-03-14  3:04 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,v3,1/1] " 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=1e235670d77eefa98744fb1ee7372e5fa6fff9fb.camel@intel.com \
    --to=caz.yokoyama@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@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