From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, Dave Gordon <david.s.gordon@intel.com>
Subject: Re: ✓ Ro.CI.BAT: success for drm/i915/guc: use one GuC client per GPU engine
Date: Fri, 22 Jul 2016 11:06:47 +0100 [thread overview]
Message-ID: <5791F037.90908@linux.intel.com> (raw)
In-Reply-To: <20160722060236.15819.66852@emeril.freedesktop.org>
On 22/07/16 07:02, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/guc: use one GuC client per GPU engine
> URL : https://patchwork.freedesktop.org/series/10149/
> State : success
>
> == Summary ==
>
> Series 10149v1 drm/i915/guc: use one GuC client per GPU engine
> http://patchwork.freedesktop.org/api/1.0/series/10149/revisions/1/mbox
>
>
> fi-hsw-i7-4770k total:244 pass:216 dwarn:0 dfail:0 fail:8 skip:20
> fi-kbl-qkkr total:244 pass:179 dwarn:29 dfail:0 fail:8 skip:28
> fi-skl-i5-6260u total:244 pass:224 dwarn:0 dfail:0 fail:8 skip:12
> fi-skl-i7-6700k total:244 pass:210 dwarn:0 dfail:0 fail:8 skip:26
> fi-snb-i7-2600 total:244 pass:196 dwarn:0 dfail:0 fail:8 skip:40
> ro-bdw-i5-5250u total:244 pass:219 dwarn:4 dfail:0 fail:8 skip:13
> ro-bdw-i7-5600u total:244 pass:204 dwarn:0 dfail:0 fail:8 skip:32
> ro-bsw-n3050 total:218 pass:173 dwarn:0 dfail:0 fail:2 skip:42
> ro-byt-n2820 total:244 pass:197 dwarn:0 dfail:0 fail:9 skip:38
> ro-hsw-i3-4010u total:244 pass:212 dwarn:0 dfail:0 fail:8 skip:24
> ro-hsw-i7-4770r total:244 pass:212 dwarn:0 dfail:0 fail:8 skip:24
> ro-ilk-i7-620lm total:244 pass:172 dwarn:0 dfail:0 fail:9 skip:63
> ro-ilk1-i5-650 total:239 pass:172 dwarn:0 dfail:0 fail:9 skip:58
> ro-ivb-i7-3770 total:244 pass:203 dwarn:0 dfail:0 fail:8 skip:33
> ro-skl3-i5-6260u total:244 pass:224 dwarn:0 dfail:0 fail:8 skip:12
> ro-snb-i7-2620M total:244 pass:193 dwarn:0 dfail:0 fail:9 skip:42
> ro-bdw-i7-5557U failed to connect after reboot
>
> Results at /archive/results/CI_IGT_test/RO_Patchwork_1565/
>
> cf82f46 drm-intel-nightly: 2016y-07m-21d-20h-43m-36s UTC integration manifest
> 45411d3 drm/i915/guc: re-optimise i915_guc_client layout
> c6b2ad6 drm/i915/guc: use for_each_engine_id() where appropriate
> df49243 drm/i915/guc: add engine mask to GuC client & pass to GuC
> 1645de9 drm/i915/guc: use a separate GuC client for each engine
> c810e6b drm/i915/guc: refactor guc_init_doorbell_hw()
> ff4f069 drm/i915/guc: doorbell reset should avoid used doorbells
You'll need to send one with "do not merge enabe guc" now that it was
disabled on all platforms due APL issues.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-22 10:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 18:15 [PATCH v2 0/6] drm/i915/guc: use one GuC client per GPU engine Dave Gordon
2016-07-21 18:15 ` [PATCH v2 1/6] drm/i915/guc: doorbell reset should avoid used doorbells Dave Gordon
2016-07-22 10:00 ` Tvrtko Ursulin
2016-07-21 18:15 ` [PATCH v2 2/6] drm/i915/guc: refactor guc_init_doorbell_hw() Dave Gordon
2016-07-22 10:01 ` Tvrtko Ursulin
2016-07-21 18:15 ` [PATCH v2 3/6] drm/i915/guc: use a separate GuC client for each engine Dave Gordon
2016-07-21 18:30 ` Chris Wilson
2016-07-22 10:23 ` Dave Gordon
2016-07-22 21:57 ` Chris Wilson
2016-07-21 18:15 ` [PATCH v2 4/6] drm/i915/guc: add engine mask to GuC client & pass to GuC Dave Gordon
2016-07-21 18:15 ` [PATCH v2 5/6] drm/i915/guc: use for_each_engine_id() where appropriate Dave Gordon
2016-07-22 10:04 ` Tvrtko Ursulin
2016-07-22 10:45 ` Dave Gordon
2016-07-21 18:15 ` [PATCH v2 6/6] drm/i915/guc: re-optimise i915_guc_client layout Dave Gordon
2016-07-22 10:05 ` Tvrtko Ursulin
2016-07-22 6:02 ` ✓ Ro.CI.BAT: success for drm/i915/guc: use one GuC client per GPU engine Patchwork
2016-07-22 10:06 ` Tvrtko Ursulin [this message]
2016-07-22 15:17 ` Dave Gordon
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=5791F037.90908@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=david.s.gordon@intel.com \
--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 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.