* [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
@ 2021-10-25 16:34 ` Matthew Brost
0 siblings, 0 replies; 11+ messages in thread
From: Matthew Brost @ 2021-10-25 16:34 UTC (permalink / raw)
To: intel-gfx, dri-devel
Cc: joonas.lahtinen, daniele.ceraolospurio, john.c.harrison
Hide the guc_id and tail fields, for request trace points, behind
CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
are ABI (maybe?) so don't change them without kernel developers Kconfig
options.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
index 9795f456cccf..4f5238d02b51 100644
--- a/drivers/gpu/drm/i915/i915_trace.h
+++ b/drivers/gpu/drm/i915/i915_trace.h
@@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
__entry->ctx, __entry->seqno, __entry->flags)
);
+#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
DECLARE_EVENT_CLASS(i915_request,
TP_PROTO(struct i915_request *rq),
TP_ARGS(rq),
@@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
__entry->guc_id, __entry->ctx, __entry->seqno,
__entry->tail)
);
+#else
+DECLARE_EVENT_CLASS(i915_request,
+ TP_PROTO(struct i915_request *rq),
+ TP_ARGS(rq),
+
+ TP_STRUCT__entry(
+ __field(u32, dev)
+ __field(u64, ctx)
+ __field(u16, class)
+ __field(u16, instance)
+ __field(u32, seqno)
+ ),
+
+ TP_fast_assign(
+ __entry->dev = rq->engine->i915->drm.primary->index;
+ __entry->class = rq->engine->uabi_class;
+ __entry->instance = rq->engine->uabi_instance;
+ __entry->ctx = rq->fence.context;
+ __entry->seqno = rq->fence.seqno;
+ ),
+
+ TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
+ __entry->dev, __entry->class, __entry->instance,
+ __entry->ctx, __entry->seqno)
+);
+#endif
DEFINE_EVENT(i915_request, i915_request_add,
TP_PROTO(struct i915_request *rq),
--
2.32.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [Intel-gfx] [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
@ 2021-10-25 16:34 ` Matthew Brost
0 siblings, 0 replies; 11+ messages in thread
From: Matthew Brost @ 2021-10-25 16:34 UTC (permalink / raw)
To: intel-gfx, dri-devel
Cc: joonas.lahtinen, daniele.ceraolospurio, john.c.harrison
Hide the guc_id and tail fields, for request trace points, behind
CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
are ABI (maybe?) so don't change them without kernel developers Kconfig
options.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
index 9795f456cccf..4f5238d02b51 100644
--- a/drivers/gpu/drm/i915/i915_trace.h
+++ b/drivers/gpu/drm/i915/i915_trace.h
@@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
__entry->ctx, __entry->seqno, __entry->flags)
);
+#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
DECLARE_EVENT_CLASS(i915_request,
TP_PROTO(struct i915_request *rq),
TP_ARGS(rq),
@@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
__entry->guc_id, __entry->ctx, __entry->seqno,
__entry->tail)
);
+#else
+DECLARE_EVENT_CLASS(i915_request,
+ TP_PROTO(struct i915_request *rq),
+ TP_ARGS(rq),
+
+ TP_STRUCT__entry(
+ __field(u32, dev)
+ __field(u64, ctx)
+ __field(u16, class)
+ __field(u16, instance)
+ __field(u32, seqno)
+ ),
+
+ TP_fast_assign(
+ __entry->dev = rq->engine->i915->drm.primary->index;
+ __entry->class = rq->engine->uabi_class;
+ __entry->instance = rq->engine->uabi_instance;
+ __entry->ctx = rq->fence.context;
+ __entry->seqno = rq->fence.seqno;
+ ),
+
+ TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
+ __entry->dev, __entry->class, __entry->instance,
+ __entry->ctx, __entry->seqno)
+);
+#endif
DEFINE_EVENT(i915_request, i915_request_add,
TP_PROTO(struct i915_request *rq),
--
2.32.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/trace: Hide backend specific fields behind Kconfig
2021-10-25 16:34 ` [Intel-gfx] " Matthew Brost
(?)
@ 2021-10-25 18:36 ` Patchwork
-1 siblings, 0 replies; 11+ messages in thread
From: Patchwork @ 2021-10-25 18:36 UTC (permalink / raw)
To: Matthew Brost; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/trace: Hide backend specific fields behind Kconfig
URL : https://patchwork.freedesktop.org/series/96258/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
621c2565d8e5 drm/i915/trace: Hide backend specific fields behind Kconfig
-:31: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#31: FILE: drivers/gpu/drm/i915/i915_trace.h:822:
+DECLARE_EVENT_CLASS(i915_request,
+ TP_PROTO(struct i915_request *rq),
-:34: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#34: FILE: drivers/gpu/drm/i915/i915_trace.h:825:
+ TP_STRUCT__entry(
-:42: CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#42: FILE: drivers/gpu/drm/i915/i915_trace.h:833:
+ TP_fast_assign(
total: 0 errors, 0 warnings, 3 checks, 39 lines checked
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/trace: Hide backend specific fields behind Kconfig
2021-10-25 16:34 ` [Intel-gfx] " Matthew Brost
(?)
(?)
@ 2021-10-25 19:08 ` Patchwork
-1 siblings, 0 replies; 11+ messages in thread
From: Patchwork @ 2021-10-25 19:08 UTC (permalink / raw)
To: Matthew Brost; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 3798 bytes --]
== Series Details ==
Series: drm/i915/trace: Hide backend specific fields behind Kconfig
URL : https://patchwork.freedesktop.org/series/96258/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10787 -> Patchwork_21440
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/index.html
Participating hosts (42 -> 37)
------------------------------
Missing (5): bat-dg1-6 fi-hsw-4200u fi-bsw-cyan bat-adlp-4 fi-ctg-p8600
Known issues
------------
Here are the changes found in Patchwork_21440 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@prime_vgem@basic-userptr:
- fi-pnv-d510: NOTRUN -> [SKIP][1] ([fdo#109271]) +48 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/fi-pnv-d510/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-bdw-5557u: NOTRUN -> [FAIL][2] ([i915#1602] / [i915#2426] / [i915#4312])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/fi-bdw-5557u/igt@runner@aborted.html
#### Possible fixes ####
* igt@gem_exec_parallel@engines@userptr:
- fi-pnv-d510: [INCOMPLETE][3] ([i915#299]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/fi-pnv-d510/igt@gem_exec_parallel@engines@userptr.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/fi-pnv-d510/igt@gem_exec_parallel@engines@userptr.html
* igt@gem_exec_suspend@basic-s3:
- fi-bdw-5557u: [INCOMPLETE][5] -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3.html
* igt@i915_module_load@reload:
- {fi-tgl-dsi}: [DMESG-WARN][7] ([i915#1982]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/fi-tgl-dsi/igt@i915_module_load@reload.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/fi-tgl-dsi/igt@i915_module_load@reload.html
* igt@i915_selftest@live@hangcheck:
- {fi-jsl-1}: [DMESG-FAIL][9] -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/fi-jsl-1/igt@i915_selftest@live@hangcheck.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/fi-jsl-1/igt@i915_selftest@live@hangcheck.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#299]: https://gitlab.freedesktop.org/drm/intel/issues/299
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
Build changes
-------------
* Linux: CI_DRM_10787 -> Patchwork_21440
CI-20190529: 20190529
CI_DRM_10787: d93fcfcb1caac6d1299830be20e5bd5cf8451c71 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6260: 46994310410404a07d142f33fab220d718c27f64 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21440: 621c2565d8e5b7b234c53d9e0dffd1f175437fdc @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
621c2565d8e5 drm/i915/trace: Hide backend specific fields behind Kconfig
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/index.html
[-- Attachment #2: Type: text/html, Size: 4421 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
2021-10-25 16:34 ` [Intel-gfx] " Matthew Brost
@ 2021-10-25 21:06 ` John Harrison
-1 siblings, 0 replies; 11+ messages in thread
From: John Harrison @ 2021-10-25 21:06 UTC (permalink / raw)
To: Matthew Brost, intel-gfx, dri-devel
Cc: joonas.lahtinen, daniele.ceraolospurio
On 10/25/2021 09:34, Matthew Brost wrote:
> Hide the guc_id and tail fields, for request trace points, behind
> CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
> are ABI (maybe?) so don't change them without kernel developers Kconfig
> options.
The i915 sw arch team have previously hard blocked requests for changes
to trace points from user land tool developers on the grounds that trace
points are not ABI and are free to change at whim as and when the i915
internal implementation changes. They are purely for use of developers
to debug the i915 driver as the i915 driver currently stands at any
given instant.
So I don't see how it can be argued that we must not update any trace
points to allow for debugging of i915 scheduling issues on current
platforms. And having to enable extra config options just to keep
existing higher level trace points usable seems broken.
John.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index 9795f456cccf..4f5238d02b51 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
> __entry->ctx, __entry->seqno, __entry->flags)
> );
>
> +#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
> DECLARE_EVENT_CLASS(i915_request,
> TP_PROTO(struct i915_request *rq),
> TP_ARGS(rq),
> @@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
> __entry->guc_id, __entry->ctx, __entry->seqno,
> __entry->tail)
> );
> +#else
> +DECLARE_EVENT_CLASS(i915_request,
> + TP_PROTO(struct i915_request *rq),
> + TP_ARGS(rq),
> +
> + TP_STRUCT__entry(
> + __field(u32, dev)
> + __field(u64, ctx)
> + __field(u16, class)
> + __field(u16, instance)
> + __field(u32, seqno)
> + ),
> +
> + TP_fast_assign(
> + __entry->dev = rq->engine->i915->drm.primary->index;
> + __entry->class = rq->engine->uabi_class;
> + __entry->instance = rq->engine->uabi_instance;
> + __entry->ctx = rq->fence.context;
> + __entry->seqno = rq->fence.seqno;
> + ),
> +
> + TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
> + __entry->dev, __entry->class, __entry->instance,
> + __entry->ctx, __entry->seqno)
> +);
> +#endif
>
> DEFINE_EVENT(i915_request, i915_request_add,
> TP_PROTO(struct i915_request *rq),
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
@ 2021-10-25 21:06 ` John Harrison
0 siblings, 0 replies; 11+ messages in thread
From: John Harrison @ 2021-10-25 21:06 UTC (permalink / raw)
To: Matthew Brost, intel-gfx, dri-devel
Cc: joonas.lahtinen, daniele.ceraolospurio
On 10/25/2021 09:34, Matthew Brost wrote:
> Hide the guc_id and tail fields, for request trace points, behind
> CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
> are ABI (maybe?) so don't change them without kernel developers Kconfig
> options.
The i915 sw arch team have previously hard blocked requests for changes
to trace points from user land tool developers on the grounds that trace
points are not ABI and are free to change at whim as and when the i915
internal implementation changes. They are purely for use of developers
to debug the i915 driver as the i915 driver currently stands at any
given instant.
So I don't see how it can be argued that we must not update any trace
points to allow for debugging of i915 scheduling issues on current
platforms. And having to enable extra config options just to keep
existing higher level trace points usable seems broken.
John.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index 9795f456cccf..4f5238d02b51 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
> __entry->ctx, __entry->seqno, __entry->flags)
> );
>
> +#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
> DECLARE_EVENT_CLASS(i915_request,
> TP_PROTO(struct i915_request *rq),
> TP_ARGS(rq),
> @@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
> __entry->guc_id, __entry->ctx, __entry->seqno,
> __entry->tail)
> );
> +#else
> +DECLARE_EVENT_CLASS(i915_request,
> + TP_PROTO(struct i915_request *rq),
> + TP_ARGS(rq),
> +
> + TP_STRUCT__entry(
> + __field(u32, dev)
> + __field(u64, ctx)
> + __field(u16, class)
> + __field(u16, instance)
> + __field(u32, seqno)
> + ),
> +
> + TP_fast_assign(
> + __entry->dev = rq->engine->i915->drm.primary->index;
> + __entry->class = rq->engine->uabi_class;
> + __entry->instance = rq->engine->uabi_instance;
> + __entry->ctx = rq->fence.context;
> + __entry->seqno = rq->fence.seqno;
> + ),
> +
> + TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
> + __entry->dev, __entry->class, __entry->instance,
> + __entry->ctx, __entry->seqno)
> +);
> +#endif
>
> DEFINE_EVENT(i915_request, i915_request_add,
> TP_PROTO(struct i915_request *rq),
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/trace: Hide backend specific fields behind Kconfig
2021-10-25 16:34 ` [Intel-gfx] " Matthew Brost
` (3 preceding siblings ...)
(?)
@ 2021-10-25 23:59 ` Patchwork
-1 siblings, 0 replies; 11+ messages in thread
From: Patchwork @ 2021-10-25 23:59 UTC (permalink / raw)
To: Matthew Brost; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 28172 bytes --]
== Series Details ==
Series: drm/i915/trace: Hide backend specific fields behind Kconfig
URL : https://patchwork.freedesktop.org/series/96258/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10787_full -> Patchwork_21440_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in Patchwork_21440_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-glk: NOTRUN -> [FAIL][1] ([i915#2842])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][2] -> [FAIL][3] ([i915#2842])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-tglb2/igt@gem_exec_fair@basic-pace-share@rcs0.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-tglb7/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-iclb: [PASS][4] -> [FAIL][5] ([i915#2842])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb6/igt@gem_exec_fair@basic-pace-solo@rcs0.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb2/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_huc_copy@huc-copy:
- shard-skl: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@gem_huc_copy@huc-copy.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-skl: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#3323])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [PASS][8] -> [DMESG-WARN][9] ([i915#1436] / [i915#716])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl3/igt@gen9_exec_parse@allowed-single.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl9/igt@gen9_exec_parse@allowed-single.html
* igt@i915_module_load@reload-no-display:
- shard-iclb: [PASS][10] -> [DMESG-WARN][11] ([i915#2867])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb6/igt@i915_module_load@reload-no-display.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb2/igt@i915_module_load@reload-no-display.html
* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [PASS][12] -> [FAIL][13] ([i915#454])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb7/igt@i915_pm_dc@dc6-dpms.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html
- shard-skl: NOTRUN -> [FAIL][14] ([i915#454])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl4/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-kbl: NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#1937])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl4/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html
* igt@i915_pm_rpm@modeset-lpsp-stress:
- shard-apl: NOTRUN -> [SKIP][16] ([fdo#109271]) +10 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-apl7/igt@i915_pm_rpm@modeset-lpsp-stress.html
* igt@i915_selftest@live@gt_pm:
- shard-skl: NOTRUN -> [DMESG-FAIL][17] ([i915#1886] / [i915#2291])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl4/igt@i915_selftest@live@gt_pm.html
* igt@i915_selftest@live@hangcheck:
- shard-snb: [PASS][18] -> [INCOMPLETE][19] ([i915#3921])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-snb2/igt@i915_selftest@live@hangcheck.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-snb6/igt@i915_selftest@live@hangcheck.html
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [FAIL][20] ([i915#3743]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl4/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [FAIL][21] ([i915#3763])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
* igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#3886]) +2 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl4/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][23] ([fdo#109271] / [i915#3886]) +8 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][24] ([fdo#109271] / [i915#3886]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-apl7/igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][25] ([fdo#109271] / [i915#3886]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_chamelium@dp-crc-multiple:
- shard-skl: NOTRUN -> [SKIP][26] ([fdo#109271] / [fdo#111827]) +12 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_chamelium@dp-crc-multiple.html
* igt@kms_chamelium@hdmi-crc-single:
- shard-apl: NOTRUN -> [SKIP][27] ([fdo#109271] / [fdo#111827])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-apl7/igt@kms_chamelium@hdmi-crc-single.html
* igt@kms_chamelium@hdmi-hpd-with-enabled-mode:
- shard-kbl: NOTRUN -> [SKIP][28] ([fdo#109271] / [fdo#111827]) +8 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl3/igt@kms_chamelium@hdmi-hpd-with-enabled-mode.html
* igt@kms_chamelium@vga-edid-read:
- shard-glk: NOTRUN -> [SKIP][29] ([fdo#109271] / [fdo#111827]) +3 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@kms_chamelium@vga-edid-read.html
* igt@kms_color@pipe-d-ctm-max:
- shard-skl: NOTRUN -> [SKIP][30] ([fdo#109271]) +176 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_color@pipe-d-ctm-max.html
* igt@kms_content_protection@lic:
- shard-kbl: NOTRUN -> [TIMEOUT][31] ([i915#1319])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl3/igt@kms_content_protection@lic.html
* igt@kms_cursor_legacy@pipe-d-single-bo:
- shard-skl: NOTRUN -> [SKIP][32] ([fdo#109271] / [i915#533])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_cursor_legacy@pipe-d-single-bo.html
* igt@kms_draw_crc@draw-method-xrgb2101010-mmap-wc-untiled:
- shard-skl: [PASS][33] -> [DMESG-WARN][34] ([i915#1982]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl9/igt@kms_draw_crc@draw-method-xrgb2101010-mmap-wc-untiled.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl9/igt@kms_draw_crc@draw-method-xrgb2101010-mmap-wc-untiled.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [PASS][35] -> [INCOMPLETE][36] ([i915#180] / [i915#1982])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-apl6/igt@kms_fbcon_fbt@fbc-suspend.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-apl8/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@2x-flip-vs-expired-vblank@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][37] -> [FAIL][38] ([i915#2122]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-glk8/igt@kms_flip@2x-flip-vs-expired-vblank@ab-hdmi-a1-hdmi-a2.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@kms_flip@2x-flip-vs-expired-vblank@ab-hdmi-a1-hdmi-a2.html
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [PASS][39] -> [DMESG-WARN][40] ([i915#180]) +7 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl3/igt@kms_flip@flip-vs-suspend@c-dp1.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl1/igt@kms_flip@flip-vs-suspend@c-dp1.html
- shard-apl: [PASS][41] -> [DMESG-WARN][42] ([i915#180]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-apl3/igt@kms_flip@flip-vs-suspend@c-dp1.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-apl4/igt@kms_flip@flip-vs-suspend@c-dp1.html
* igt@kms_flip@plain-flip-ts-check@b-edp1:
- shard-skl: [PASS][43] -> [FAIL][44] ([i915#2122])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl1/igt@kms_flip@plain-flip-ts-check@b-edp1.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl3/igt@kms_flip@plain-flip-ts-check@b-edp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs:
- shard-skl: NOTRUN -> [INCOMPLETE][45] ([i915#3699])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-render:
- shard-tglb: NOTRUN -> [SKIP][46] ([fdo#111825])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-tglb3/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-shrfb-msflip-blt:
- shard-glk: NOTRUN -> [SKIP][47] ([fdo#109271]) +34 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-shrfb-msflip-blt.html
* igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
- shard-kbl: NOTRUN -> [FAIL][48] ([i915#265])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl4/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: NOTRUN -> [FAIL][49] ([fdo#108145] / [i915#265]) +2 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-skl: NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#2733])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl4/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5:
- shard-kbl: NOTRUN -> [SKIP][51] ([fdo#109271] / [i915#658]) +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl4/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-3:
- shard-glk: NOTRUN -> [SKIP][52] ([fdo#109271] / [i915#658])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-3.html
* igt@kms_psr2_su@frontbuffer:
- shard-skl: NOTRUN -> [SKIP][53] ([fdo#109271] / [i915#658]) +3 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [PASS][54] -> [SKIP][55] ([fdo#109441])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb8/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_writeback@writeback-check-output:
- shard-kbl: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#2437])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl3/igt@kms_writeback@writeback-check-output.html
- shard-glk: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#2437])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@kms_writeback@writeback-check-output.html
* igt@perf@blocking:
- shard-skl: [PASS][58] -> [FAIL][59] ([i915#1542])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl9/igt@perf@blocking.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl4/igt@perf@blocking.html
* igt@sysfs_clients@busy:
- shard-skl: NOTRUN -> [SKIP][60] ([fdo#109271] / [i915#2994]) +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl10/igt@sysfs_clients@busy.html
* igt@sysfs_clients@pidname:
- shard-glk: NOTRUN -> [SKIP][61] ([fdo#109271] / [i915#2994])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@sysfs_clients@pidname.html
- shard-kbl: NOTRUN -> [SKIP][62] ([fdo#109271] / [i915#2994]) +1 similar issue
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl3/igt@sysfs_clients@pidname.html
* igt@tools_test@sysfs_l3_parity:
- shard-kbl: NOTRUN -> [SKIP][63] ([fdo#109271]) +71 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl3/igt@tools_test@sysfs_l3_parity.html
#### Possible fixes ####
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [FAIL][64] ([i915#2842]) -> [PASS][65]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-tglb3/igt@gem_exec_fair@basic-none-share@rcs0.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-tglb2/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][66] ([i915#2842]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl4/igt@gem_exec_fair@basic-none@vcs0.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl1/igt@gem_exec_fair@basic-none@vcs0.html
- shard-iclb: [FAIL][68] ([i915#2842]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb8/igt@gem_exec_fair@basic-none@vcs0.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb7/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][70] ([i915#2842]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-glk1/igt@gem_exec_fair@basic-pace-share@rcs0.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk9/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_whisper@basic-fds-priority-all:
- shard-glk: [DMESG-WARN][72] ([i915#118]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-glk6/igt@gem_exec_whisper@basic-fds-priority-all.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk5/igt@gem_exec_whisper@basic-fds-priority-all.html
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [SKIP][74] ([i915#2190]) -> [PASS][75]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-tglb7/igt@gem_huc_copy@huc-copy.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-tglb8/igt@gem_huc_copy@huc-copy.html
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][76] ([i915#454]) -> [PASS][77]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb6/igt@i915_pm_dc@dc6-psr.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb2/igt@i915_pm_dc@dc6-psr.html
* igt@kms_concurrent@pipe-a:
- shard-skl: [DMESG-WARN][78] ([i915#1982]) -> [PASS][79]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl9/igt@kms_concurrent@pipe-a.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl4/igt@kms_concurrent@pipe-a.html
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [DMESG-WARN][80] ([i915#180]) -> [PASS][81] +2 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-suspend.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [FAIL][82] ([i915#2346] / [i915#533]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl8/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl8/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-toggle:
- shard-iclb: [FAIL][84] ([i915#2346]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb7/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb3/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-apl: [DMESG-WARN][86] ([i915#180]) -> [PASS][87] +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-apl6/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-apl7/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
- shard-iclb: [SKIP][88] ([i915#3701]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb8/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [SKIP][90] ([fdo#109441]) -> [PASS][91] +1 similar issue
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb6/igt@kms_psr@psr2_cursor_plane_onoff.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_setmode@basic:
- shard-glk: [FAIL][92] ([i915#31]) -> [PASS][93]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-glk2/igt@kms_setmode@basic.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk5/igt@kms_setmode@basic.html
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: [WARN][94] ([i915#1804] / [i915#2684]) -> [WARN][95] ([i915#2684])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb7/igt@i915_pm_rc6_residency@rc6-fence.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb8/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-glk: [DMESG-WARN][96] ([i915#118]) -> [DMESG-WARN][97] ([i915#118] / [i915#1982])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-glk8/igt@kms_big_fb@linear-32bpp-rotate-180.html
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-glk2/igt@kms_big_fb@linear-32bpp-rotate-180.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-2:
- shard-iclb: [SKIP][98] ([i915#658]) -> [SKIP][99] ([i915#2920]) +1 similar issue
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb6/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-2.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb2/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-2.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5:
- shard-iclb: [SKIP][100] ([i915#2920]) -> [SKIP][101] ([i915#658]) +1 similar issue
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-iclb8/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][102], [FAIL][103], [FAIL][104], [FAIL][105], [FAIL][106], [FAIL][107], [FAIL][108], [FAIL][109], [FAIL][110], [FAIL][111]) ([fdo#109271] / [i915#180] / [i915#1814] / [i915#3002] / [i915#3363] / [i915#4312] / [i915#602] / [i915#92]) -> ([FAIL][112], [FAIL][113], [FAIL][114], [FAIL][115], [FAIL][116], [FAIL][117], [FAIL][118], [FAIL][119], [FAIL][120], [FAIL][121]) ([fdo#109271] / [i915#1436] / [i915#180] / [i915#1814] / [i915#3002] / [i915#3363] / [i915#4312] / [i915#602] / [i915#92])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl7/igt@runner@aborted.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl1/igt@runner@aborted.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl7/igt@runner@aborted.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl6/igt@runner@aborted.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl6/igt@runner@aborted.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl6/igt@runner@aborted.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl6/igt@runner@aborted.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl6/igt@runner@aborted.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl7/igt@runner@aborted.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-kbl7/igt@runner@aborted.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl1/igt@runner@aborted.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl4/igt@runner@aborted.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl7/igt@runner@aborted.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl6/igt@runner@aborted.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl1/igt@runner@aborted.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl6/igt@runner@aborted.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl7/igt@runner@aborted.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl1/igt@runner@aborted.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl7/igt@runner@aborted.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-kbl7/igt@runner@aborted.html
- shard-skl: ([FAIL][122], [FAIL][123]) ([i915#3002] / [i915#3363] / [i915#4312]) -> ([FAIL][124], [FAIL][125], [FAIL][126]) ([i915#1436] / [i915#3002] / [i915#3363] / [i915#4312])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl3/igt@runner@aborted.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10787/shard-skl2/igt@runner@aborted.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl1/igt@runner@aborted.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl9/igt@runner@aborted.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21440/shard-skl8/igt@runner@aborted.html
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2733]: https://gitlab.freedesktop.org/drm/intel/issues/2733
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#3699]: https://gitlab.freedesktop.org/drm/intel/issues/3699
[i915#3701]: https://gitlab.freedesktop.org/drm/intel/issues/3701
[i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743
[i915#3763]: https://gitlab.freedesktop.org/drm/intel/issues/3763
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#602]: https://gitlab.freedesktop.org/drm/intel/issues/602
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
Build changes
-------------
* Linux: CI_DRM_10787 -> Patchwork_21440
CI-20190529: 20190529
CI_DRM_10787: d93fcfcb1caac6d1299830be20e5bd5cf8451c71 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6260: 46994310410404a07d142f33fab220d718c27f64 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21440: 621c2565d8e5b7b234c53d9e0dffd1f175437fdc @ 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_21440/index.html
[-- Attachment #2: Type: text/html, Size: 36140 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
2021-10-25 21:06 ` [Intel-gfx] " John Harrison
@ 2021-10-26 9:11 ` Joonas Lahtinen
-1 siblings, 0 replies; 11+ messages in thread
From: Joonas Lahtinen @ 2021-10-26 9:11 UTC (permalink / raw)
To: John Harrison, Matthew Brost, dri-devel, intel-gfx; +Cc: daniele.ceraolospurio
Quoting John Harrison (2021-10-26 00:06:54)
> On 10/25/2021 09:34, Matthew Brost wrote:
> > Hide the guc_id and tail fields, for request trace points, behind
> > CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
> > are ABI (maybe?) so don't change them without kernel developers Kconfig
> > options.
> The i915 sw arch team have previously hard blocked requests for changes
> to trace points from user land tool developers on the grounds that trace
> points are not ABI and are free to change at whim as and when the i915
> internal implementation changes. They are purely for use of developers
> to debug the i915 driver as the i915 driver currently stands at any
> given instant.
Correct. That is indicated by the LOW_LEVEL_TRACEPOINTS.
All the discussions about stable usage really revolve around the low level
backend specific scheduling tracepoints to analyze hardware utilization.
And those even become infeasible to expose when GuC scheduling is enabled
as the information really goes to GuC log.
Luckily we have added the mechanism to get the actual utilization
through OA via gpuvis tool, so we don't have to guesstimate it from the
KMD scheduling tracepoints (which are for KMD debugging).
> So I don't see how it can be argued that we must not update any trace
> points to allow for debugging of i915 scheduling issues on current
> platforms. And having to enable extra config options just to keep
> existing higher level trace points usable seems broken.
We can update them (even outside LOW_LEVEL_TRACEPOINTS) but there should
not be any backend specific data added outside the LOW_LEVEL_TRACEPOINTS,
just to prevent anyone from starting to use them in some
visualization/analysis tooling.
If you have the energy to drive the general LKML/Linux Plumbers level
discussion about tracepoint stability limbo into a conclusion, I'll be
more than happy to see it resolved :)
Regards, Joonas
>
> John.
>
>
> >
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
> > 1 file changed, 27 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> > index 9795f456cccf..4f5238d02b51 100644
> > --- a/drivers/gpu/drm/i915/i915_trace.h
> > +++ b/drivers/gpu/drm/i915/i915_trace.h
> > @@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
> > __entry->ctx, __entry->seqno, __entry->flags)
> > );
> >
> > +#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
> > DECLARE_EVENT_CLASS(i915_request,
> > TP_PROTO(struct i915_request *rq),
> > TP_ARGS(rq),
> > @@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
> > __entry->guc_id, __entry->ctx, __entry->seqno,
> > __entry->tail)
> > );
> > +#else
> > +DECLARE_EVENT_CLASS(i915_request,
> > + TP_PROTO(struct i915_request *rq),
> > + TP_ARGS(rq),
> > +
> > + TP_STRUCT__entry(
> > + __field(u32, dev)
> > + __field(u64, ctx)
> > + __field(u16, class)
> > + __field(u16, instance)
> > + __field(u32, seqno)
> > + ),
> > +
> > + TP_fast_assign(
> > + __entry->dev = rq->engine->i915->drm.primary->index;
> > + __entry->class = rq->engine->uabi_class;
> > + __entry->instance = rq->engine->uabi_instance;
> > + __entry->ctx = rq->fence.context;
> > + __entry->seqno = rq->fence.seqno;
> > + ),
> > +
> > + TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
> > + __entry->dev, __entry->class, __entry->instance,
> > + __entry->ctx, __entry->seqno)
> > +);
> > +#endif
> >
> > DEFINE_EVENT(i915_request, i915_request_add,
> > TP_PROTO(struct i915_request *rq),
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
@ 2021-10-26 9:11 ` Joonas Lahtinen
0 siblings, 0 replies; 11+ messages in thread
From: Joonas Lahtinen @ 2021-10-26 9:11 UTC (permalink / raw)
To: John Harrison, Matthew Brost, dri-devel, intel-gfx; +Cc: daniele.ceraolospurio
Quoting John Harrison (2021-10-26 00:06:54)
> On 10/25/2021 09:34, Matthew Brost wrote:
> > Hide the guc_id and tail fields, for request trace points, behind
> > CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
> > are ABI (maybe?) so don't change them without kernel developers Kconfig
> > options.
> The i915 sw arch team have previously hard blocked requests for changes
> to trace points from user land tool developers on the grounds that trace
> points are not ABI and are free to change at whim as and when the i915
> internal implementation changes. They are purely for use of developers
> to debug the i915 driver as the i915 driver currently stands at any
> given instant.
Correct. That is indicated by the LOW_LEVEL_TRACEPOINTS.
All the discussions about stable usage really revolve around the low level
backend specific scheduling tracepoints to analyze hardware utilization.
And those even become infeasible to expose when GuC scheduling is enabled
as the information really goes to GuC log.
Luckily we have added the mechanism to get the actual utilization
through OA via gpuvis tool, so we don't have to guesstimate it from the
KMD scheduling tracepoints (which are for KMD debugging).
> So I don't see how it can be argued that we must not update any trace
> points to allow for debugging of i915 scheduling issues on current
> platforms. And having to enable extra config options just to keep
> existing higher level trace points usable seems broken.
We can update them (even outside LOW_LEVEL_TRACEPOINTS) but there should
not be any backend specific data added outside the LOW_LEVEL_TRACEPOINTS,
just to prevent anyone from starting to use them in some
visualization/analysis tooling.
If you have the energy to drive the general LKML/Linux Plumbers level
discussion about tracepoint stability limbo into a conclusion, I'll be
more than happy to see it resolved :)
Regards, Joonas
>
> John.
>
>
> >
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
> > 1 file changed, 27 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> > index 9795f456cccf..4f5238d02b51 100644
> > --- a/drivers/gpu/drm/i915/i915_trace.h
> > +++ b/drivers/gpu/drm/i915/i915_trace.h
> > @@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
> > __entry->ctx, __entry->seqno, __entry->flags)
> > );
> >
> > +#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
> > DECLARE_EVENT_CLASS(i915_request,
> > TP_PROTO(struct i915_request *rq),
> > TP_ARGS(rq),
> > @@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
> > __entry->guc_id, __entry->ctx, __entry->seqno,
> > __entry->tail)
> > );
> > +#else
> > +DECLARE_EVENT_CLASS(i915_request,
> > + TP_PROTO(struct i915_request *rq),
> > + TP_ARGS(rq),
> > +
> > + TP_STRUCT__entry(
> > + __field(u32, dev)
> > + __field(u64, ctx)
> > + __field(u16, class)
> > + __field(u16, instance)
> > + __field(u32, seqno)
> > + ),
> > +
> > + TP_fast_assign(
> > + __entry->dev = rq->engine->i915->drm.primary->index;
> > + __entry->class = rq->engine->uabi_class;
> > + __entry->instance = rq->engine->uabi_instance;
> > + __entry->ctx = rq->fence.context;
> > + __entry->seqno = rq->fence.seqno;
> > + ),
> > +
> > + TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
> > + __entry->dev, __entry->class, __entry->instance,
> > + __entry->ctx, __entry->seqno)
> > +);
> > +#endif
> >
> > DEFINE_EVENT(i915_request, i915_request_add,
> > TP_PROTO(struct i915_request *rq),
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
2021-10-25 16:34 ` [Intel-gfx] " Matthew Brost
@ 2021-10-27 11:24 ` Joonas Lahtinen
-1 siblings, 0 replies; 11+ messages in thread
From: Joonas Lahtinen @ 2021-10-27 11:24 UTC (permalink / raw)
To: Matthew Brost, dri-devel, intel-gfx
Cc: daniele.ceraolospurio, john.c.harrison
Quoting Matthew Brost (2021-10-25 19:34:04)
> Hide the guc_id and tail fields, for request trace points, behind
> CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
> are ABI (maybe?) so don't change them without kernel developers Kconfig
> options.
I've pushed the simple fix to eliminate the 'guc_id' field.
In my opinion a separate tracepoint with more information would be a
better choice here compared to mutating an existing one.
The idea with LOW_LEVEL_TRACEPOINTS is to make sure there are two sets
of tracepoints: one that is quasi stable and the other that is unstable.
Mutating the other set when the unstable set is enabled kind of breaks
that clean split.
Regards, Joonas
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index 9795f456cccf..4f5238d02b51 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
> __entry->ctx, __entry->seqno, __entry->flags)
> );
>
> +#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
> DECLARE_EVENT_CLASS(i915_request,
> TP_PROTO(struct i915_request *rq),
> TP_ARGS(rq),
> @@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
> __entry->guc_id, __entry->ctx, __entry->seqno,
> __entry->tail)
> );
> +#else
> +DECLARE_EVENT_CLASS(i915_request,
> + TP_PROTO(struct i915_request *rq),
> + TP_ARGS(rq),
> +
> + TP_STRUCT__entry(
> + __field(u32, dev)
> + __field(u64, ctx)
> + __field(u16, class)
> + __field(u16, instance)
> + __field(u32, seqno)
> + ),
> +
> + TP_fast_assign(
> + __entry->dev = rq->engine->i915->drm.primary->index;
> + __entry->class = rq->engine->uabi_class;
> + __entry->instance = rq->engine->uabi_instance;
> + __entry->ctx = rq->fence.context;
> + __entry->seqno = rq->fence.seqno;
> + ),
> +
> + TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
> + __entry->dev, __entry->class, __entry->instance,
> + __entry->ctx, __entry->seqno)
> +);
> +#endif
>
> DEFINE_EVENT(i915_request, i915_request_add,
> TP_PROTO(struct i915_request *rq),
> --
> 2.32.0
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig
@ 2021-10-27 11:24 ` Joonas Lahtinen
0 siblings, 0 replies; 11+ messages in thread
From: Joonas Lahtinen @ 2021-10-27 11:24 UTC (permalink / raw)
To: Matthew Brost, dri-devel, intel-gfx
Cc: daniele.ceraolospurio, john.c.harrison
Quoting Matthew Brost (2021-10-25 19:34:04)
> Hide the guc_id and tail fields, for request trace points, behind
> CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option. Trace points
> are ABI (maybe?) so don't change them without kernel developers Kconfig
> options.
I've pushed the simple fix to eliminate the 'guc_id' field.
In my opinion a separate tracepoint with more information would be a
better choice here compared to mutating an existing one.
The idea with LOW_LEVEL_TRACEPOINTS is to make sure there are two sets
of tracepoints: one that is quasi stable and the other that is unstable.
Mutating the other set when the unstable set is enabled kind of breaks
that clean split.
Regards, Joonas
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/i915/i915_trace.h | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
> index 9795f456cccf..4f5238d02b51 100644
> --- a/drivers/gpu/drm/i915/i915_trace.h
> +++ b/drivers/gpu/drm/i915/i915_trace.h
> @@ -787,6 +787,7 @@ TRACE_EVENT(i915_request_queue,
> __entry->ctx, __entry->seqno, __entry->flags)
> );
>
> +#if defined(CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS)
> DECLARE_EVENT_CLASS(i915_request,
> TP_PROTO(struct i915_request *rq),
> TP_ARGS(rq),
> @@ -816,6 +817,32 @@ DECLARE_EVENT_CLASS(i915_request,
> __entry->guc_id, __entry->ctx, __entry->seqno,
> __entry->tail)
> );
> +#else
> +DECLARE_EVENT_CLASS(i915_request,
> + TP_PROTO(struct i915_request *rq),
> + TP_ARGS(rq),
> +
> + TP_STRUCT__entry(
> + __field(u32, dev)
> + __field(u64, ctx)
> + __field(u16, class)
> + __field(u16, instance)
> + __field(u32, seqno)
> + ),
> +
> + TP_fast_assign(
> + __entry->dev = rq->engine->i915->drm.primary->index;
> + __entry->class = rq->engine->uabi_class;
> + __entry->instance = rq->engine->uabi_instance;
> + __entry->ctx = rq->fence.context;
> + __entry->seqno = rq->fence.seqno;
> + ),
> +
> + TP_printk("dev=%u, engine=%u:%u, ctx=%llu, seqno=%u",
> + __entry->dev, __entry->class, __entry->instance,
> + __entry->ctx, __entry->seqno)
> +);
> +#endif
>
> DEFINE_EVENT(i915_request, i915_request_add,
> TP_PROTO(struct i915_request *rq),
> --
> 2.32.0
>
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2021-10-27 11:24 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-25 16:34 [PATCH] drm/i915/trace: Hide backend specific fields behind Kconfig Matthew Brost
2021-10-25 16:34 ` [Intel-gfx] " Matthew Brost
2021-10-25 18:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-10-25 19:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-25 21:06 ` [PATCH] " John Harrison
2021-10-25 21:06 ` [Intel-gfx] " John Harrison
2021-10-26 9:11 ` Joonas Lahtinen
2021-10-26 9:11 ` [Intel-gfx] " Joonas Lahtinen
2021-10-25 23:59 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2021-10-27 11:24 ` [PATCH] " Joonas Lahtinen
2021-10-27 11:24 ` [Intel-gfx] " Joonas Lahtinen
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.