fdinfo: Enable some support for GuC based client busyness
Subsystems (2)
cover fdinfo: Enable some support for GuC based client busyness
Export context runtime into the fdinfo framework to enable per client busyness for GuC back-end.
v2: Fix zeroed busyness values
v3: Include review comments from Ashutosh
Umesh Nerlige Ramappa (2):
i915/pmu: Add support for total context runtime for GuC back-end drm/i915/fdinfo: Enable fdinfo for GuC backends
drivers/gpu/drm/i915/gt/intel_context.c | 5 ++- drivers/gpu/drm/i915/gt/intel_context.h | 2 +- drivers/gpu/drm/i915/gt/intel_context_types.h | 2 ++ .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 31 +++++++++++++++++++ drivers/gpu/drm/i915/i915_drm_client.c | 6 +--- 5 files changed, 39 insertions(+), 7 deletions(-)
Signature · 1 line
2.36.1
PATCH 1/2 i915/pmu: Add support for total context runtime for GuC back-end
GPU accumulates the context runtime in a 32 bit counter - CTX_TIMESTAMP in the context image. This value is saved/restored on context switches. KMD accumulates these values into a 64 bit counter taking care of any overflows as needed. This count provides the basis for client specific busyness in the fdinfo interface.
KMD accumulation happens just before the context is unpinned and when context switches out. This works for execlist back-end since execlist scheduling has visibility into context switches. With GuC mode, KMD does not have visibility into context switches and this counter is accumulated only when context is unpinned. Context is unpinned once the context scheduling is successfully disabled. Disabling context scheduling is an asynchronous operation. Also if a context is servicing frequent requests, scheduling may never be disabled on it.
For GuC mode, since updates to the context runtime may be delayed, add hooks to update the context runtime in a worker thread as well as when a user queries for it.
Limitation:
- If a context is never switched out or runs for a long period of time, the runtime value of CTX_TIMESTAMP may never be updated, so the counter value may be unreliable. This patch does not support such cases. Such support must be available from the GuC FW and it is WIP.
This patch is an extract from previous work authored by John/Umesh here -
https://patchwork.freedesktop.org/patch/496441/?series=105085&rev=4
v2: (Ashutosh)
- Drop COPS_RUNTIME_ACTIVE_TOTAL
- s/guc_context_update_clks/__guc_context_update_stats
- Pin context before accessing in guc_timestamp_ping
- In guc_context_unpin, use spinlock to serialize access to runtime stats
--- drivers/gpu/drm/i915/gt/intel_context.c | 5 ++- drivers/gpu/drm/i915/gt/intel_context.h | 2 +- drivers/gpu/drm/i915/gt/intel_context_types.h | 2 ++ .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 31 +++++++++++++++++++ 4 files changed, 38 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/gt/intel_context.c +4 -1
@@ -578,10 +578,13 @@ void intel_context_bind_parent_child(struct intel_context *parent, child->parallel.parent = parent; } -u64 intel_context_get_total_runtime_ns (const struct intel_context *ce) +u64 intel_context_get_total_runtime_ns (struct intel_context *ce) {u64 total, active; +if (ce->ops->update_stats) + ce->ops->update_stats (ce); + total = ce->stats.runtime.total;if (ce->ops->flags &COPS_RUNTIME_CYCLES ) total *= ce->engine->gt->clock_period_ns;
drivers/gpu/drm/i915/gt/intel_context.h +1 -1
@@ -375,7 +375,7 @@ intel_context_clear_nopreempt(struct intel_context *ce)clear_bit (CONTEXT_NOPREEMPT , &ce->flags); } -u64 intel_context_get_total_runtime_ns (const struct intel_context *ce); +u64 intel_context_get_total_runtime_ns (struct intel_context *ce);u64 intel_context_get_avg_runtime_ns (struct intel_context *ce);static inline u64 intel_context_clock (void )
drivers/gpu/drm/i915/gt/intel_context_types.h +2 -0
@@ -58,6 +58,8 @@ struct intel_context_ops {void (*sched_disable)(struct intel_context *ce); +void (*update_stats)(struct intel_context *ce); +void (*reset)(struct intel_context *ce);void (*destroy)(struct kref *kref);
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +31 -0
@@ -1402,13 +1402,34 @@ static void __update_guc_busyness_stats(struct intel_guc *guc)spin_unlock_irqrestore (&guc->timestamp.lock, flags); } +static void __guc_context_update_stats (struct intel_context *ce) +{ +struct intel_guc *guc =ce_to_guc (ce); +unsigned long flags; + +spin_lock_irqsave (&guc->timestamp.lock, flags); +lrc_update_runtime (ce); +spin_unlock_irqrestore (&guc->timestamp.lock, flags); +} + +static void guc_context_update_stats (struct intel_context *ce) +{ +if (!intel_context_pin_if_active (ce)) +return ; + +__guc_context_update_stats (ce); +intel_context_unpin (ce); +} +static void guc_timestamp_ping (struct work_struct *wrk) {struct intel_guc *guc =container_of (wrk,typeof (*guc), timestamp.work.work);struct intel_uc *uc =container_of (guc,typeof (*uc), guc);struct intel_gt *gt =guc_to_gt (guc); +struct intel_context *ce;intel_wakeref_t wakeref; +unsigned long index;int srcu, ret;/*
@@ -1424,6 +1445,10 @@ static void guc_timestamp_ping(struct work_struct *wrk) with_intel_runtime_pm(>->i915->runtime_pm, wakeref)__update_guc_busyness_stats (guc); +/* adjust context stats for overflow */ +xa_for_each (&guc->context_lookup, index, ce) +guc_context_update_stats (ce); +intel_gt_reset_unlock (gt, srcu);guc_enable_busyness_worker (guc);
@@ -2774,6 +2799,7 @@ static void guc_context_unpin(struct intel_context *ce) {struct intel_guc *guc =ce_to_guc (ce); +__guc_context_update_stats (ce);unpin_guc_id (guc, ce);lrc_unpin (ce);
@@ -3455,6 +3481,7 @@ static void remove_from_context(struct i915_request *rq) }static const struct intel_context_ops guc_context_ops = { + .flags =COPS_RUNTIME_CYCLES , .alloc = guc_context_alloc, .close = guc_context_close,
@@ -3473,6 +3500,8 @@ static const struct intel_context_ops guc_context_ops = { .sched_disable = guc_context_sched_disable, + .update_stats = guc_context_update_stats, + .reset = lrc_reset, .destroy = guc_context_destroy,
@@ -3728,6 +3757,7 @@ static int guc_virtual_context_alloc(struct intel_context *ce) }static const struct intel_context_ops virtual_guc_context_ops = { + .flags =COPS_RUNTIME_CYCLES , .alloc = guc_virtual_context_alloc, .close = guc_context_close,
@@ -3745,6 +3775,7 @@ static const struct intel_context_ops virtual_guc_context_ops = { .exit = guc_virtual_context_exit, .sched_disable = guc_context_sched_disable, + .update_stats = guc_context_update_stats, .destroy = guc_context_destroy,
Signature · 1 line
2.36.1
Re: [Intel-gfx] [PATCH 1/2] i915/pmu: Add support for total context runtime for GuC back-end
Quoted 26 lines · Umesh Nerlige Ramappa
GPU accumulates the context runtime in a 32 bit counter -
CTX_TIMESTAMPin the context image. This value is saved/restored on context switches. KMD accumulates these values into a 64 bit counter taking care of any overflows as needed. This count provides the basis for client specific busyness in the fdinfo interface.KMD accumulation happens just before the context is unpinned and when context switches out. This works for execlist back-end since execlist scheduling has visibility into context switches. With GuC mode, KMD does not have visibility into context switches and this counter is accumulated only when context is unpinned. Context is unpinned once the context scheduling is successfully disabled. Disabling context scheduling is an asynchronous operation. Also if a context is servicing frequent requests, scheduling may never be disabled on it.
For GuC mode, since updates to the context runtime may be delayed, add hooks to update the context runtime in a worker thread as well as when a user queries for it.
Limitation:
- If a context is never switched out or runs for a long period of time, the runtime value ofCTX_TIMESTAMPmay never be updated, so the counter value may be unreliable. This patch does not support such cases. Such support must be available from the GuC FW and it is WIP.
Quoted 8 lines
This patch is an extract from previous work authored by John/Umesh here -
https://patchwork.freedesktop.org/patch/496441/?series=105085&rev=4v2: (Ashutosh)
- DropCOPS_RUNTIME_ACTIVE_TOTAL
- s/guc_context_update_clks/__guc_context_update_stats
- Pin context before accessing inguc_timestamp_ping
- Inguc_context_unpin, use spinlock to serialize access to runtime stats
LGTM now:
I have made a few notes for myself below.
Quoted 16 lines
Signed-off-by Umesh Nerlige Ramappa <[email protected]>Co-developed-by John Harrison <[email protected]>Signed-off-by John Harrison <[email protected]>--- drivers/gpu/drm/i915/gt/intel_context.c | 5 ++- drivers/gpu/drm/i915/gt/intel_context.h | 2 +- drivers/gpu/drm/i915/gt/intel_context_types.h | 2 ++ .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 31 +++++++++++++++++++ 4 files changed, 38 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gt/intel_context.c +0
-0
drivers/gpu/drm/i915/gt/intel_context.c void intel_context_bind_parent_child(struct intel_context *parent, · line 586
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_context.c +3
-1@@ -578,10 +578,13 @@ void intel_context_bind_parent_child(struct intel_context *parent, child->parallel.parent = parent; } -u64 intel_context_get_total_runtime_ns (const struct intel_context *ce) +u64 intel_context_get_total_runtime_ns (struct intel_context *ce) {u64 total, active; +if (ce->ops->update_stats) + ce->ops->update_stats (ce);
This is indeed called from atomic context due to rcu_read_lock in show_client_class, so we can't sleep in update_stats (and we are not due to use of intel_context_pin_if_active).
Because we are already updating stats from guc_timestamp_ping, we could have skipped updating them again from here without losing too much accuracy but it's fine.
Quoted 41 lines
drivers/gpu/drm/i915/gt/intel_context.c +1
-0+ total = ce->stats.runtime.total;if (ce->ops->flags &COPS_RUNTIME_CYCLES ) total *= ce->engine->gt->clock_period_ns;drivers/gpu/drm/i915/gt/intel_context.h +1
-1@@ -375,7 +375,7 @@ intel_context_clear_nopreempt(struct intel_context *ce)clear_bit (CONTEXT_NOPREEMPT , &ce->flags); } -u64 intel_context_get_total_runtime_ns (const struct intel_context *ce); +u64 intel_context_get_total_runtime_ns (struct intel_context *ce);u64 intel_context_get_avg_runtime_ns (struct intel_context *ce);static inline u64 intel_context_clock (void )drivers/gpu/drm/i915/gt/intel_context_types.h +2
-0@@ -58,6 +58,8 @@ struct intel_context_ops {void (*sched_disable)(struct intel_context *ce); +void (*update_stats)(struct intel_context *ce); +void (*reset)(struct intel_context *ce);void (*destroy)(struct kref *kref);drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +3
-0@@ -1402,13 +1402,34 @@ static void __update_guc_busyness_stats(struct intel_guc *guc)spin_unlock_irqrestore (&guc->timestamp.lock, flags); } +static void __guc_context_update_stats (struct intel_context *ce) +{ +struct intel_guc *guc =ce_to_guc (ce);
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c static void __update_guc_busyness_stats(struct intel_guc *guc) · line 1417
Quoted 10 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +10
-0+unsigned long flags; + +spin_lock_irqsave (&guc->timestamp.lock, flags); +lrc_update_runtime (ce); +spin_unlock_irqrestore (&guc->timestamp.lock, flags); +} + +static void guc_context_update_stats (struct intel_context *ce) +{ +if (!intel_context_pin_if_active (ce))
Correct, all we need here is intel_context_pin_if_active. If the context is not pinned we updated stats when we unpinned.
Quoted 19 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +8
-0+return ; + +__guc_context_update_stats (ce); +intel_context_unpin (ce); +} +static void guc_timestamp_ping (struct work_struct *wrk) {struct intel_guc *guc =container_of (wrk,typeof (*guc), timestamp.work.work);struct intel_uc *uc =container_of (guc,typeof (*uc), guc);struct intel_gt *gt =guc_to_gt (guc); +struct intel_context *ce;intel_wakeref_t wakeref; +unsigned long index;int srcu, ret;/*
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c static void guc_timestamp_ping(struct work_struct *wrk) · line 1450
Quoted 6 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +3
-0@@ -1424,6 +1445,10 @@ static void guc_timestamp_ping(struct work_struct *wrk) with_intel_runtime_pm(>->i915->runtime_pm, wakeref)__update_guc_busyness_stats (guc); +/* adjust context stats for overflow */ +xa_for_each (&guc->context_lookup, index, ce) +guc_context_update_stats (ce);
This helps prevent overflow if the context switched out (which updated the runtime in the context image) but was not not unpinned.
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c static void guc_context_unpin(struct intel_context *ce) · line 2802
Quoted 9 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +2
-0+intel_gt_reset_unlock (gt, srcu);guc_enable_busyness_worker (guc);@@ -2774,6 +2799,7 @@ static void guc_context_unpin(struct intel_context *ce) {struct intel_guc *guc =ce_to_guc (ce); +__guc_context_update_stats (ce);
Correct, cannot call intel_context_unpin (from guc_context_update_stats) since this function is called from intel_context_unpin.
Quoted 29 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +4
-0unpin_guc_id (guc, ce);lrc_unpin (ce);@@ -3455,6 +3481,7 @@ static void remove_from_context(struct i915_request *rq) }static const struct intel_context_ops guc_context_ops = { + .flags =COPS_RUNTIME_CYCLES , .alloc = guc_context_alloc, .close = guc_context_close,@@ -3473,6 +3500,8 @@ static const struct intel_context_ops guc_context_ops = { .sched_disable = guc_context_sched_disable, + .update_stats = guc_context_update_stats, + .reset = lrc_reset, .destroy = guc_context_destroy,@@ -3728,6 +3757,7 @@ static int guc_virtual_context_alloc(struct intel_context *ce) }static const struct intel_context_ops virtual_guc_context_ops = { + .flags =COPS_RUNTIME_CYCLES , .alloc = guc_virtual_context_alloc, .close = guc_context_close,
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c static const struct intel_context_ops virtual_guc_context_ops = { · line 3778
Quoted 4 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +1
-0@@ -3745,6 +3775,7 @@ static const struct intel_context_ops virtual_guc_context_ops = { .exit = guc_virtual_context_exit, .sched_disable = guc_context_sched_disable, + .update_stats = guc_context_update_stats,
The approach should also work for virtual engines.
Quoted 6 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +0
-1.destroy = guc_context_destroy, --2.36.1
Thanks.
--
Ashutosh
PATCH 2/2 drm/i915/fdinfo: Enable fdinfo for GuC backends
In reply to Umesh Nerlige RamappaEnable fdinfo for GuC based platforms with the exception that long running contexts will not provide reliable busyness data unless they switch out at some reasonable point in time.
--- drivers/gpu/drm/i915/i915_drm_client.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)
drivers/gpu/drm/i915/i915_drm_client.c +1 -5
@@ -147,11 +147,7 @@ void i915_drm_client_fdinfo(struct seq_file *m, struct file *f) PCI_SLOT(pdev->devfn), PCI_FUNC(pdev->devfn));seq_printf (m,"drm-client-id:\t%u\n" , client->id); -/* -* Temporarily skip showing client engine information with GuC submission till -* fetching engine busyness is implemented in the GuC submission backend -*/ -if (GRAPHICS_VER (i915) <8 ||intel_uc_uses_guc_submission (&i915->gt0.uc)) +if (GRAPHICS_VER (i915) <8 )return ;for (i =0 ; i <ARRAY_SIZE (uabi_class_names); i++)
Signature · 1 line
2.36.1
Re: [Intel-gfx] [PATCH 2/2] drm/i915/fdinfo: Enable fdinfo for GuC backends
Quoted 18 lines · Umesh Nerlige Ramappa
Enable fdinfo for GuC based platforms with the exception that long running contexts will not provide reliable busyness data unless they switch out at some reasonable point in time.
Signed-off-by Umesh Nerlige Ramappa <[email protected]>--- drivers/gpu/drm/i915/i915_drm_client.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)drivers/gpu/drm/i915/i915_drm_client.c +0
-0@@ -147,11 +147,7 @@ void i915_drm_client_fdinfo(struct seq_file *m, struct file *f) PCI_SLOT(pdev->devfn), PCI_FUNC(pdev->devfn));seq_printf (m,"drm-client-id:\t%u\n" , client->id);
drivers/gpu/drm/i915/i915_drm_client.c void i915_drm_client_fdinfo(struct seq_file *m, struct file *f) · line 153
Quoted 10 lines
drivers/gpu/drm/i915/i915_drm_client.c +1
-5-/* -* Temporarily skip showing client engine information with GuC submission till -* fetching engine busyness is implemented in the GuC submission backend -*/ -if (GRAPHICS_VER (i915) <8 ||intel_uc_uses_guc_submission (&i915->gt0.uc)) +if (GRAPHICS_VER (i915) <8 )return ;for (i =0 ; i <ARRAY_SIZE (uabi_class_names); i++)
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for fdinfo: Enable some support for GuC based client busyness (rev2)
In reply to Umesh Nerlige Ramappa== Series Details ==
== Series Details ==
Series: fdinfo: Enable some support for GuC based client busyness (rev2)
URL : https://patchwork.freedesktop.org/series/116120/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for fdinfo: Enable some support for GuC based client busyness (rev2)
In reply to Umesh Nerlige Ramappa== Series Details ==
== Series Details ==
Series: fdinfo: Enable some support for GuC based client busyness (rev2)
URL : https://patchwork.freedesktop.org/series/116120/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13071 -> Patchwork_116120v2
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/index.html
Participating hosts (38 -> 37)
------------------------------
Additional (1): fi-kbl-soraka
Missing (2): bat-mtlp-8 fi-snb-2520m
Known issues
------------
Here are the changes found in Patchwork_116120v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-kbl-soraka: NOTRUN -> [SKIP][1] ([fdo#109271] / [i915#2190])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/fi-kbl-soraka/igt@[email protected]
* igt@gem_lmem_swapping@basic:
- fi-kbl-soraka: NOTRUN -> [SKIP][2] ([fdo#109271] / [i915#4613]) +3 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/fi-kbl-soraka/igt@[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- fi-kbl-soraka: NOTRUN -> [FAIL][3] ([i915#7916])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: NOTRUN -> [FAIL][4] ([i915#7913] / [i915#8383])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
* igt@i915_selftest@live@migrate:
- bat-atsm-1: [PASS][5] -> [FAIL][6] ([i915#6268] / [i915#7913])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/bat-atsm-1/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/bat-atsm-1/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@slpc:
- bat-rplp-1: [PASS][7] -> [FAIL][8] ([i915#7913])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/bat-rplp-1/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/bat-rplp-1/igt@i915_selftest@[email protected]
* igt@kms_chamelium_frames@hdmi-crc-fast:
- fi-kbl-soraka: NOTRUN -> [SKIP][9] ([fdo#109271]) +16 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/fi-kbl-soraka/igt@[email protected]
* igt@kms_chamelium_hpd@common-hpd-after-suspend:
- bat-rpls-1: NOTRUN -> [SKIP][10] ([i915#7828])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/bat-rpls-1/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc:
- bat-rpls-1: NOTRUN -> [SKIP][11] ([i915#1845])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/bat-rpls-1/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3@smem:
- bat-rpls-1: [ABORT][12] ([i915#6687]) -> [PASS][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/bat-rpls-1/igt@gem_exec_suspend@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/bat-rpls-1/igt@gem_exec_suspend@[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- fi-glk-j4005: [FAIL][14] ([i915#7916]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/fi-glk-j4005/igt@i915_selftest@live@gt_heartbeat.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/fi-glk-j4005/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@requests:
- {bat-mtlp-6}: [ABORT][16] ([i915#7920]) -> [PASS][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/bat-mtlp-6/igt@i915_selftest@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/bat-mtlp-6/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@slpc:
- bat-rpls-1: [FAIL][18] ([i915#6997]) -> [PASS][19]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/bat-rpls-1/igt@i915_selftest@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/bat-rpls-1/igt@i915_selftest@[email protected]
#### Warnings ####
* igt@core_hotunplug@unbind-rebind:
- fi-kbl-8809g: [ABORT][20] -> [ABORT][21] ([i915#8397])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/fi-kbl-8809g/igt@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/fi-kbl-8809g/igt@[email protected]
{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
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6645]: https://gitlab.freedesktop.org/drm/intel/issues/6645
[i915#6687]: https://gitlab.freedesktop.org/drm/intel/issues/6687
[i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#7913]: https://gitlab.freedesktop.org/drm/intel/issues/7913
[i915#7916]: https://gitlab.freedesktop.org/drm/intel/issues/7916
[i915#7920]: https://gitlab.freedesktop.org/drm/intel/issues/7920
[i915#8383]: https://gitlab.freedesktop.org/drm/intel/issues/8383
[i915#8397]: https://gitlab.freedesktop.org/drm/intel/issues/8397
Build changes
-------------
* Linux: CI_DRM_13071 -> Patchwork_116120v2
CI-20190529: 20190529
CI_DRM_13071: b9458e7075652669ec0e04abe039a5ed001701fe @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7273: f40ef4b058466219968b7792d22ff0648b82396b @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_116120v2: b9458e7075652669ec0e04abe039a5ed001701fe @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
d51aa0d07dd5 drm/i915/fdinfo: Enable fdinfo for GuC backends b4045d3217ac i915/pmu: Add support for total context runtime for GuC back-end
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/index.html
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for fdinfo: Enable some support for GuC based client busyness (rev2)
In reply to Umesh Nerlige Ramappa== Series Details ==
== Series Details ==
Series: fdinfo: Enable some support for GuC based client busyness (rev2)
URL : https://patchwork.freedesktop.org/series/116120/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_13071_full -> Patchwork_116120v2_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (7 -> 7)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_116120v2_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@drm_fdinfo@isolation@vecs0:
- {shard-dg1}: NOTRUN -> [SKIP][1] +39 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-dg1-12/igt@drm_fdinfo@[email protected]
* igt@drm_fdinfo@virtual-busy-all:
- {shard-dg1}: [SKIP][2] ([i915#5563]) -> [SKIP][3] +7 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-dg1-17/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-dg1-13/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_116120v2_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_barrier_race@remote-request@rcs0:
- shard-glk: [PASS][4] -> [ABORT][5] ([i915#7461])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-glk2/igt@gem_barrier_race@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-glk2/igt@gem_barrier_race@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-glk: [PASS][6] -> [FAIL][7] ([i915#2846])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-glk9/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-glk7/igt@[email protected]
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-apl: [PASS][8] -> [FAIL][9] ([i915#2842])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-apl2/igt@gem_exec_fair@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-apl7/igt@gem_exec_fair@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#2190])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-apl2/igt@[email protected]
* igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip:
- shard-apl: NOTRUN -> [SKIP][11] ([fdo#109271]) +25 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-apl2/igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip.html
* igt@kms_cdclk@mode-transition:
- shard-glk: NOTRUN -> [SKIP][12] ([fdo#109271]) +6 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-glk3/igt@[email protected]
* igt@kms_content_protection@atomic@pipe-a-dp-1:
- shard-apl: NOTRUN -> [TIMEOUT][13] ([i915#7173])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-apl2/igt@kms_content_protection@[email protected]
* igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-0-25@pipe-a-hdmi-a-1:
- shard-snb: NOTRUN -> [SKIP][14] ([fdo#109271]) +21 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-snb1/igt@kms_plane_scaling@[email protected]
* igt@kms_psr2_sf@overlay-plane-move-continuous-sf:
- shard-glk: NOTRUN -> [SKIP][15] ([fdo#109271] / [i915#658])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-glk3/igt@[email protected]
#### Possible fixes ####
* igt@drm_fdinfo@most-busy-idle-check-all@rcs0:
- {shard-rkl}: [FAIL][16] ([i915#7742]) -> [PASS][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-rkl-6/igt@drm_fdinfo@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-rkl-1/igt@drm_fdinfo@[email protected]
* igt@drm_fdinfo@virtual-idle:
- {shard-dg1}: [SKIP][18] ([i915#5563]) -> [PASS][19] +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-dg1-17/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-dg1-13/igt@[email protected]
* igt@gem_barrier_race@remote-request@rcs0:
- {shard-dg1}: [ABORT][20] ([i915#7461] / [i915#8234]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-dg1-16/igt@gem_barrier_race@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-dg1-15/igt@gem_barrier_race@[email protected]
* igt@gem_eio@hibernate:
- shard-apl: [ABORT][22] ([i915#8213]) -> [PASS][23]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-apl3/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-apl2/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- {shard-rkl}: [FAIL][24] ([i915#2846]) -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-rkl-7/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-rkl-7/igt@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][26] ([i915#2842]) -> [PASS][27]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-glk2/igt@gem_exec_fair@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-glk2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- {shard-rkl}: [FAIL][28] ([i915#2842]) -> [PASS][29]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-rkl-7/igt@gem_exec_fair@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-rkl-3/igt@gem_exec_fair@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- {shard-dg1}: [FAIL][30] ([i915#3591]) -> [PASS][31]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-dg1-14/igt@i915_pm_rc6_residency@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-dg1-15/igt@i915_pm_rc6_residency@[email protected]
* igt@i915_pm_rpm@modeset-lpsp-stress-no-wait:
- {shard-rkl}: [SKIP][32] ([i915#1397]) -> [PASS][33] +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-rkl-1/igt@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-rkl-7/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-apl: [FAIL][34] ([i915#2346]) -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-apl2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-apl2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_plane@pixel-format@pipe-a-planes:
- shard-glk: [FAIL][36] ([i915#1623]) -> [PASS][37]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13071/shard-glk9/igt@kms_plane@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_116120v2/shard-glk8/igt@kms_plane@[email protected]
{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#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1623]: https://gitlab.freedesktop.org/drm/intel/issues/1623
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354
[i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#7116]: https://gitlab.freedesktop.org/drm/intel/issues/7116
[i915#7173]: https://gitlab.freedesktop.org/drm/intel/issues/7173
[i915#7443]: https://gitlab.freedesktop.org/drm/intel/issues/7443
[i915#7461]: https://gitlab.freedesktop.org/drm/intel/issues/7461
[i915#7742]: https://gitlab.freedesktop.org/drm/intel/issues/7742
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#8011]: https://gitlab.freedesktop.org/drm/intel/issues/8011
[i915#8102]: https://gitlab.freedesktop.org/drm/intel/issues/8102
[i915#8213]: https://gitlab.freedesktop.org/drm/intel/issues/8213
[i915#8234]: https://gitlab.freedesktop.org/drm/intel/issues/8234
[i915#8381]: https://gitlab.freedesktop.org/drm/intel/issues/8381
Build changes
-------------
* Linux: CI_DRM_13071 -> Patchwork_116120v2
CI-20190529: 20190529
CI_DRM_13071: b9458e7075652669ec0e04abe039a5ed001701fe @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7273: f40ef4b058466219968b7792d22ff0648b82396b @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_116120v2: b9458e7075652669ec0e04abe039a5ed001701fe @ 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_116120v2/index.html