Inherit GPU scheduling priority from process nice
Subsystems (2)
cover Inherit GPU scheduling priority from process nice
From: Tvrtko Ursulin <[email protected]>
Current processing landscape seems to be more and more composed of pipelines where computations are done on multiple hardware devices. Furthermore some of the non-CPU devices, like in this case many GPUs supported by the i915 driver, actually support priority based scheduling which is currently rather inaccessible to the user (in terms of being able to control it from the outside).
From these two statements a question arises on how to allow for a simple, effective and consolidated user experience. In other words why user would not be able to do something like:
$ nice ffmmpeg ...transcode my videos... $ my-favourite-game
And have the nice hint apply to GPU parts of the transcode pipeline as well?
This would in fact follow the approach taken by kernel's block scheduler where ionice is by default inherited from process nice.
This series implements the same idea by inheriting context creator and batch buffer submitted nice value as context nice. To avoid influencing GPU scheduling aware clients this is done only one for contexts where userspace hasn't explicitly specified a non-default scheduling priority
With the series applied I simulated the scenario of a background GPU task running simultaneously with an interactive client, varying the hog's nice value. These were the results:
GPU hog (nice) | TRex fps | perf drop
---------------+---------------+------------
no hog | 48.9 | - n/a -
0 | 42.7 | -13%
10 | 47.9 | -2%
-10 | 29.0 | -41%As can be seen running the background GPU task re-niced can restore the performance of the foreground task to almost the level when it is running alone on the machine.
The approach is completely compatible with GuC and drm/scheduler since all support at least low/normal/high priority levels with just the granularity of available control differing. In other words with GuC scheduling there is no difference between nice 5 and 10, both would map to low priority, but the default case of positive or negative nice, versus nice 0, is still correctly propagated to the firmware scheduler.
v2:
* Moved notifier outside task_rq_lock.
* Some improvements and restructuring on the i915 side of the series.
v3:
* Dropped task nice notifier - inheriting nice on request submit time is good enough.
Tvrtko Ursulin (3):
drm/i915: Make some recently added vfuncs use full scheduling
attribute
drm/i915: Inherit process nice for context scheduling priority drm/i915: Inherit submitter nice when scheduling requests
drivers/gpu/drm/i915/gem/i915_gem_context.c | 6 +++++- .../gpu/drm/i915/gt/intel_execlists_submission.c | 6 ++++-- .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 3 ++- drivers/gpu/drm/i915/i915_request.c | 7 +++++-- drivers/gpu/drm/i915/i915_request.h | 5 +++++ drivers/gpu/drm/i915/i915_scheduler.c | 16 ++++++++++------ drivers/gpu/drm/i915/i915_scheduler.h | 14 ++++++++++++++ drivers/gpu/drm/i915/i915_scheduler_types.h | 12 ++++++++++-- 8 files changed, 55 insertions(+), 14 deletions(-)
Signature · 1 line
2.32.0
PATCH 1/3 drm/i915: Make some recently added vfuncs use full scheduling attribute
From: Tvrtko Ursulin <[email protected]>
Code added in 71ed60112d5d ("drm/i915: Add kick_backend function to i915_sched_engine") and ee242ca704d3 ("drm/i915/guc: Implement GuC priority management") introduced some scheduling related vfuncs which take integer request priority as argument.
Make them instead take struct i915_sched_attr which is the type encapsulating this information. This better aligns with the codebase and enables transparently extending the internal data passed along the scheduling call chains.
--- drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 4 +++- drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 3 ++- drivers/gpu/drm/i915/i915_scheduler.c | 4 ++-- drivers/gpu/drm/i915/i915_scheduler_types.h | 4 ++-- 4 files changed, 9 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/gt/intel_execlists_submission.c +3 -1
@@ -3273,11 +3273,13 @@ static bool can_preempt(struct intel_engine_cs *engine)return engine->class !=RENDER_CLASS ; } -static void kick_execlists (const struct i915_request *rq,int prio) +static void kick_execlists (const struct i915_request *rq, +const struct i915_sched_attr *attr) {struct intel_engine_cs *engine = rq->engine;struct i915_sched_engine *sched_engine = engine->sched_engine;const struct i915_request *inflight; +const int prio = attr->priority;/* * We only need to kick the tasklet once for the high priority
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +2 -1
@@ -3520,9 +3520,10 @@ static void guc_init_breadcrumbs(struct intel_engine_cs *engine) }static void guc_bump_inflight_request_prio (struct i915_request *rq, -int prio) +const struct i915_sched_attr *attr) {struct intel_context *ce =request_to_scheduling_context (rq); +const int prio = attr->priority;u8 new_guc_prio =map_i915_prio_to_guc_prio (prio);/* Short circuit function */
drivers/gpu/drm/i915/i915_scheduler.c +2 -2
@@ -255,7 +255,7 @@ static void __i915_schedule(struct i915_sched_node *node,/* Must be called before changing the nodes priority */ if (sched_engine->bump_inflight_request_prio) - sched_engine->bump_inflight_request_prio (from, prio); + sched_engine->bump_inflight_request_prio (from, attr);WRITE_ONCE (node->attr.priority, prio);
@@ -280,7 +280,7 @@ static void __i915_schedule(struct i915_sched_node *node,/* Defer (tasklet) submission until after all of our updates. */ if (sched_engine->kick_backend) - sched_engine->kick_backend (node_to_request (node), prio); + sched_engine->kick_backend (node_to_request (node), attr); }spin_unlock (&sched_engine->lock);
drivers/gpu/drm/i915/i915_scheduler_types.h +2 -2
@@ -177,13 +177,13 @@ struct i915_sched_engine {* @kick_backend: kick backend after a request's priority has changed */ void (*kick_backend)(const struct i915_request *rq, -int prio); +const struct i915_sched_attr *attr);/** * @bump_inflight_request_prio: update priority of an inflight request */ void (*bump_inflight_request_prio)(struct i915_request *rq, -int prio); +const struct i915_sched_attr *attr);/** * @retire_inflight_request_prio: indicate request is retired to
Signature · 1 line
2.32.0
PATCH 2/3 drm/i915: Inherit process nice for context scheduling priority
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Introduce the concept of context nice value which matches the process nice.
We do this by extending the struct i915_sched_attr and add a helper (i915_sched_attr_priority) to be used to convert to effective priority when used by backend code and for priority sorting.
Context nice is then inherited from the process which creates the GEM context and utilised secondary to context priority, but only when the latter has been left at the default setting in order to avoid disturbing any application made choices of low and high (batch processing and maybe latency sensitive compositing). In this case nice value adjusts the effective priority in the narrow band of -19 to +20 around I915_CONTEXT_DEFAULT_PRIORITY.
This means that userspace using the context priority uapi directly has a wider range of possible adjustments (in practice that only applies to execlists platforms - with GuC there are only three priority buckets), but in all cases nice adjustment has the expected effect: positive nice lowering the scheduling priority and negative nice raising it.
--- drivers/gpu/drm/i915/gem/i915_gem_context.c | 6 +++++- .../gpu/drm/i915/gt/intel_execlists_submission.c | 4 ++-- drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 2 +- drivers/gpu/drm/i915/i915_request.c | 2 +- drivers/gpu/drm/i915/i915_request.h | 5 +++++ drivers/gpu/drm/i915/i915_scheduler.c | 12 ++++++++---- drivers/gpu/drm/i915/i915_scheduler.h | 14 ++++++++++++++ drivers/gpu/drm/i915/i915_scheduler_types.h | 8 ++++++++ 8 files changed, 44 insertions(+), 9 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_context.c +5 -1
@@ -294,6 +294,7 @@ proto_context_create(struct drm_i915_private *i915, unsigned int flags)if (i915->params.enable_hangcheck) pc->user_flags |=BIT (UCONTEXT_PERSISTENCE ); pc->sched.priority =I915_PRIORITY_NORMAL ; + pc->sched.nice =task_nice (current);if (flags &I915_CONTEXT_CREATE_FLAGS_SINGLE_TIMELINE ) {if (!HAS_EXECLISTS (i915)) {
@@ -914,8 +915,11 @@ static int set_proto_ctx_param(struct drm_i915_file_private *fpriv,case I915_CONTEXT_PARAM_PRIORITY : ret =validate_priority (fpriv->dev_priv, args); -if (!ret) +if (!ret) { pc->sched.priority = args->value; +if (args->value ==I915_CONTEXT_DEFAULT_PRIORITY ) + pc->sched.nice =task_nice (current); + }break ;case I915_CONTEXT_PARAM_SSEU :
drivers/gpu/drm/i915/gt/intel_execlists_submission.c +2 -2
@@ -254,7 +254,7 @@ static struct i915_priolist *to_priolist(struct rb_node *rb)static int rq_prio (const struct i915_request *rq) { -return READ_ONCE (rq->sched.attr.priority); +return i915_request_priority (rq); }static int effective_prio (const struct i915_request *rq)
@@ -3278,8 +3278,8 @@ static void kick_execlists(const struct i915_request *rq, {struct intel_engine_cs *engine = rq->engine;struct i915_sched_engine *sched_engine = engine->sched_engine; +const int prio =i915_sched_attr_priority (attr);const struct i915_request *inflight; -const int prio = attr->priority;/* * We only need to kick the tasklet once for the high priority
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +1 -1
@@ -3523,7 +3523,7 @@ static void guc_bump_inflight_request_prio(struct i915_request *rq, const struct i915_sched_attr *attr) {struct intel_context *ce =request_to_scheduling_context (rq); -const int prio = attr->priority; +const int prio =i915_sched_attr_priority (attr);u8 new_guc_prio =map_i915_prio_to_guc_prio (prio);/* Short circuit function */
drivers/gpu/drm/i915/i915_request.c +1 -1
@@ -2093,7 +2093,7 @@ static int print_sched_attr(const struct i915_sched_attr *attr,return x; x +=snprintf (buf + x, len - x, -" prio=%d" , attr->priority); +" prio=%d nice=%d" , attr->priority, attr->nice);return x; }
drivers/gpu/drm/i915/i915_request.h +5 -0
@@ -439,6 +439,11 @@ long i915_request_wait(struct i915_request *rq,#define I915_WAIT_PRIORITY BIT(1)/* small priority bump for the request */ #define I915_WAIT_ALL BIT(2)/* used by i915_gem_object_wait() */ +static inline int i915_request_priority (const struct i915_request *rq) +{ +return i915_sched_attr_priority (&rq->sched.attr); +} + void i915_request_show(struct drm_printer *m, const struct i915_request *rq, const char *prefix,
drivers/gpu/drm/i915/i915_scheduler.c +8 -4
@@ -155,7 +155,9 @@ lock_sched_engine(struct i915_sched_node *node,static void __i915_schedule (struct i915_sched_node *node,const struct i915_sched_attr *attr) { -const int prio =max (attr->priority, node->attr.priority); +const int prio = +max (i915_sched_attr_priority (attr), +i915_sched_attr_priority (&node->attr));struct i915_sched_engine *sched_engine;struct i915_dependency *dep, *p;struct i915_dependency stack;
@@ -209,7 +211,7 @@ static void __i915_schedule(struct i915_sched_node *node,if (node_signaled (p->signaler))continue ; -if (prio >READ_ONCE (p->signaler->attr.priority)) +if (prio >i915_sched_attr_priority (&p->signaler->attr))list_move_tail (&p->dfs_link, &dfs); } }
@@ -247,7 +249,8 @@ static void __i915_schedule(struct i915_sched_node *node,lockdep_assert_held (&sched_engine->lock);/* Recheck after acquiring the engine->timeline.lock */ -if (prio <= node->attr.priority ||node_signaled (node)) +if (prio <=i915_sched_attr_priority (&node->attr) || +node_signaled (node))continue ; GEM_BUG_ON(node_to_request(node)->engine->sched_engine !=
@@ -257,7 +260,7 @@ static void __i915_schedule(struct i915_sched_node *node,if (sched_engine->bump_inflight_request_prio) sched_engine->bump_inflight_request_prio (from, attr); -WRITE_ONCE (node->attr.priority, prio); +WRITE_ONCE (node->attr, *attr);/* * Once the request is ready, it will be placed into the
@@ -305,6 +308,7 @@ void i915_sched_node_init(struct i915_sched_node *node)void i915_sched_node_reinit (struct i915_sched_node *node) { node->attr.priority =I915_PRIORITY_INVALID ; + node->attr.nice =0 ; node->semaphores =0 ; node->flags =0 ;
drivers/gpu/drm/i915/i915_scheduler.h +14 -0
@@ -38,6 +38,20 @@ void i915_sched_node_fini(struct i915_sched_node *node);void i915_schedule (struct i915_request *request,const struct i915_sched_attr *attr); +static inline int i915_sched_attr_priority (const struct i915_sched_attr *attr) +{ +int prio = attr->priority; + +/* +* Only allow I915_CONTEXT_DEFAULT_PRIORITY to be affected by the +* nice setting. +*/ +if (!prio) + prio = -attr->nice; + +return prio; +} +struct list_head *i915_sched_lookup_priolist (struct i915_sched_engine *sched_engine,int prio);
drivers/gpu/drm/i915/i915_scheduler_types.h +8 -0
@@ -29,6 +29,14 @@ struct i915_sched_attr {* The &drm_i915_private.kernel_context is assigned the lowest priority. */ int priority; + +/** +* @nice: context nice level +* +* Nice level follows the CPU scheduler nice value as set for the +* process owning the GPU context. +*/ +int nice; };/*
Signature · 1 line
2.32.0
PATCH 3/3 drm/i915: Inherit submitter nice when scheduling requests
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Inherit submitter nice at point of request submission to account for long running processes getting either externally or self re-niced.
Nice value will only apply to requests which originate from user contexts and have default context priority.
--- drivers/gpu/drm/i915/i915_request.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_request.c +4 -1
@@ -1811,8 +1811,11 @@ void i915_request_add(struct i915_request *rq)/* XXX placeholder for selftests */ rcu_read_lock (); ctx =rcu_dereference (rq->context->gem_context); -if (ctx) +if (ctx) { attr = ctx->sched; +if (attr.priority ==I915_CONTEXT_DEFAULT_PRIORITY ) + attr.nice =task_nice (current); + }rcu_read_unlock ();__i915_request_queue (rq, &attr);
Signature · 1 line
2.32.0
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Inherit GPU scheduling priority from process nice
In reply to Tvrtko Ursulin== Series Details ==
== Series Details ==
Series: Inherit GPU scheduling priority from process nice
URL : https://patchwork.freedesktop.org/series/102203/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ded698b30753 drm/i915: Make some recently added vfuncs use full scheduling attribute
-:7: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 71ed60112d5d ("drm/i915: Add kick_backend function to i915_sched_engine")'
#7:
Code added in 71ed60112d5d ("drm/i915: Add kick_backend function to-:8: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit ee242ca704d3 ("drm/i915/guc: Implement GuC priority management")' #8:i915_sched_engine") and ee242ca704d3 ("drm/i915/guc: Implement GuC
total: 2 errors, 0 warnings, 0 checks, 56 lines checked 809fe4fc972b drm/i915: Inherit process nice for context scheduling priority ac9ed0a50032 drm/i915: Inherit submitter nice when scheduling requests
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Inherit GPU scheduling priority from process nice
In reply to Tvrtko Ursulin== Series Details ==
== Series Details ==
Series: Inherit GPU scheduling priority from process nice
URL : https://patchwork.freedesktop.org/series/102203/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✗ Fi.CI.DOCS: warning for Inherit GPU scheduling priority from process nice
In reply to Tvrtko Ursulin== Series Details ==
== Series Details ==
Series: Inherit GPU scheduling priority from process nice
URL : https://patchwork.freedesktop.org/series/102203/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/gem/i915_gem_context_types.h:417: warning: Function parameter or member 'client_link' not described in 'i915_gem_context'
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for Inherit GPU scheduling priority from process nice
In reply to Tvrtko Ursulin== Series Details ==
== Series Details ==
Series: Inherit GPU scheduling priority from process nice
URL : https://patchwork.freedesktop.org/series/102203/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11456 -> Patchwork_22782
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_22782 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_22782, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/index.html
Participating hosts (46 -> 44)
------------------------------
Additional (4): fi-kbl-soraka bat-rpls-1 bat-adlp-4 fi-tgl-u2
Missing (6): shard-tglu fi-bsw-cyan shard-rkl shard-dg1 bat-jsl-2 fi-bdw-samus
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22782:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@gt_heartbeat:
- fi-cfl-guc: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11456/fi-cfl-guc/igt@i915_selftest@live@gt_heartbeat.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-cfl-guc/igt@i915_selftest@live@gt_heartbeat.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@i915_suspend@system-suspend-without-i915}:
- {bat-dg2-8}: NOTRUN -> [INCOMPLETE][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/bat-dg2-8/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_22782 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_cs_nop@sync-fork-compute0:
- fi-snb-2600: NOTRUN -> [SKIP][4] ([fdo#109271]) +17 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-snb-2600/igt@amdgpu/[email protected]
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-kbl-soraka: NOTRUN -> [SKIP][5] ([fdo#109271]) +9 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-kbl-soraka/igt@gem_exec_fence@[email protected]
* igt@gem_huc_copy@huc-copy:
- fi-tgl-u2: NOTRUN -> [SKIP][6] ([i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-u2/igt@[email protected]
- fi-kbl-soraka: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#2190])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-kbl-soraka/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-engines:
- fi-kbl-soraka: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#4613]) +3 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-kbl-soraka/igt@[email protected]
* igt@gem_lmem_swapping@verify-random:
- fi-tgl-u2: NOTRUN -> [SKIP][9] ([i915#4613]) +3 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-u2/igt@[email protected]
* igt@i915_selftest@live@gt_lrc:
- fi-bsw-n3050: [PASS][10] -> [DMESG-FAIL][11] ([i915#2373])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11456/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][12] ([i915#1886])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
* igt@i915_selftest@live@hangcheck:
- bat-dg1-6: NOTRUN -> [DMESG-FAIL][13] ([i915#4494] / [i915#4957])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/bat-dg1-6/igt@i915_selftest@[email protected]
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-tgl-u2: NOTRUN -> [SKIP][14] ([fdo#109284] / [fdo#111827]) +8 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-u2/igt@[email protected]
* igt@kms_chamelium@dp-edid-read:
- fi-kbl-soraka: NOTRUN -> [SKIP][15] ([fdo#109271] / [fdo#111827]) +8 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-kbl-soraka/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-u2: NOTRUN -> [SKIP][16] ([i915#4103]) +1 similar issue
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-u2/igt@[email protected]
* igt@kms_flip@basic-plain-flip@a-edp1:
- fi-tgl-u2: NOTRUN -> [DMESG-WARN][17] ([i915#402]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-u2/igt@kms_flip@[email protected]
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-u2: NOTRUN -> [SKIP][18] ([fdo#109285])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-u2/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-kbl-soraka: NOTRUN -> [SKIP][19] ([fdo#109271] / [i915#533])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-kbl-soraka/igt@[email protected]
* igt@kms_setmode@basic-clone-single-crtc:
- fi-tgl-u2: NOTRUN -> [SKIP][20] ([i915#3555])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-u2/igt@[email protected]
* igt@runner@aborted:
- bat-adlp-4: NOTRUN -> [FAIL][21] ([i915#5457])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/bat-adlp-4/igt@[email protected]
#### Possible fixes ####
* igt@i915_pm_rps@basic-api:
- bat-dg1-6: [FAIL][22] ([i915#4032]) -> [PASS][23]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11456/bat-dg1-6/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/bat-dg1-6/igt@[email protected]
* igt@i915_selftest@live@gt_engines:
- bat-dg1-6: [INCOMPLETE][24] ([i915#4418]) -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11456/bat-dg1-6/igt@i915_selftest@live@gt_engines.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/bat-dg1-6/igt@i915_selftest@live@gt_engines.html
* igt@i915_selftest@live@gt_pm:
- fi-tgl-1115g4: [DMESG-FAIL][26] ([i915#3987]) -> [PASS][27]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11456/fi-tgl-1115g4/igt@i915_selftest@live@gt_pm.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-tgl-1115g4/igt@i915_selftest@live@gt_pm.html
* igt@i915_selftest@live@hangcheck:
- fi-snb-2600: [INCOMPLETE][28] ([i915#3921]) -> [PASS][29]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11456/fi-snb-2600/igt@i915_selftest@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/fi-snb-2600/igt@i915_selftest@[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#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#3987]: https://gitlab.freedesktop.org/drm/intel/issues/3987
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#4032]: https://gitlab.freedesktop.org/drm/intel/issues/4032
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215
[i915#4391]: https://gitlab.freedesktop.org/drm/intel/issues/4391
[i915#4418]: https://gitlab.freedesktop.org/drm/intel/issues/4418
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
[i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190
[i915#5274]: https://gitlab.freedesktop.org/drm/intel/issues/5274
[i915#5275]: https://gitlab.freedesktop.org/drm/intel/issues/5275
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5341]: https://gitlab.freedesktop.org/drm/intel/issues/5341
[i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354
[i915#5414]: https://gitlab.freedesktop.org/drm/intel/issues/5414
[i915#5457]: https://gitlab.freedesktop.org/drm/intel/issues/5457
Build changes
-------------
* Linux: CI_DRM_11456 -> Patchwork_22782
CI-20190529: 20190529
CI_DRM_11456: 0059060adfc9738fffdc0e03629d480579e3f7a2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6410: cc359d5d2d3fc8be50340ba0379bacaf5c37bc5f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22782: ac9ed0a5003251769ec1ffe0f1d61384c8dfd565 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
ac9ed0a50032 drm/i915: Inherit submitter nice when scheduling requests 809fe4fc972b drm/i915: Inherit process nice for context scheduling priority ded698b30753 drm/i915: Make some recently added vfuncs use full scheduling attribute
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22782/index.html