Add sysfs interface to control class-of-service
Subsystems (2)
v3 cover Add sysfs interface to control class-of-service
For GEN11 MOCS are part of context register state. This means updating CLOS also needs to update the context state of active contexts.
v3: Rebase
v2: Updated the interface to use two sysfs files(Joonas)
- Gen12 PCode interface is not ready yet to read the way mask. So removed TGL support and added support for Gen11.
- Updating MOCS in Gen 11 also require changing the context image of existing contexts.
Referred to gen8_configure_all_contexts() as suggested by Chris.
Prathap Kumar Valsan (1):
drm/i915/ehl: Add sysfs interface to control class-of-service
drivers/gpu/drm/i915/gt/intel_lrc.c | 7 + drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 1 + drivers/gpu/drm/i915/gt/intel_mocs.c | 216 +++++++++++++++++++++++- drivers/gpu/drm/i915/gt/intel_mocs.h | 6 +- drivers/gpu/drm/i915/i915_drv.h | 8 + drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/i915_sysfs.c | 100 +++++++++++ 7 files changed, 337 insertions(+), 2 deletions(-)
Signature · 5 lines
2.20.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 1/1 drm/i915/ehl: Add sysfs interface to control class-of-service
To provide shared last-level-cache isolation to cpu workloads running concurrently with gpu workloads, the gpu allocation of cache lines needs to be restricted to certain ways. Currently GPU hardware supports four class-of-service(CLOS) levels and there is an associated way-mask for each CLOS. Each LLC MOCS register has a field to select the clos level. So in-order to globally set the gpu to a clos level, driver needs to program entire MOCS table.
Hardware supports reading supported way-mask configuration for GPU using a bios pcode interface. This interface has two files--llc_clos_modes and llc_clos. The file llc_clos_modes is read only file and will list the available way masks. The file llc_clos is read/write and will show the currently active way mask and writing a new way mask will update the active way mask of the gpu.
Note of Caution: Restricting cache ways using this mechanism presents a larger attack surface for side-channel attacks.
Example usage:
Quoted 1 line
cat
/sys/class/drm/card0/llc_clos_modes
0xfff 0xfc0 0xc00 0x800
Quoted 1 line
cat
/sys/class/drm/card0/llc_clos
0xfff
Update to new clos
echo "0x800" > /sys/class/drm/card0/llc_clos
--- drivers/gpu/drm/i915/gt/intel_lrc.c | 7 + drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 1 + drivers/gpu/drm/i915/gt/intel_mocs.c | 216 +++++++++++++++++++++++- drivers/gpu/drm/i915/gt/intel_mocs.h | 6 +- drivers/gpu/drm/i915/i915_drv.h | 8 + drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/i915_sysfs.c | 100 +++++++++++ 7 files changed, 337 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/gt/intel_lrc.c +7 -0
@@ -2137,6 +2137,13 @@ __execlists_update_reg_state(const struct intel_context *ce,intel_sseu_make_rpcs (engine->i915, &ce->sseu);i915_oa_init_reg_state (ce, engine); +/* +* Gen11+ wants to support update of LLC class-of-service via +* sysfs interface. CLOS is defined in MOCS registers and for +* Gen11, MOCS is part of context resgister state. +*/ +if (IS_GEN (engine->i915,11 )) +intel_mocs_init_reg_state (ce); } }
drivers/gpu/drm/i915/gt/intel_lrc_reg.h +1 -0
@@ -28,6 +28,7 @@#define CTX_R_PWR_CLK_STATE (0x42 + 1)#define GEN9_CTX_RING_MI_MODE 0x54 +#define GEN11_CTX_GFX_MOCS_BASE 0x4F2/* GEN12+ Reg State Context */ #define GEN12_CTX_BB_PER_CTX_PTR (0x12 + 1)
drivers/gpu/drm/i915/gt/intel_mocs.c +215 -1
287 lines not on this page · raw message
drivers/gpu/drm/i915/gt/intel_mocs.h +5 -1
@@ -49,13 +49,17 @@* context handling keep the MOCS in step. */ -struct i915_request ;struct intel_engine_cs ; +struct intel_context ; +struct i915_request ;struct intel_gt ;void intel_mocs_init (struct intel_gt *gt);void intel_mocs_init_engine (struct intel_engine_cs *engine);int intel_mocs_emit (struct i915_request *rq); +int intel_mocs_update_clos (struct intel_gt *gt); + +void intel_mocs_init_reg_state (const struct intel_context *ce);#endif
drivers/gpu/drm/i915/i915_drv.h +8 -0
@@ -1604,6 +1604,14 @@ struct drm_i915_private {bool distrust_bios_wm; } wm; +/* Last Level Cache Class of Service */ +struct { +bool support_way_mask_read; +u8 active_clos; +#define NUM_OF_CLOS 4 +u16 way_mask[NUM_OF_CLOS ]; + } clos; +struct dram_info {bool valid;bool is_16gb_dimm;
drivers/gpu/drm/i915/i915_reg.h +1 -0
@@ -8859,6 +8859,7 @@ enum {#define ICL_PCODE_MEM_SUBSYSYSTEM_INFO 0xd#define ICL_PCODE_MEM_SS_READ_GLOBAL_INFO (0x0 << 8)#define ICL_PCODE_MEM_SS_READ_QGV_POINT_INFO (point) (((point) << 16) | (0x1 << 8)) +#define ICL_PCODE_LLC_COS_WAY_MASK_INFO 0x1d#define GEN6_PCODE_READ_D_COMP 0x10#define GEN6_PCODE_WRITE_D_COMP 0x11#define HSW_PCODE_DE_WRITE_FREQ_REQ 0x17
drivers/gpu/drm/i915/i915_sysfs.c +100 -0
124 lines not on this page · raw message
Signature · 6 lines
2.20.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v3 1/1] drm/i915/ehl: Add sysfs interface to control class-of-service
Quoting Prathap Kumar Valsan (2019-10-07 17:52:09)
Quoted 19 lines
To provide shared last-level-cache isolation to cpu workloads running concurrently with gpu workloads, the gpu allocation of cache lines needs to be restricted to certain ways. Currently GPU hardware supports four class-of-service(CLOS) levels and there is an associated way-mask for each CLOS. Each LLC MOCS register has a field to select the clos level. So in-order to globally set the gpu to a clos level, driver needs to program entire MOCS table.
Hardware supports reading supported way-mask configuration for GPU using a bios pcode interface. This interface has two files--llc_clos_modes and
llc_clos. The filellc_clos_modesis read only file and will list the available way masks. The filellc_closis read/write and will show the currently active way mask and writing a new way mask will update the active way mask of the gpu.Note of Caution: Restricting cache ways using this mechanism presents a larger attack surface for side-channel attacks.
Example usage:
Quoted 8 lines
Quoted 1 line
cat
/sys/class/drm/card0/llc_clos_modes
0xfff0xfc00xc000x800Quoted 1 line
cat
/sys/class/drm/card0/llc_clos
0xfffUpdate to new clos
echo "0x800" >/sys/class/drm/card0/llc_clos
So the first question is whether this is global on the device or local to the GT.
Quoted 16 lines
Signed-off-by Prathap Kumar Valsan <[email protected]>--- drivers/gpu/drm/i915/gt/intel_lrc.c | 7 + drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 1 + drivers/gpu/drm/i915/gt/intel_mocs.c | 216 +++++++++++++++++++++++- drivers/gpu/drm/i915/gt/intel_mocs.h | 6 +- drivers/gpu/drm/i915/i915_drv.h | 8 + drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/i915_sysfs.c | 100 +++++++++++ 7 files changed, 337 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gt/intel_lrc.c +0
-0
drivers/gpu/drm/i915/gt/intel_lrc.c __execlists_update_reg_state(const struct intel_context *ce, · line 2146
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +7
-0@@ -2137,6 +2137,13 @@ __execlists_update_reg_state(const struct intel_context *ce,intel_sseu_make_rpcs (engine->i915, &ce->sseu);i915_oa_init_reg_state (ce, engine); +/* +* Gen11+ wants to support update of LLC class-of-service via +* sysfs interface. CLOS is defined in MOCS registers and for +* Gen11, MOCS is part of context resgister state. +*/ +if (IS_GEN (engine->i915,11 )) +intel_mocs_init_reg_state (ce);
Do the filtering in intel_mocs_init_reg_state(). The intel_ prefix says it should be common to all.
Not IS_ELKHARTLAKE(), that is implies by subject?
Quoted 13 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +13
-0+static int +mocs_store_clos (struct i915_request *rq, +struct intel_context *ce) +{ +struct drm_i915_mocs_table t; +unsigned int count, active_clos, index; +u32 offset; +u32 value; +u32 *cs; + +if (!get_mocs_settings (rq->engine->gt, &t)) +return -ENODEV ; +
drivers/gpu/drm/i915/gt/intel_lrc.c __execlists_update_reg_state(const struct intel_context *ce,
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +10
-0+ count = t.n_entries; + active_clos = rq->i915->clos.active_clos; + cs =intel_ring_begin (rq,4 * count); +if (IS_ERR (cs)) +return PTR_ERR (cs); + + offset =i915_ggtt_offset (ce->state) +LRC_STATE_PN *PAGE_SIZE ; + +for (index =0 ; index < count; index++) { + value = ce->lrc_reg_state[ctx_mocsN (index)];
Their context image is volatile at this point. They are pinned and active. If you must do a rmw, do it on the GPU. But do we not know the full value (as I don't expect it to be nonpriv)? [If doing rmw on the GPU, we're probably have to use a secure batch here to avoid running out of ringspace.]
Quoted 53 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +53
-0+ value &= ~LE_COS_MASK ; + value |=FIELD_PREP (LE_COS_MASK , active_clos); + + *cs++ =MI_STORE_DWORD_IMM_GEN4 |MI_USE_GGTT ; + *cs++ = offset +ctx_mocsN (index) *sizeof (uint32_t ); + *cs++ =0 ; + *cs++ = value; + } + +intel_ring_advance (rq, cs); + +return 0 ; +} + +static int modify_context_mocs (struct intel_context *ce) +{ +struct i915_request *rq; +int err; + +lockdep_assert_held (&ce->pin_mutex); + + rq =i915_request_create (ce->engine->kernel_context); +if (IS_ERR (rq)) +return PTR_ERR (rq); + +/* Serialise with the remote context */ + err =intel_context_prepare_remote_request (ce, rq); +if (err ==0 ) + err =mocs_store_clos (rq, ce); + +i915_request_add (rq); +return err; +} + +static int intel_mocs_configure_context (struct i915_gem_context *ctx) +{ +struct i915_gem_engines_iter it; +struct intel_context *ce; +int err =0 ; + +for_each_gem_engine (ce,i915_gem_context_lock_engines (ctx), it) { +GEM_BUG_ON (ce == ce->engine->kernel_context); + +if (ce->engine->class !=RENDER_CLASS ) +continue ; + + err =intel_context_lock_pinned (ce); +if (err) +break ; + +if (intel_context_is_pinned (ce)) + err =modify_context_mocs (ce); +
drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +10
-0+intel_context_unlock_pinned (ce); +if (err) +break ; + } +i915_gem_context_unlock_engines (ctx); + +return err; +} + +static int intel_mocs_configure_all_contexts (struct intel_gt *gt)
So this on the GT,
drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +8
-0+{ +struct drm_i915_private *i915 = gt->i915; +struct intel_engine_cs *engine; +struct i915_gem_context *ctx; +enum intel_engine_id id; +int err; + +lockdep_assert_held (&i915->drm.struct_mutex);
Wrong lock entirely, you need the context lock for walking the i915->gem.contexts.list.
drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 11 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +11
-0+/* +* MOCS registers of render engine are context saved and restored to and +* from a context image. +* So for any MOCS update to reflect on the existing contexts requires +* updating the context image. +*/ +list_for_each_entry (ctx, &i915->gem.contexts.list, link) { +if (ctx == i915->kernel_context) +continue ; + + err =intel_mocs_configure_context (ctx);
but this is global,
drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +10
-0+if (err) +return err; + } + +/* +* After updating all other contexts, update render context image of +* kernel context. Also update the MOCS of non-render engines. +*/ + +for_each_engine (engine, i915, id) {
and here again you are on the gt.
Quoted 26 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +20
-0+struct i915_request *rq; +struct drm_i915_mocs_table t; + + rq =i915_request_create (engine->kernel_context); +if (IS_ERR (rq)) +return PTR_ERR (rq); + +get_mocs_settings (rq->engine->gt, &t); + err =emit_mocs_control_table (rq, &t); +if (err) { +i915_request_skip (rq, err); +i915_request_add (rq); +return err; + } + +i915_request_add (rq); + } + +return 0 ; +}drivers/gpu/drm/i915/gt/intel_mocs.h +0
-0
drivers/gpu/drm/i915/gt/intel_mocs.h line 55
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_mocs.h +2
-1@@ -49,13 +49,17 @@* context handling keep the MOCS in step. */ -struct i915_request ;struct intel_engine_cs ; +struct intel_context ; +struct i915_request ;struct intel_gt ;
Our OCD is to keep these in alphabetical order.
-Chris
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v3 1/1] drm/i915/ehl: Add sysfs interface to control class-of-service
Quoted 23 lines · Chris Wilson
Quoting Prathap Kumar Valsan (2019-10-07 17:52:09)
Quoted 22 lines
To provide shared last-level-cache isolation to cpu workloads running concurrently with gpu workloads, the gpu allocation of cache lines needs to be restricted to certain ways. Currently GPU hardware supports four class-of-service(CLOS) levels and there is an associated way-mask for each CLOS. Each LLC MOCS register has a field to select the clos level. So in-order to globally set the gpu to a clos level, driver needs to program entire MOCS table.
Hardware supports reading supported way-mask configuration for GPU using a bios pcode interface. This interface has two files--llc_clos_modes and
llc_clos. The filellc_clos_modesis read only file and will list the available way masks. The filellc_closis read/write and will show the currently active way mask and writing a new way mask will update the active way mask of the gpu.Note of Caution: Restricting cache ways using this mechanism presents a larger attack surface for side-channel attacks.
Example usage:
Quoted 1 line
cat
/sys/class/drm/card0/llc_clos_modes
0xfff0xfc00xc000x800
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
cat
/sys/class/drm/card0/llc_clos
0xfffUpdate to new clos
echo "0x800" >/sys/class/drm/card0/llc_closSo the first question is whether this is global on the device or local to the GT.
It is global to the device. I have sent the updated patch, which would explicitly state this in commit message.
Quoted 31 lines
Quoted 17 lines
Signed-off-by Prathap Kumar Valsan <[email protected]>--- drivers/gpu/drm/i915/gt/intel_lrc.c | 7 + drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 1 + drivers/gpu/drm/i915/gt/intel_mocs.c | 216 +++++++++++++++++++++++- drivers/gpu/drm/i915/gt/intel_mocs.h | 6 +- drivers/gpu/drm/i915/i915_drv.h | 8 + drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/i915_sysfs.c | 100 +++++++++++ 7 files changed, 337 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/gt/intel_lrc.c +0
-0drivers/gpu/drm/i915/gt/intel_lrc.c __execlists_update_reg_state(const struct intel_context *ce, · line 2146
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +7
-0@@ -2137,6 +2137,13 @@ __execlists_update_reg_state(const struct intel_context *ce,intel_sseu_make_rpcs (engine->i915, &ce->sseu);i915_oa_init_reg_state (ce, engine); +/* +* Gen11+ wants to support update of LLC class-of-service via +* sysfs interface. CLOS is defined in MOCS registers and for +* Gen11, MOCS is part of context resgister state. +*/ +if (IS_GEN (engine->i915,11 )) +intel_mocs_init_reg_state (ce);Do the filtering in
intel_mocs_init_reg_state(). Theintel_prefix says it should be common to all.
Quoted 2 lines
Not
IS_ELKHARTLAKE(), that is implies by subject?
Gen11 PCode implementation has this support to read way mask. So updated it to Gen11.
Quoted 21 lines
Quoted 21 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +21
-0+static int +mocs_store_clos (struct i915_request *rq, +struct intel_context *ce) +{ +struct drm_i915_mocs_table t; +unsigned int count, active_clos, index; +u32 offset; +u32 value; +u32 *cs; + +if (!get_mocs_settings (rq->engine->gt, &t)) +return -ENODEV ; + + count = t.n_entries; + active_clos = rq->i915->clos.active_clos; + cs =intel_ring_begin (rq,4 * count); +if (IS_ERR (cs)) +return PTR_ERR (cs); + + offset =i915_ggtt_offset (ce->state) +LRC_STATE_PN *PAGE_SIZE ; +
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 2 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +2
-0+for (index =0 ; index < count; index++) { + value = ce->lrc_reg_state[ctx_mocsN (index)];Their context image is volatile at this point. They are pinned and active. If you must do a rmw, do it on the GPU. But do we not know the full value (as I don't expect it to be nonpriv)? [If doing rmw on the GPU, we're probably have to use a secure batch here to avoid running out of ringspace.]
Right. Fixed.
Quoted 91 lines
Quoted 54 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +53
-0+ value &= ~LE_COS_MASK ; + value |=FIELD_PREP (LE_COS_MASK , active_clos); + + *cs++ =MI_STORE_DWORD_IMM_GEN4 |MI_USE_GGTT ; + *cs++ = offset +ctx_mocsN (index) *sizeof (uint32_t ); + *cs++ =0 ; + *cs++ = value; + } + +intel_ring_advance (rq, cs); + +return 0 ; +} + +static int modify_context_mocs (struct intel_context *ce) +{ +struct i915_request *rq; +int err; + +lockdep_assert_held (&ce->pin_mutex); + + rq =i915_request_create (ce->engine->kernel_context); +if (IS_ERR (rq)) +return PTR_ERR (rq); + +/* Serialise with the remote context */ + err =intel_context_prepare_remote_request (ce, rq); +if (err ==0 ) + err =mocs_store_clos (rq, ce); + +i915_request_add (rq); +return err; +} + +static int intel_mocs_configure_context (struct i915_gem_context *ctx) +{ +struct i915_gem_engines_iter it; +struct intel_context *ce; +int err =0 ; + +for_each_gem_engine (ce,i915_gem_context_lock_engines (ctx), it) { +GEM_BUG_ON (ce == ce->engine->kernel_context); + +if (ce->engine->class !=RENDER_CLASS ) +continue ; + + err =intel_context_lock_pinned (ce); +if (err) +break ; + +if (intel_context_is_pinned (ce)) + err =modify_context_mocs (ce); +drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +10
-0+intel_context_unlock_pinned (ce); +if (err) +break ; + } +i915_gem_context_unlock_engines (ctx); + +return err; +} + +static int intel_mocs_configure_all_contexts (struct intel_gt *gt)So this on the GT,
drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +8
-0+{ +struct drm_i915_private *i915 = gt->i915; +struct intel_engine_cs *engine; +struct i915_gem_context *ctx; +enum intel_engine_id id; +int err; + +lockdep_assert_held (&i915->drm.struct_mutex);Wrong lock entirely, you need the context lock for walking the
i915->gem.contexts.list.drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 11 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +11
-0+/* +* MOCS registers of render engine are context saved and restored to and +* from a context image. +* So for any MOCS update to reflect on the existing contexts requires +* updating the context image. +*/ +list_for_each_entry (ctx, &i915->gem.contexts.list, link) { +if (ctx == i915->kernel_context) +continue ; + + err =intel_mocs_configure_context (ctx);
Quoted 2 lines
but this is global,
Even though in Gen11, global and GT may not make much difference, I made an attempt to move the global out of GT.
Quoted 42 lines
drivers/gpu/drm/i915/gt/intel_lrc.c
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +10
-0+if (err) +return err; + } + +/* +* After updating all other contexts, update render context image of +* kernel context. Also update the MOCS of non-render engines. +*/ + +for_each_engine (engine, i915, id) {and here again you are on the gt.
Quoted 29 lines
drivers/gpu/drm/i915/gt/intel_lrc.c +20
-0+struct i915_request *rq; +struct drm_i915_mocs_table t; + + rq =i915_request_create (engine->kernel_context); +if (IS_ERR (rq)) +return PTR_ERR (rq); + +get_mocs_settings (rq->engine->gt, &t); + err =emit_mocs_control_table (rq, &t); +if (err) { +i915_request_skip (rq, err); +i915_request_add (rq); +return err; + } + +i915_request_add (rq); + } + +return 0 ; +}drivers/gpu/drm/i915/gt/intel_mocs.h +0
-0@@ -49,13 +49,17 @@* context handling keep the MOCS in step. */
Quoted 7 lines
drivers/gpu/drm/i915/gt/intel_mocs.h line 55
Quoted 5 lines
drivers/gpu/drm/i915/gt/intel_mocs.h +2
-1-struct i915_request ;struct intel_engine_cs ; +struct intel_context ; +struct i915_request ;struct intel_gt ;Our OCD is to keep these in alphabetical order.
Fixed.
Thank You,
Prathap
Quoted 1 line
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.SPARSE: warning for Add sysfs interface to control class-of-service
In reply to Prathap Kumar Valsan== Series Details ==
== Series Details ==
Series: Add sysfs interface to control class-of-service
URL : https://patchwork.freedesktop.org/series/67700/
State : warning
== Summary ==
$ dim sparse origin/drm-tip Sparse version: v0.6.0 Commit: drm/i915/ehl: Add sysfs interface to control class-of-service +drivers/gpu/drm/i915/gt/intel_mocs.c:422:6: warning: symbol 'intel_mocs_init_global' was not declared. Should it be static?
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: failure for Add sysfs interface to control class-of-service
In reply to Prathap Kumar Valsan== Series Details ==
== Series Details ==
Series: Add sysfs interface to control class-of-service
URL : https://patchwork.freedesktop.org/series/67700/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7024 -> Patchwork_14694
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_14694 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_14694, 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_14694/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_14694:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live_execlists:
- fi-skl-6260u: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7024/fi-skl-6260u/igt@i915_selftest@live_execlists.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14694/fi-skl-6260u/igt@i915_selftest@live_execlists.html
Known issues
------------
Here are the changes found in Patchwork_14694 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live_execlists:
- fi-icl-u3: [PASS][3] -> [DMESG-FAIL][4] ([fdo#111872])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7024/fi-icl-u3/igt@i915_selftest@live_execlists.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14694/fi-icl-u3/igt@i915_selftest@live_execlists.html
* igt@prime_vgem@basic-read:
- fi-icl-u3: [PASS][5] -> [DMESG-WARN][6] ([fdo#107724])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7024/fi-icl-u3/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14694/fi-icl-u3/igt@[email protected]
#### Possible fixes ####
* igt@gem_mmap_gtt@basic-write-gtt:
- fi-icl-u3: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8] +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7024/fi-icl-u3/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14694/fi-icl-u3/igt@[email protected]
* igt@kms_chamelium@dp-edid-read:
- fi-kbl-7500u: [WARN][9] ([fdo#109483]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7024/fi-kbl-7500u/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14694/fi-kbl-7500u/igt@[email protected]
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483
[fdo#111872]: https://bugs.freedesktop.org/show_bug.cgi?id=111872
Participating hosts (52 -> 44)
------------------------------
Missing (8): fi-ilk-m540 fi-tgl-u fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7024 -> Patchwork_14694
CI-20190529: 20190529
CI_DRM_7024: b149aba92ace27b28e068c2541270653c23bca75 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5215: 880c8d3c9831349a269ac6822c8d44e80807089f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14694: c0fc7c3ea79f2cfb9c05e4e26e3cbd76d74652a2 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
c0fc7c3ea79f drm/i915/ehl: Add sysfs interface to control class-of-service
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14694/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx