public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/i915_pm_rpm: Split the planes into dynamic subtests
Date: Wed, 22 Apr 2020 11:45:59 +0300	[thread overview]
Message-ID: <20200422084559.GG9497@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <158754459592.11203.9839200188400166169@build.alporthouse.com>

On Wed, Apr 22, 2020 at 09:36:35AM +0100, Chris Wilson wrote:
> Quoting Petri Latvala (2020-04-22 09:33:49)
> > On Wed, Apr 22, 2020 at 09:12:58AM +0100, Chris Wilson wrote:
> > > Use the dynamic subtests to allow the user to individually run the
> > > per-plane rpm tests.
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Petri Latvala <petri.latvala@intel.com>
> > > ---
> > >  tests/i915/i915_pm_rpm.c | 18 +++++++-----------
> > >  1 file changed, 7 insertions(+), 11 deletions(-)
> > > 
> > > diff --git a/tests/i915/i915_pm_rpm.c b/tests/i915/i915_pm_rpm.c
> > > index 4f8124dc4..a34e78b6b 100644
> > > --- a/tests/i915/i915_pm_rpm.c
> > > +++ b/tests/i915/i915_pm_rpm.c
> > > @@ -1778,7 +1778,7 @@ static void test_one_plane(bool dpms, uint32_t plane_id,
> > >  /* This one also triggered WARNs on our driver at some point in time. */
> > >  static void planes_subtest(bool universal, bool dpms)
> > >  {
> > > -     int i, rc, planes_tested = 0, crtc_idx;
> > > +     int i, rc, crtc_idx;
> > >       drmModePlaneResPtr planes;
> > >  
> > >       igt_require(default_mode_params);
> > > @@ -1803,8 +1803,8 @@ static void planes_subtest(bool universal, bool dpms)
> > >  
> > >                       type = universal ? get_plane_type(plane->plane_id) :
> > >                                          PLANE_OVERLAY;
> > > -                     test_one_plane(dpms, plane->plane_id, type);
> > > -                     planes_tested++;
> > > +                     igt_dynamic_f("plane-%d\n", plane->plane_id)
> > > +                             test_one_plane(dpms, plane->plane_id, type);
> > >               }
> > >               drmModeFreePlane(plane);
> > >       }
> > > @@ -1813,10 +1813,6 @@ static void planes_subtest(bool universal, bool dpms)
> > >       if (universal) {
> > >               rc = drmSetClientCap(drm_fd, DRM_CLIENT_CAP_UNIVERSAL_PLANES, 0);
> > >               igt_assert_eq(rc, 0);
> > > -
> > > -             igt_assert_lte(3, planes_tested);
> > > -     } else {
> > > -             igt_assert_lte(1, planes_tested);
> > 
> > Sure, we cannot have these asserts anymore when people can run a
> > limited set. Do we need to check them somewhere else?
> > 
> > Hang on, what was the point of these asserts? Asserting that we have
> > at least 3 universal planes? And at least 1 of non-universal? Wtf?
> 
> I'm glad I wasn't the only one asking that :)
> 
> This isn't even a test for the universal/legacy API, it's just checking
> that we don't get runtime errors when poking them.


Yeah, off with them!

Reviewed-by: Petri Latvala <petri.latvala@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-04-22  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22  8:10 [igt-dev] [PATCH i-g-t] i915/i915_pm_rpm: Split the planes into dynamic subtests Chris Wilson
2020-04-22  8:12 ` Chris Wilson
2020-04-22  8:33   ` Petri Latvala
2020-04-22  8:36     ` Chris Wilson
2020-04-22  8:45       ` Petri Latvala [this message]
2020-04-22  9:06 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/i915_pm_rpm: Split the planes into dynamic subtests (rev2) Patchwork
2020-04-22  9:14   ` Petri Latvala
2020-04-22  9:43     ` Vudum, Lakshminarayana
2020-04-22  9:33 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-04-22 10:30 ` [igt-dev] ✗ Fi.CI.IGT: 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=20200422084559.GG9497@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@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