From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v3] tests/gem_ringfill: Add {render, blitter}-forked-1 subtests.
Date: Wed, 01 Jul 2015 16:19:17 +0300 [thread overview]
Message-ID: <874mloow16.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20150629104226.GD15506@nuc-i3427.alporthouse.com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> On Fri, Jun 26, 2015 at 02:52:34PM +0300, Joonas Lahtinen wrote:
>> Add forking subtests to gem_ringfill. Tests cause consistent GPU
>> hangs on SKL.
>>
>> v2: Removed noop parts.
>> v3:
>> - Allow executing the tests in order too (Chris Wilson).
>> - Rename the tests to -forked-1
>>
>> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89959
>
> I extended the test to cover the forked-N case and found that we shared
> the first batch handle (due to creating the intel_batch_buffer in the
> parent). Fixed that up and pushed, hopefully it still causes SKL to die
> horribly.
It does, very well. And has already helped to isolate the blitter
ctx switches out from the pool of suspects. Thanks for the test
and pushing it.
-Mika
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-07-01 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 11:52 [PATCH i-g-t v3] tests/gem_ringfill: Add {render, blitter}-forked-1 subtests Joonas Lahtinen
2015-06-29 10:42 ` Chris Wilson
2015-07-01 13:19 ` Mika Kuoppala [this message]
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=874mloow16.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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.