public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] tests/kms_mmap_write_crc: Fix igt_fixture handling
Date: Thu, 21 Feb 2019 00:44:59 +0100	[thread overview]
Message-ID: <20190220234459.GH2665@phenom.ffwll.local> (raw)
In-Reply-To: <155067308109.30979.12568907326839654466@skylake-alporthouse-com>

On Wed, Feb 20, 2019 at 02:31:21PM +0000, Chris Wilson wrote:
> Quoting Daniel Vetter (2019-02-20 14:24:48)
> > igt_fixture within an igt_simple_test don't really work as advertised.
> > 
> > Minimal fix, the testcase seems fairly questionable already ...
> 
> Definitely; it was written to reproduce a specific setup and demonstrate
> an issue with forgetting to sync, or soemthing like that. Maarten
> hopefully knows whether this can be simply subsumed into one of our
> other tests. It's just the use of a cpu_hog stands out; though really it
> wants a memory_hog? for that extra bit of cache pressure. That might be
> useful to generalise in our other coherency sensitive tests.
> 
> > References: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_222/fi-icl-y/igt@kms_mmap_write_crc.html
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > ---
> >  tests/kms_mmap_write_crc.c | 11 +++++++----
> >  1 file changed, 7 insertions(+), 4 deletions(-)
> > 
> > diff --git a/tests/kms_mmap_write_crc.c b/tests/kms_mmap_write_crc.c
> > index 93c96ef4de08..bf2b0c2991b3 100644
> > --- a/tests/kms_mmap_write_crc.c
> > +++ b/tests/kms_mmap_write_crc.c
> > @@ -268,7 +268,8 @@ static data_t data;
> >  int main(int argc, char **argv)
> >  {
> >         int i;
> > -       igt_simple_init_parse_opts(&argc, argv, "n", NULL, NULL, opt_handler, NULL);
> > +       igt_subtest_init_parse_opts(&argc, argv, "n", NULL, NULL,
> > +                                   opt_handler, NULL);
> >  
> >         igt_skip_on_simulation();
> >  
> > @@ -286,10 +287,12 @@ int main(int argc, char **argv)
> >                 fork_cpuhog_helper();
> >         }
> >  
> > -       igt_info("Using %d rounds for the test\n", ROUNDS);
> > +       igt_subtest("main") {
> > +               igt_info("Using %d rounds for the test\n", ROUNDS);
> >  
> > -       for (i = 0; i < ROUNDS; i++)
> > -               run_test(&data);
> > +               for (i = 0; i < ROUNDS; i++)
> > +                       run_test(&data);
> > +       }
> 
> Ok, that was much simpler than I feared. I started by ripping out the
> parse_opts :)

Yeah occasionally it pays of to be a minimalist :-)

> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Thanks for taking a look, merged.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-20 23:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 14:24 [igt-dev] [PATCH i-g-t 1/3] lib/tests: Use ARRAY_SIZE Daniel Vetter
2019-02-20 14:24 ` [igt-dev] [PATCH i-g-t 2/3] tests/kms_mmap_write_crc: Fix igt_fixture handling Daniel Vetter
2019-02-20 14:31   ` Chris Wilson
2019-02-20 23:44     ` Daniel Vetter [this message]
2019-02-20 14:24 ` [igt-dev] [PATCH i-g-t 3/3] lib: disallow fixtures/subtest groups in simple tests Daniel Vetter
2019-02-20 14:51   ` Arkadiusz Hiler
2019-02-20 23:41     ` Daniel Vetter
2019-02-20 15:00 ` [igt-dev] [PATCH i-g-t 1/3] lib/tests: Use ARRAY_SIZE Arkadiusz Hiler
2019-02-20 23:38   ` Daniel Vetter
2019-02-20 15:14 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] " Patchwork
2019-02-20 17:46 ` [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=20190220234459.GH2665@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@intel.com \
    --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