public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Katarzyna Dec <katarzyna.dec@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/gem_exec_parallel: Add skip_on_simulation to whole binary
Date: Fri, 8 Feb 2019 14:49:28 +0100	[thread overview]
Message-ID: <20190208134928.GC27881@kdec5-desk.ger.corp.intel.com> (raw)
In-Reply-To: <154963336247.3378.2628103121008962909@skylake-alporthouse-com>

On Fri, Feb 08, 2019 at 01:42:42PM +0000, Chris Wilson wrote:
> Quoting Katarzyna Dec (2019-02-08 13:32:38)
> > On Fri, Feb 08, 2019 at 01:27:51PM +0000, Chris Wilson wrote:
> > > Quoting Katarzyna Dec (2019-02-08 13:23:59)
> > > > On Fri, Feb 08, 2019 at 01:14:26PM +0000, Chris Wilson wrote:
> > > > > Quoting Katarzyna Dec (2019-02-08 13:10:37)
> > > > > > On simulation environment these tests were failing. During debug
> > > > > > we decided that whole binary should be skipped, because there is
> > > > > > no additional coverage in simulation.
> > > > > 
> > > > > How did they fail? There are some paths here that are rarely touched
> > > > > elsewhere.
> > > > > -Chris
> > > > I like you challenges Chris :)
> > > > 
> > > > gem_exec_parallel@*context* were failing with error:
> > > > 
> > > > (gem_exec_parallel:1245) ioctl_wrappers-CRITICAL: Test assertion failure
> > > > function gem_execbuf, file ../lib/ioctl_wrappers.c:605:
> > > > (gem_exec_parallel:1245) ioctl_wrappers-CRITICAL: Failed assertion:
> > > > __gem_execbuf(fd, execbuf) == 0
> > > > (gem_exec_parallel:1245) ioctl_wrappers-CRITICAL: error: -28 != 0
> > > 
> > > Should not happen.
> > But happends and is reproducible on some CI runs.
> 
> Well fix it. It is not a valid error in this case. ENOSPC is only valid
> in the case the user submitted more than could be fitted into the GGTT
> (or had an overlap in their softpin). In this instance, it means that
> one _context_ impacted another client, and that is simply not allowed.
>
According to what you are saying we need to debug and fix the issue.
> > > > and @*fds* with:
> > > > 
> > > > (gem_exec_parallel:1315) igt_debugfs-CRITICAL: Last errno: 24, Too many open
> > > > files
> > > 
> > > That is boring, but more indicative of system setup failure. We should
> > > be configuring the system to allow ourselves, as root, to use as many fd
> > > as can fit in memory.
> > > 
> > > I'd recommend a pass through the basic stress test at least. It won't
> > > take a lot to exercise some unusual conditions.
> > > -Chris
> > 
> > What if we skip all *context* and all *fds* and leave rest as it is?
> > Will it be resonable in this shape?
> 
> I would rewrite it such that the threads ran for a certain period of
> time rather than iterations; set basic to something small (say 2s) and
> left everything else to run for 150s (tends to be the common value I've
Is this comment to *fds* testcases or general to whole binary?
Kasia :)
> used for random stress tests). Then skip everything but the basic-all
> test.
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-08 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 13:10 [igt-dev] [PATCH i-g-t] i915/gem_exec_parallel: Add skip_on_simulation to whole binary Katarzyna Dec
2019-02-08 13:14 ` Chris Wilson
2019-02-08 13:23   ` Katarzyna Dec
2019-02-08 13:27     ` Chris Wilson
2019-02-08 13:32       ` Katarzyna Dec
2019-02-08 13:42         ` Chris Wilson
2019-02-08 13:49           ` Katarzyna Dec [this message]
2019-02-08 13:57             ` Chris Wilson
2019-02-08 13:55 ` [igt-dev] ✗ Fi.CI.BAT: failure for " 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=20190208134928.GC27881@kdec5-desk.ger.corp.intel.com \
    --to=katarzyna.dec@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