From: Petri Latvala <petri.latvala@intel.com>
To: "Saarinen, Jani" <jani.saarinen@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>
Cc: "Goel, Akash" <akash.goel@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: warning for drm/i915: Allocate intel_engine_cs structure only for the enabled engines (rev3)
Date: Fri, 14 Oct 2016 13:37:46 +0300 [thread overview]
Message-ID: <11e7b96c-054d-b200-eef3-12fa327875eb@intel.com> (raw)
In-Reply-To: <43D4F724E12AB6478FC1572B3FBE89D04C034AAB@IRSMSX106.ger.corp.intel.com>
>> Are the test run in the order defined by fast-feedback.testlist ?
>> I intended the vgem unload test to be run as the first vgem testcase to
>> minimise the chance of a stray module leak. Can we define the order within
>> CI? Can we put comments into fast-feedback.testlist ?
> My understanding, yes, we are running on that order.
> Adding comment, no I think no, Petri, Tomi?
>
Order: Yes, that order. I'm waiting for an opportune moment to test a
patch to sleep-and-retry in vgem unload to prune out the cases of just
having soon-to-finish work left over. Just need to tune the amount of
retries and sleeping.
We can also order vgem unload test to be first (along with
drv_module_reload) depending on whether we want to catch those stray
module leaks. Comments on that tradeoff?
Comments in the test list: Not yet. Piglit patch for them just sent to
piglit mailing list.
Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-14 10:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 9:33 [PATCH v9] drm/i915: Allocate intel_engine_cs structure only for the enabled engines akash.goel
2016-10-07 9:58 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-10-07 11:44 ` Chris Wilson
2016-10-07 11:53 ` Goel, Akash
2016-10-07 10:49 ` [PATCH v9] " Joonas Lahtinen
2016-10-07 13:24 ` akash goel
2016-10-07 19:11 ` [PATCH v10] " akash.goel
2016-10-10 12:33 ` ✗ Fi.CI.BAT: warning for drm/i915: Allocate intel_engine_cs structure only for the enabled engines (rev3) Patchwork
2016-10-13 16:10 ` Goel, Akash
2016-10-13 16:28 ` Tvrtko Ursulin
2016-10-13 17:14 ` [PATCH v11] drm/i915: Allocate intel_engine_cs structure only for the enabled engines akash.goel
2016-10-13 18:47 ` ✗ Fi.CI.BAT: warning for drm/i915: Allocate intel_engine_cs structure only for the enabled engines (rev3) Saarinen, Jani
2016-10-13 19:57 ` Chris Wilson
2016-10-14 6:03 ` Saarinen, Jani
2016-10-14 10:37 ` Petri Latvala [this message]
2016-10-14 11:01 ` Chris Wilson
2016-10-13 17:20 ` ✗ Fi.CI.BAT: warning for drm/i915: Allocate intel_engine_cs structure only for the enabled engines (rev4) Patchwork
2016-10-14 9:02 ` Goel, Akash
2016-10-14 9:04 ` Tvrtko Ursulin
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=11e7b96c-054d-b200-eef3-12fa327875eb@intel.com \
--to=petri.latvala@intel.com \
--cc=akash.goel@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=tomi.p.sarvela@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.