From: "Szwichtenberg, Radoslaw" <radoslaw.szwichtenberg@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Subject: Re: [PATCH igt 5/5] igt/gem_flink_race: Limit name subtest to 5s
Date: Mon, 11 Sep 2017 10:10:27 +0000 [thread overview]
Message-ID: <1505124625.21576.20.camel@intel.com> (raw)
In-Reply-To: <20170911085602.23506-6-chris@chris-wilson.co.uk>
On Mon, 2017-09-11 at 09:56 +0100, Chris Wilson wrote:
> At present, we try to do 1,000,000 cycles, which may be a reasonable
> estimate for detecting the race, takes 6 minutes in practice on bxt on a
> good day (as it spends more time doing rpm suspend/resume than actual work,
> and that accounts for more of the relative difference in performance
> between bxt and big core than the difference in clocks+ipc).
>
> An ideal solution would be to have a data-race detector in the kernel
> combined with a short test to exercise the different paths. Lacking the
> DRD, use a shorter test anyway. 5s is chosen simply on the basis that
> the other race subtest is also run over a 5s interval.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Radoslaw Szwichtenberg <radoslaw.szwichtenberg@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-11 10:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 8:55 CI urgent Chris Wilson
2017-09-11 8:55 ` [PATCH igt 1/5] igt/gem_eio: inflight wedged requires long plugging Chris Wilson
2017-09-11 10:57 ` Petri Latvala
2017-09-11 11:06 ` Martin Peres
2017-09-11 11:11 ` Chris Wilson
2017-09-11 12:03 ` Michał Winiarski
2017-09-11 12:14 ` Chris Wilson
2017-09-11 8:55 ` [PATCH igt 2/5] igt/gem_eio: Exercise wedged with native in-flight requests Chris Wilson
2017-09-11 8:56 ` [PATCH igt 3/5] igt/gem_eio: Install an exithandler to unwedge the device after failure Chris Wilson
2017-09-11 10:45 ` Arkadiusz Hiler
2017-09-11 8:56 ` [PATCH igt 4/5] igt/gem_fence_thresh: Use streaming reads for verify Chris Wilson
2017-09-11 8:56 ` [PATCH igt 5/5] igt/gem_flink_race: Limit name subtest to 5s Chris Wilson
2017-09-11 10:09 ` Arkadiusz Hiler
2017-09-11 10:10 ` Szwichtenberg, Radoslaw [this message]
2017-09-11 9:50 ` ✓ Fi.CI.BAT: success for series starting with [1/5] igt/gem_eio: inflight wedged requires long plugging Patchwork
2017-09-11 11:51 ` ✓ Fi.CI.IGT: " 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=1505124625.21576.20.camel@intel.com \
--to=radoslaw.szwichtenberg@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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