All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kahola <mika.kahola@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] tests/kms_pipe_crc_basic: Reset GPU before running subtests
Date: Tue, 06 Jun 2017 15:33:14 +0300	[thread overview]
Message-ID: <1496752394.11332.52.camel@intel.com> (raw)
In-Reply-To: <20170606122737.GC12629@intel.com>

On Tue, 2017-06-06 at 15:27 +0300, Ville Syrjälä wrote:
> On Tue, Jun 06, 2017 at 03:20:46PM +0300, Mika Kahola wrote:
> > 
> > It has been noticed by our CI BAT testing that in some 1%-3%
> > probability
> > kms_pipe_crc_basic subtest read-crc-pipe-x-frame-sequence fails
> > when
> > comparing gathered CRC frames. However, running kms_pipe_crc_basic
> > subtests alone i.e. outside BAT I was unable to replicate the
> > issue.
> > 
> > The patch proposes a GPU reset before running the subtests. This
> > way we
> > can ensure that GPU register settings are reinitialized if they
> > have been
> > altered by the tests executed earlier in BAT.
> What does GPU reset have to do with display CRCs?
It's unclear but when you do it I was unable to replicate this in
couple hundred BAT runs. Maybe the error probability just hits below 1%
mark with this.

> 
> > 
> > 
> > The issue has been seen on following bug reports
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99788
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100367
> > 
> > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> > ---
> >  tests/kms_pipe_crc_basic.c | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> > 
> > diff --git a/tests/kms_pipe_crc_basic.c
> > b/tests/kms_pipe_crc_basic.c
> > index f49b434..e1940e6 100644
> > --- a/tests/kms_pipe_crc_basic.c
> > +++ b/tests/kms_pipe_crc_basic.c
> > @@ -175,6 +175,13 @@ static void test_read_crc(data_t *data, int
> > pipe, unsigned flags)
> >  	igt_require_f(valid_connectors, "No connector found for
> > pipe %i\n", pipe);
> >  }
> >  
> > +static void reset_gpu(void)
> > +{
> > +	int fd = drm_open_driver(DRIVER_INTEL);
> > +	igt_post_hang_ring(fd, igt_hang_ring(fd,
> > I915_EXEC_DEFAULT));
> > +	close(fd);
> > +}
> > +
> >  data_t data = {0, };
> >  
> >  igt_main
> > @@ -194,6 +201,9 @@ igt_main
> >  		data.debugfs = igt_debugfs_dir(data.drm_fd);
> >  	}
> >  
> > +	/* before running tests, reset gpu */
> > +	reset_gpu();
> > +
> >  	igt_subtest("bad-pipe")
> >  		test_bad_command(&data, "pipe D none");
> >  
> > -- 
> > 2.7.4
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
-- 
Mika Kahola - Intel OTC

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-06-06 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 12:20 [PATCH i-g-t] tests/kms_pipe_crc_basic: Reset GPU before running subtests Mika Kahola
2017-06-06 12:27 ` Ville Syrjälä
2017-06-06 12:33   ` Mika Kahola [this message]
2017-06-06 13:23     ` Chris Wilson
2017-06-07  8:00       ` Mika Kahola
2017-06-07 10:24         ` Chris Wilson
2017-06-07 10:50           ` Mika Kahola

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=1496752394.11332.52.camel@intel.com \
    --to=mika.kahola@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /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.