* [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream
@ 2020-02-25 13:23 Chris Wilson
2020-02-25 13:30 ` Lionel Landwerlin
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: Chris Wilson @ 2020-02-25 13:23 UTC (permalink / raw)
To: intel-gfx
Inside the general i915_oa_init_reg_state() we avoid using the
perf->mutex. However, we rely on perf->exclusive_stream being valid to
access at that point, and for that we have to control the race with
disabling perf. This relies on the disabling being a heavy barrier that
inspects all active contexts, after marking the perf->exclusive_stream
as not avaiable. This should ensure that there are no more concurrent
accesses to the perf->exclusive_stream as we destroy it.
Mark up the races around the perf->exclusive_stream so that they stand
out much more. (And hopefully we will be running kcsan to start
validating that the only races we have are carefully controlled.)
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
---
drivers/gpu/drm/i915/i915_perf.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
index e34c79df6ebc..0838a12e2dc5 100644
--- a/drivers/gpu/drm/i915/i915_perf.c
+++ b/drivers/gpu/drm/i915/i915_perf.c
@@ -1405,8 +1405,10 @@ static void i915_oa_stream_destroy(struct i915_perf_stream *stream)
/*
* Unset exclusive_stream first, it will be checked while disabling
* the metric set on gen8+.
+ *
+ * See i915_oa_init_reg_state() and lrc_configure_all_contexts()
*/
- perf->exclusive_stream = NULL;
+ WRITE_ONCE(perf->exclusive_stream, NULL);
perf->ops.disable_metric_set(stream);
free_oa_buffer(stream);
@@ -2847,7 +2849,7 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
goto err_oa_buf_alloc;
stream->ops = &i915_oa_stream_ops;
- perf->exclusive_stream = stream;
+ WRITE_ONCE(perf->exclusive_stream, stream);
ret = perf->ops.enable_metric_set(stream);
if (ret) {
@@ -2867,7 +2869,7 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
return 0;
err_enable:
- perf->exclusive_stream = NULL;
+ WRITE_ONCE(perf->exclusive_stream, NULL);
perf->ops.disable_metric_set(stream);
free_oa_buffer(stream);
@@ -2893,12 +2895,11 @@ void i915_oa_init_reg_state(const struct intel_context *ce,
{
struct i915_perf_stream *stream;
- /* perf.exclusive_stream serialised by lrc_configure_all_contexts() */
-
if (engine->class != RENDER_CLASS)
return;
- stream = engine->i915->perf.exclusive_stream;
+ /* perf.exclusive_stream serialised by lrc_configure_all_contexts() */
+ stream = READ_ONCE(engine->i915->perf.exclusive_stream);
/*
* For gen12, only CTX_R_PWR_CLK_STATE needs update, but the caller
* is already doing that, so nothing to be done for gen12 here.
--
2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream
2020-02-25 13:23 [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream Chris Wilson
@ 2020-02-25 13:30 ` Lionel Landwerlin
2020-02-25 13:31 ` Lionel Landwerlin
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Lionel Landwerlin @ 2020-02-25 13:30 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
On 25/02/2020 15:23, Chris Wilson wrote:
> Inside the general i915_oa_init_reg_state() we avoid using the
> perf->mutex. However, we rely on perf->exclusive_stream being valid to
> access at that point, and for that we have to control the race with
> disabling perf. This relies on the disabling being a heavy barrier that
> inspects all active contexts, after marking the perf->exclusive_stream
> as not avaiable. This should ensure that there are no more concurrent
> accesses to the perf->exclusive_stream as we destroy it.
>
> Mark up the races around the perf->exclusive_stream so that they stand
> out much more. (And hopefully we will be running kcsan to start
> validating that the only races we have are carefully controlled.)
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_perf.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index e34c79df6ebc..0838a12e2dc5 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -1405,8 +1405,10 @@ static void i915_oa_stream_destroy(struct i915_perf_stream *stream)
> /*
> * Unset exclusive_stream first, it will be checked while disabling
> * the metric set on gen8+.
> + *
> + * See i915_oa_init_reg_state() and lrc_configure_all_contexts()
> */
> - perf->exclusive_stream = NULL;
> + WRITE_ONCE(perf->exclusive_stream, NULL);
> perf->ops.disable_metric_set(stream);
>
> free_oa_buffer(stream);
> @@ -2847,7 +2849,7 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
> goto err_oa_buf_alloc;
>
> stream->ops = &i915_oa_stream_ops;
> - perf->exclusive_stream = stream;
> + WRITE_ONCE(perf->exclusive_stream, stream);
>
> ret = perf->ops.enable_metric_set(stream);
> if (ret) {
> @@ -2867,7 +2869,7 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
> return 0;
>
> err_enable:
> - perf->exclusive_stream = NULL;
> + WRITE_ONCE(perf->exclusive_stream, NULL);
> perf->ops.disable_metric_set(stream);
>
> free_oa_buffer(stream);
> @@ -2893,12 +2895,11 @@ void i915_oa_init_reg_state(const struct intel_context *ce,
> {
> struct i915_perf_stream *stream;
>
> - /* perf.exclusive_stream serialised by lrc_configure_all_contexts() */
> -
> if (engine->class != RENDER_CLASS)
> return;
>
> - stream = engine->i915->perf.exclusive_stream;
> + /* perf.exclusive_stream serialised by lrc_configure_all_contexts() */
> + stream = READ_ONCE(engine->i915->perf.exclusive_stream);
> /*
> * For gen12, only CTX_R_PWR_CLK_STATE needs update, but the caller
> * is already doing that, so nothing to be done for gen12 here.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream
2020-02-25 13:23 [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream Chris Wilson
2020-02-25 13:30 ` Lionel Landwerlin
@ 2020-02-25 13:31 ` Lionel Landwerlin
2020-02-25 14:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Lionel Landwerlin @ 2020-02-25 13:31 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Actually, what about drivers/gpu/drm/i915/gt/intel_sseu.c?
-Lionel
On 25/02/2020 15:23, Chris Wilson wrote:
> Inside the general i915_oa_init_reg_state() we avoid using the
> perf->mutex. However, we rely on perf->exclusive_stream being valid to
> access at that point, and for that we have to control the race with
> disabling perf. This relies on the disabling being a heavy barrier that
> inspects all active contexts, after marking the perf->exclusive_stream
> as not avaiable. This should ensure that there are no more concurrent
> accesses to the perf->exclusive_stream as we destroy it.
>
> Mark up the races around the perf->exclusive_stream so that they stand
> out much more. (And hopefully we will be running kcsan to start
> validating that the only races we have are carefully controlled.)
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> ---
> drivers/gpu/drm/i915/i915_perf.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index e34c79df6ebc..0838a12e2dc5 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -1405,8 +1405,10 @@ static void i915_oa_stream_destroy(struct i915_perf_stream *stream)
> /*
> * Unset exclusive_stream first, it will be checked while disabling
> * the metric set on gen8+.
> + *
> + * See i915_oa_init_reg_state() and lrc_configure_all_contexts()
> */
> - perf->exclusive_stream = NULL;
> + WRITE_ONCE(perf->exclusive_stream, NULL);
> perf->ops.disable_metric_set(stream);
>
> free_oa_buffer(stream);
> @@ -2847,7 +2849,7 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
> goto err_oa_buf_alloc;
>
> stream->ops = &i915_oa_stream_ops;
> - perf->exclusive_stream = stream;
> + WRITE_ONCE(perf->exclusive_stream, stream);
>
> ret = perf->ops.enable_metric_set(stream);
> if (ret) {
> @@ -2867,7 +2869,7 @@ static int i915_oa_stream_init(struct i915_perf_stream *stream,
> return 0;
>
> err_enable:
> - perf->exclusive_stream = NULL;
> + WRITE_ONCE(perf->exclusive_stream, NULL);
> perf->ops.disable_metric_set(stream);
>
> free_oa_buffer(stream);
> @@ -2893,12 +2895,11 @@ void i915_oa_init_reg_state(const struct intel_context *ce,
> {
> struct i915_perf_stream *stream;
>
> - /* perf.exclusive_stream serialised by lrc_configure_all_contexts() */
> -
> if (engine->class != RENDER_CLASS)
> return;
>
> - stream = engine->i915->perf.exclusive_stream;
> + /* perf.exclusive_stream serialised by lrc_configure_all_contexts() */
> + stream = READ_ONCE(engine->i915->perf.exclusive_stream);
> /*
> * For gen12, only CTX_R_PWR_CLK_STATE needs update, but the caller
> * is already doing that, so nothing to be done for gen12 here.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/perf: Mark up the racy use of perf->exclusive_stream
2020-02-25 13:23 [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream Chris Wilson
2020-02-25 13:30 ` Lionel Landwerlin
2020-02-25 13:31 ` Lionel Landwerlin
@ 2020-02-25 14:51 ` Patchwork
2020-02-25 15:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-26 16:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
4 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2020-02-25 14:51 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/perf: Mark up the racy use of perf->exclusive_stream
URL : https://patchwork.freedesktop.org/series/73905/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
0dd2fa185616 drm/i915/perf: Mark up the racy use of perf->exclusive_stream
-:11: WARNING:TYPO_SPELLING: 'avaiable' may be misspelled - perhaps 'available'?
#11:
as not avaiable. This should ensure that there are no more concurrent
total: 0 errors, 1 warnings, 0 checks, 41 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/perf: Mark up the racy use of perf->exclusive_stream
2020-02-25 13:23 [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream Chris Wilson
` (2 preceding siblings ...)
2020-02-25 14:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
@ 2020-02-25 15:32 ` Patchwork
2020-02-26 16:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
4 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2020-02-25 15:32 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/perf: Mark up the racy use of perf->exclusive_stream
URL : https://patchwork.freedesktop.org/series/73905/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8004 -> Patchwork_16703
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/index.html
Known issues
------------
Here are the changes found in Patchwork_16703 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-tgl-y: [PASS][1] -> [FAIL][2] ([CI#94])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8004/fi-tgl-y/igt@gem_exec_suspend@basic-s4-devices.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/fi-tgl-y/igt@gem_exec_suspend@basic-s4-devices.html
* igt@i915_selftest@live_gem_contexts:
- fi-cml-s: [PASS][3] -> [DMESG-FAIL][4] ([i915#877])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8004/fi-cml-s/igt@i915_selftest@live_gem_contexts.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/fi-cml-s/igt@i915_selftest@live_gem_contexts.html
* igt@vgem_basic@dmabuf-export:
- fi-tgl-y: [PASS][5] -> [DMESG-WARN][6] ([CI#94] / [i915#402]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8004/fi-tgl-y/igt@vgem_basic@dmabuf-export.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/fi-tgl-y/igt@vgem_basic@dmabuf-export.html
#### Possible fixes ####
* igt@i915_selftest@live_execlists:
- fi-icl-y: [INCOMPLETE][7] ([i915#140]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8004/fi-icl-y/igt@i915_selftest@live_execlists.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/fi-icl-y/igt@i915_selftest@live_execlists.html
* igt@kms_addfb_basic@addfb25-bad-modifier:
- fi-tgl-y: [DMESG-WARN][9] ([CI#94] / [i915#402]) -> [PASS][10] +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8004/fi-tgl-y/igt@kms_addfb_basic@addfb25-bad-modifier.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/fi-tgl-y/igt@kms_addfb_basic@addfb25-bad-modifier.html
* igt@kms_chamelium@dp-edid-read:
- fi-cml-u2: [FAIL][11] ([i915#217] / [i915#976]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8004/fi-cml-u2/igt@kms_chamelium@dp-edid-read.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/fi-cml-u2/igt@kms_chamelium@dp-edid-read.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[CI#94]: https://gitlab.freedesktop.org/gfx-ci/i915-infra/issues/94
[i915#1233]: https://gitlab.freedesktop.org/drm/intel/issues/1233
[i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140
[i915#217]: https://gitlab.freedesktop.org/drm/intel/issues/217
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#877]: https://gitlab.freedesktop.org/drm/intel/issues/877
[i915#976]: https://gitlab.freedesktop.org/drm/intel/issues/976
Participating hosts (43 -> 43)
------------------------------
Additional (8): fi-ehl-1 fi-skl-6770hq fi-ilk-650 fi-snb-2520m fi-gdg-551 fi-elk-e7500 fi-blb-e6850 fi-skl-6600u
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-glk-dsi fi-byt-squawks fi-byt-clapper fi-bsw-nick fi-bdw-samus fi-snb-2600
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8004 -> Patchwork_16703
CI-20190529: 20190529
CI_DRM_8004: 1a2e0cce5af4a9ad9694995610ed64578ccc430f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5464: 8cf2f8684992052ab89de1cf328c418224c0c2a7 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16703: 0dd2fa1856167d951facb19c40185fb2929cf67d @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
0dd2fa185616 drm/i915/perf: Mark up the racy use of perf->exclusive_stream
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/perf: Mark up the racy use of perf->exclusive_stream
2020-02-25 13:23 [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream Chris Wilson
` (3 preceding siblings ...)
2020-02-25 15:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
@ 2020-02-26 16:10 ` Patchwork
4 siblings, 0 replies; 6+ messages in thread
From: Patchwork @ 2020-02-26 16:10 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/perf: Mark up the racy use of perf->exclusive_stream
URL : https://patchwork.freedesktop.org/series/73905/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8004_full -> Patchwork_16703_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_16703_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_16703_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_16703_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_tiled_blits@normal:
- shard-apl: NOTRUN -> [TIMEOUT][1] +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/shard-apl3/igt@gem_tiled_blits@normal.html
* igt@i915_pm_rpm@pm-tiling:
- shard-iclb: NOTRUN -> [SKIP][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/shard-iclb2/igt@i915_pm_rpm@pm-tiling.html
* igt@sw_sync@sync_multi_producer_single_consumer:
- shard-kbl: NOTRUN -> [TIMEOUT][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/shard-kbl2/igt@sw_sync@sync_multi_producer_single_consumer.html
- shard-skl: NOTRUN -> [TIMEOUT][4] +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/shard-skl5/igt@sw_sync@sync_multi_producer_single_consumer.html
- shard-glk: NOTRUN -> [TIMEOUT][5]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/shard-glk4/igt@sw_sync@sync_multi_producer_single_consumer.html
Participating hosts (8 -> 10)
------------------------------
Additional (2): pig-skl-6260u pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_8004 -> Patchwork_16703
* Piglit: None -> piglit_4509
CI-20190529: 20190529
CI_DRM_8004: 1a2e0cce5af4a9ad9694995610ed64578ccc430f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5464: 8cf2f8684992052ab89de1cf328c418224c0c2a7 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_16703: 0dd2fa1856167d951facb19c40185fb2929cf67d @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_16703/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-02-26 16:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-25 13:23 [Intel-gfx] [PATCH] drm/i915/perf: Mark up the racy use of perf->exclusive_stream Chris Wilson
2020-02-25 13:30 ` Lionel Landwerlin
2020-02-25 13:31 ` Lionel Landwerlin
2020-02-25 14:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-02-25 15:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-26 16:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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.