drm/i915: Do not call API requiring struct_mutex where it is not available
Subsystems (2)
PATCH 1/3 drm/i915: Do not call API requiring struct_mutex where it is not available
From: Tvrtko Ursulin <[email protected]>
LRC code was calling GEM API like i915_gem_obj_ggtt_offset from places where the struct_mutex cannot be grabbed (irq handlers).
To avoid that this patch caches some interesting bits and values in the engine and context structures.
Some usages are also removed where they are not needed like a few asserts which are either impossible or have been checked already during engine initialization.
Side benefit is also that interrupt handlers and command submission stop evaluating invariant conditionals, like what Gen we are running on, on every interrupt and every command submitted.
This patch deals with logical ring context id and descriptors while subsequent patches will deal with the remaining issues.
v2:
* Cache the VMA instead of the address. (Chris Wilson)
* Incorporate Dave Gordon's good comments and function name.
v3:
* Extract ctx descriptor template to a function and group functions dealing with ctx descriptor & co together near top of the file. (Dave Gordon)
--- drivers/gpu/drm/i915/i915_debugfs.c | 15 ++-- drivers/gpu/drm/i915/i915_drv.h | 2 + drivers/gpu/drm/i915/i915_gem_gtt.h | 1 - drivers/gpu/drm/i915/intel_lrc.c | 151 +++++++++++++++++++------------- drivers/gpu/drm/i915/intel_lrc.h | 4 +- drivers/gpu/drm/i915/intel_ringbuffer.h | 2 + 6 files changed, 103 insertions(+), 72 deletions(-)
drivers/gpu/drm/i915/i915_debugfs.c +6 -9
@@ -1994,12 +1994,13 @@ static int i915_context_status(struct seq_file *m, void *unused) }static void i915_dump_lrc_obj (struct seq_file *m, -struct intel_engine_cs *ring, -struct drm_i915_gem_object *ctx_obj) +struct intel_context *ctx, +struct intel_engine_cs *ring) {struct page *page;uint32_t *reg_state;int j; +struct drm_i915_gem_object *ctx_obj = ctx->engine[ring->id].state;unsigned long ggtt_offset =0 ;if (ctx_obj ==NULL ) {
@@ -2009,7 +2010,7 @@ static void i915_dump_lrc_obj(struct seq_file *m, }seq_printf (m,"CONTEXT: %s %u\n" , ring->name, -intel_execlists_ctx_id (ctx_obj)); +intel_execlists_ctx_id (ctx, ring));if (!i915_gem_obj_ggtt_bound (ctx_obj))seq_puts (m,"\tNot bound in GGTT\n" );
@@ -2058,8 +2059,7 @@ static int i915_dump_lrc(struct seq_file *m, void *unused)list_for_each_entry (ctx, &dev_priv->context_list, link) {for_each_ring (ring, dev_priv, i) {if (ring->default_context != ctx) -i915_dump_lrc_obj (m, ring, - ctx->engine[i].state); +i915_dump_lrc_obj (m, ctx, ring); } }
@@ -2133,11 +2133,8 @@ static int i915_execlists(struct seq_file *m, void *data)seq_printf (m,"\t%d requests in queue\n" , count);if (head_req) { -struct drm_i915_gem_object *ctx_obj; - - ctx_obj = head_req->ctx->engine[ring_id].state;seq_printf (m,"\tHead request id: %u\n" , -intel_execlists_ctx_id (ctx_obj)); +intel_execlists_ctx_id (head_req->ctx, ring));seq_printf (m,"\tHead request tail: %u\n" , head_req->tail); }
drivers/gpu/drm/i915/i915_drv.h +2 -0
@@ -888,6 +888,8 @@ struct intel_context {struct drm_i915_gem_object *state;struct intel_ringbuffer *ringbuf;int pin_count; +struct i915_vma *lrc_vma; +u64 lrc_desc; } engine[I915_NUM_RINGS ];struct list_head link;
drivers/gpu/drm/i915/i915_gem_gtt.h +0 -1
@@ -44,7 +44,6 @@ typedef uint64_t gen8_ppgtt_pml4e_t;#define gtt_total_entries (gtt) ((gtt).base.total >> PAGE_SHIFT) -/* gen6-hsw has bit 11-4 for physical addr bit 39-32 */ #define GEN6_GTT_ADDR_ENCODE (addr) ((addr) | (((addr) >> 28) & 0xff0))#define GEN6_PTE_ADDR_ENCODE (addr) GEN6_GTT_ADDR_ENCODE(addr)
drivers/gpu/drm/i915/intel_lrc.c +90 -61
238 lines not on this page · raw message
drivers/gpu/drm/i915/intel_lrc.h +3 -1
@@ -107,13 +107,15 @@ void intel_lr_context_reset(struct drm_device *dev,uint64_t intel_lr_context_descriptor (struct intel_context *ctx,struct intel_engine_cs *ring); +u32 intel_execlists_ctx_id (struct intel_context *ctx, +struct intel_engine_cs *ring); +/* Execlists */ int intel_sanitize_enable_execlists (struct drm_device *dev,int enable_execlists);struct i915_execbuffer_params ;int intel_execlists_submission (struct i915_execbuffer_params *params,struct drm_i915_gem_execbuffer2 *args,struct list_head *vmas); -u32 intel_execlists_ctx_id (struct drm_i915_gem_object *ctx_obj);void intel_lrc_irq_handler (struct intel_engine_cs *ring);void intel_execlists_retire_requests (struct intel_engine_cs *ring);
drivers/gpu/drm/i915/intel_ringbuffer.h +2 -0
@@ -269,6 +269,8 @@ struct intel_engine_cs {struct list_head execlist_queue;struct list_head execlist_retired_req_list;u8 next_context_status_buffer; +bool disable_lite_restore_wa; +u32 ctx_desc_template;u32 irq_keep_mask;/* bitmask for interrupts that should not be masked */ int (*emit_request)(struct drm_i915_gem_request *request); int (*emit_flush)(struct drm_i915_gem_request *request,
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/3 drm/i915: Cache ringbuffer GTT VMA
From: Tvrtko Ursulin <[email protected]>
Purpose is to avoid calling i915_gem_obj_ggtt_offset from the interrupt context without the big lock held.
v2: Renamed gtt_start to gtt_offset. (Daniel Vetter)
v3: Cache the VMA instead of address. (Chris Wilson)
--- drivers/gpu/drm/i915/intel_lrc.c | 3 +-- drivers/gpu/drm/i915/intel_ringbuffer.c | 3 +++ drivers/gpu/drm/i915/intel_ringbuffer.h | 1 + 3 files changed, 5 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/intel_lrc.c +1 -2
@@ -391,7 +391,6 @@ static int execlists_update_context(struct drm_i915_gem_request *rq)struct intel_engine_cs *ring = rq->ring;struct i915_hw_ppgtt *ppgtt = rq->ctx->ppgtt;struct drm_i915_gem_object *ctx_obj = rq->ctx->engine[ring->id].state; -struct drm_i915_gem_object *rb_obj = rq->ringbuf->obj;struct page *page;uint32_t *reg_state;
@@ -401,7 +400,7 @@ static int execlists_update_context(struct drm_i915_gem_request *rq) reg_state =kmap_atomic (page); reg_state[CTX_RING_TAIL +1 ] = rq->tail; - reg_state[CTX_RING_BUFFER_START +1 ] =i915_gem_obj_ggtt_offset (rb_obj); + reg_state[CTX_RING_BUFFER_START +1 ] = rq->ringbuf->vma->node.start;if (ppgtt && !USES_FULL_48BIT_PPGTT (ppgtt->base.dev)) {/* True 32b PPGTT with dynamic page allocation: update PDP
drivers/gpu/drm/i915/intel_ringbuffer.c +3 -0
@@ -1997,6 +1997,7 @@ void intel_unpin_ringbuffer_obj(struct intel_ringbuffer *ringbuf)else iounmap (ringbuf->virtual_start); ringbuf->virtual_start =NULL ; + ringbuf->vma =NULL ;i915_gem_object_ggtt_unpin (ringbuf->obj); }
@@ -2063,6 +2064,8 @@ int intel_pin_and_map_ringbuffer_obj(struct drm_device *dev, } } + ringbuf->vma =i915_gem_obj_to_ggtt (obj); +return 0 ; }
drivers/gpu/drm/i915/intel_ringbuffer.h +1 -0
@@ -99,6 +99,7 @@ struct intel_ring_hangcheck {struct intel_ringbuffer {struct drm_i915_gem_object *obj;void __iomem *virtual_start; +struct i915_vma *vma;struct intel_engine_cs *ring;struct list_head link;
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 3/3 drm/i915: Cache LRC state page in the context
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
LRC lifetime is well defined so we can cache the page pointing to the object backing store in the context in order to avoid walking over the object SG page list from the interrupt context without the big lock held.
v2: Also cache the mapping. (Chris Wilson)
v3: Unmap on the error path.
v4: No need to cache the page. (Chris Wilson)
--- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_lrc.c | 53 ++++++++++++++++++++++++++-------------- 2 files changed, 35 insertions(+), 19 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -890,6 +890,7 @@ struct intel_context {int pin_count;struct i915_vma *lrc_vma;u64 lrc_desc; +uint32_t *lrc_reg_state; } engine[I915_NUM_RINGS ];struct list_head link;
drivers/gpu/drm/i915/intel_lrc.c +34 -19
95 lines not on this page · raw message
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 3/3] drm/i915: Cache LRC state page in the context
drivers/gpu/drm/i915/intel_lrc.c void intel_lr_context_unpin(struct drm_i915_gem_request *rq) · line 1128
Quoted 4 lines · Tvrtko Ursulin
drivers/gpu/drm/i915/intel_lrc.c +3
-0@@ -1118,15 +1126,22 @@ void intel_lr_context_unpin(struct drm_i915_gem_request *rq) +if (--rq->ctx->engine[ring->id].pin_count ==0 ) { + lrc_state_page =i915_gem_object_get_dirty_page (ctx_obj, +LRC_STATE_PN );
Interesting choice. We called set_page_dirty() when we took the mapping. Should that page flag be preserved whilst we hold the kmap - I think so, i.e. the mm cannot flush the page whilst it has an elevated mapcount. So calling set_page_dirty() again is redundant, right?
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 3/3] drm/i915: Cache LRC state page in the context
Quoted 10 lines · Chris Wilson
drivers/gpu/drm/i915/intel_lrc.c void intel_lr_context_unpin(struct drm_i915_gem_request *rq) · line 1128
Quoted 4 lines · Tvrtko Ursulin
drivers/gpu/drm/i915/intel_lrc.c +3
-0@@ -1118,15 +1126,22 @@ void intel_lr_context_unpin(struct drm_i915_gem_request *rq) +if (--rq->ctx->engine[ring->id].pin_count ==0 ) { + lrc_state_page =i915_gem_object_get_dirty_page (ctx_obj, +LRC_STATE_PN );Interesting choice. We called
set_page_dirty()when we took the mapping. Should that page flag be preserved whilst we hold the kmap - I think so, i.e. the mm cannot flush the page whilst it has an elevated mapcount. So callingset_page_dirty()again is redundant, right?
If you call mindless copy & paste interesting. :D
Any other concerns or I can respin with that only?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 3/3] drm/i915: Cache LRC state page in the context
Quoted 13 lines · Tvrtko Ursulin
Quoted 10 lines · Chris Wilson
drivers/gpu/drm/i915/intel_lrc.c void intel_lr_context_unpin(struct drm_i915_gem_request *rq) · line 1128
Quoted 4 lines · Tvrtko Ursulin
drivers/gpu/drm/i915/intel_lrc.c +3
-0@@ -1118,15 +1126,22 @@ void intel_lr_context_unpin(struct drm_i915_gem_request *rq) +if (--rq->ctx->engine[ring->id].pin_count ==0 ) { + lrc_state_page =i915_gem_object_get_dirty_page (ctx_obj, +LRC_STATE_PN );Interesting choice. We called
set_page_dirty()when we took the mapping. Should that page flag be preserved whilst we hold the kmap - I think so, i.e. the mm cannot flush the page whilst it has an elevated mapcount. So callingset_page_dirty()again is redundant, right?
Quoted 3 lines
If you call mindless copy & paste interesting. :D
Any other concerns or I can respin with that only?
No. I was quibbling over the excess clearing of state on unpinning :)
Pity we have to respin even for innoculous changes just to get a CI tick.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v5 1/1 drm/i915: Cache LRC state page in the context
From: Tvrtko Ursulin <[email protected]>
LRC lifetime is well defined so we can cache the page pointing to the object backing store in the context in order to avoid walking over the object SG page list from the interrupt context without the big lock held.
v2: Also cache the mapping. (Chris Wilson)
v3: Unmap on the error path.
v4: No need to cache the page. (Chris Wilson)
v5: No need to dirty the page on unpin. (Chris Wilson)
--- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_lrc.c | 53 ++++++++++++++++++++++++++-------------- 2 files changed, 35 insertions(+), 19 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -890,6 +890,7 @@ struct intel_context {int pin_count;struct i915_vma *lrc_vma;u64 lrc_desc; +uint32_t *lrc_reg_state; } engine[I915_NUM_RINGS ];struct list_head link;
drivers/gpu/drm/i915/intel_lrc.c +34 -19
95 lines not on this page · raw message
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v5] drm/i915: Cache LRC state page in the context
Quoted 11 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
LRC lifetime is well defined so we can cache the page pointing to the object backing store in the context in order to avoid walking over the object SG page list from the interrupt context without the big lock held.
v2: Also cache the mapping. (Chris Wilson)
v3: Unmap on the error path.
v4: No need to cache the page. (Chris Wilson)
v5: No need to dirty the page on unpin. (Chris Wilson)
Sorry.
drivers/gpu/drm/i915/intel_lrc.c static int intel_lr_context_do_pin(struct intel_engine_cs *ring, · line 1078
Quoted 11 lines
drivers/gpu/drm/i915/intel_lrc.c +7
-0@@ -1076,12 +1069,25 @@ static int intel_lr_context_do_pin(struct intel_engine_cs *ring,if (ret)return ret; + lrc_state_page =i915_gem_object_get_dirty_page (ctx_obj,LRC_STATE_PN ); +if (WARN_ON (!lrc_state_page)) { + ret = -ENODEV ; + goto unpin_ctx_obj; + } + + lrc_reg_state =kmap (lrc_state_page);
kmap() cannot fail.
drivers/gpu/drm/i915/intel_lrc.c static int intel_lr_context_do_pin(struct intel_engine_cs *ring,
Quoted 5 lines
drivers/gpu/drm/i915/intel_lrc.c +5
-0+if (!lrc_reg_state) { + ret = -ENOMEM ; + goto unpin_ctx_obj; + } +if (--rq->ctx->engine[ring->id].pin_count ==0 ) {
I was wondering if we should just use
kunmap(kmap_to_page(ce->lrc_reg_state));
Except until we get struct intel_context_engine that line will exceed 80cols!
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v6 1/1 drm/i915: Cache LRC state page in the context
From: Tvrtko Ursulin <[email protected]>
LRC lifetime is well defined so we can cache the page pointing to the object backing store in the context in order to avoid walking over the object SG page list from the interrupt context without the big lock held.
v2: Also cache the mapping. (Chris Wilson)
v3: Unmap on the error path.
v4: No need to cache the page. (Chris Wilson)
v5: No need to dirty the page on unpin. (Chris Wilson)
v6: kmap() cannot fail and use kmap_to_page to simplify unpin.
(Chris Wilson)
--- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_lrc.c | 39 +++++++++++++++++++++------------------ 2 files changed, 22 insertions(+), 18 deletions(-)
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -890,6 +890,7 @@ struct intel_context {int pin_count;struct i915_vma *lrc_vma;u64 lrc_desc; +uint32_t *lrc_reg_state; } engine[I915_NUM_RINGS ];struct list_head link;
drivers/gpu/drm/i915/intel_lrc.c +21 -18
@@ -390,14 +390,7 @@ static int execlists_update_context(struct drm_i915_gem_request *rq) {struct intel_engine_cs *ring = rq->ring;struct i915_hw_ppgtt *ppgtt = rq->ctx->ppgtt; -struct drm_i915_gem_object *ctx_obj = rq->ctx->engine[ring->id].state; -struct page *page; -uint32_t *reg_state; - -BUG_ON (!ctx_obj); - - page =i915_gem_object_get_dirty_page (ctx_obj,LRC_STATE_PN ); - reg_state =kmap_atomic (page); +uint32_t *reg_state = rq->ctx->engine[ring->id].lrc_reg_state; reg_state[CTX_RING_TAIL +1 ] = rq->tail; reg_state[CTX_RING_BUFFER_START +1 ] = rq->ringbuf->vma->node.start;
@@ -414,8 +407,6 @@ static int execlists_update_context(struct drm_i915_gem_request *rq)ASSIGN_CTX_PDP (ppgtt, reg_state,0 ); } -kunmap_atomic (reg_state); -return 0 ; }
@@ -1067,6 +1058,7 @@ static int intel_lr_context_do_pin(struct intel_engine_cs *ring,struct drm_i915_private *dev_priv = dev->dev_private;struct drm_i915_gem_object *ctx_obj = ctx->engine[ring->id].state;struct intel_ringbuffer *ringbuf = ctx->engine[ring->id].ringbuf; +struct page *lrc_state_page;int ret;WARN_ON (!mutex_is_locked (&ring->dev->struct_mutex));
@@ -1076,12 +1068,19 @@ static int intel_lr_context_do_pin(struct intel_engine_cs *ring,if (ret)return ret; + lrc_state_page =i915_gem_object_get_dirty_page (ctx_obj,LRC_STATE_PN ); +if (WARN_ON (!lrc_state_page)) { + ret = -ENODEV ; + goto unpin_ctx_obj; + } + ret =intel_pin_and_map_ringbuffer_obj (ring->dev, ringbuf);if (ret) goto unpin_ctx_obj; ctx->engine[ring->id].lrc_vma =i915_gem_obj_to_ggtt (ctx_obj);intel_lr_context_descriptor_update (ctx, ring); + ctx->engine[ring->id].lrc_reg_state =kmap (lrc_state_page); ctx_obj->dirty = true;/* Invalidate GuC TLB. */
@@ -1119,14 +1118,18 @@ void intel_lr_context_unpin(struct drm_i915_gem_request *rq)struct drm_i915_gem_object *ctx_obj = rq->ctx->engine[ring->id].state;struct intel_ringbuffer *ringbuf = rq->ringbuf; -if (ctx_obj) { -WARN_ON (!mutex_is_locked (&ring->dev->struct_mutex)); -if (--rq->ctx->engine[ring->id].pin_count ==0 ) { -intel_unpin_ringbuffer_obj (ringbuf); -i915_gem_object_ggtt_unpin (ctx_obj); - rq->ctx->engine[ring->id].lrc_vma =NULL ; - rq->ctx->engine[ring->id].lrc_desc =0 ; - } +WARN_ON (!mutex_is_locked (&ring->dev->struct_mutex)); + +if (!ctx_obj) +return ; + +if (--rq->ctx->engine[ring->id].pin_count ==0 ) { +kunmap (kmap_to_page (rq->ctx->engine[ring->id].lrc_reg_state)); +intel_unpin_ringbuffer_obj (ringbuf); +i915_gem_object_ggtt_unpin (ctx_obj); + rq->ctx->engine[ring->id].lrc_vma =NULL ; + rq->ctx->engine[ring->id].lrc_desc =0 ; + rq->ctx->engine[ring->id].lrc_reg_state =NULL ; } }
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6] drm/i915: Cache LRC state page in the context
Quoted 14 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
LRC lifetime is well defined so we can cache the page pointing to the object backing store in the context in order to avoid walking over the object SG page list from the interrupt context without the big lock held.
v2: Also cache the mapping. (Chris Wilson)
v3: Unmap on the error path.
v4: No need to cache the page. (Chris Wilson)
v5: No need to dirty the page on unpin. (Chris Wilson)
v6:kmap()cannot fail and usekmap_to_pageto simplify unpin.
(Chris Wilson)
Quoted 3 lines
Signed-off-by Tvrtko Ursulin <[email protected]>Cc Chris Wilson <[email protected]>Cc Dave Gordon <[email protected]>
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915: Do not call API requiring struct_mutex where it is not available
In reply to Tvrtko Ursulin== Summary ==
== Summary ==
Built on 615fbad7f4cea73b1a8eccdcc942c8ca1a708dab drm-intel-nightly: 2016y-01m-15d-09h-46m-32s UTC integration manifest
Test gem_storedw_loop:
Subgroup basic-render:
pass -> DMESG-WARN (skl-i7k-2) UNSTABLE
Test kms_flip:
Subgroup basic-flip-vs-modeset:
dmesg-warn -> PASS (skl-i5k-2)
Test kms_pipe_crc_basic:
Subgroup read-crc-pipe-b:
pass -> DMESG-WARN (ilk-hp8440p)bdw-nuci7 total:138 pass:128 dwarn:1 dfail:0 fail:0 skip:9 bdw-ultra total:138 pass:132 dwarn:0 dfail:0 fail:0 skip:6 bsw-nuc-2 total:141 pass:115 dwarn:2 dfail:0 fail:0 skip:24 byt-nuc total:141 pass:123 dwarn:3 dfail:0 fail:0 skip:15 hsw-brixbox total:141 pass:134 dwarn:0 dfail:0 fail:0 skip:7 ilk-hp8440p total:141 pass:100 dwarn:4 dfail:0 fail:0 skip:37 ivb-t430s total:135 pass:122 dwarn:3 dfail:4 fail:0 skip:6 skl-i5k-2 total:141 pass:132 dwarn:1 dfail:0 fail:0 skip:8 skl-i7k-2 total:141 pass:131 dwarn:2 dfail:0 fail:0 skip:8 snb-dellxps total:141 pass:122 dwarn:5 dfail:0 fail:0 skip:14 snb-x220t total:141 pass:122 dwarn:5 dfail:0 fail:1 skip:13
HANGED hsw-gt2 in igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a
Results at /archive/results/CI_IGT_test/Patchwork_1199/
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915: Do not call API requiring struct_mutex where it is not available (rev3)
In reply to Tvrtko Ursulin== Summary ==
== Summary ==
Built on 0ea9000bcb6f394edde5111494a92b0607214cfa drm-intel-nightly: 2016y-01m-15d-19h-09m-45s UTC integration manifest
Test gem_ctx_basic:
pass -> FAIL (bdw-ultra)
Test gem_storedw_loop:
Subgroup basic-render:
dmesg-warn -> PASS (bdw-ultra) UNSTABLE
Test kms_flip:
Subgroup basic-flip-vs-wf_vblank:
dmesg-warn -> PASS (snb-dellxps)
Test kms_pipe_crc_basic:
Subgroup hang-read-crc-pipe-a:
pass -> DMESG-WARN (snb-dellxps)
Test pm_rpm:
Subgroup basic-rte:
dmesg-warn -> PASS (byt-nuc) UNSTABLEbdw-nuci7 total:138 pass:128 dwarn:1 dfail:0 fail:0 skip:9 bdw-ultra total:138 pass:131 dwarn:0 dfail:0 fail:1 skip:6 byt-nuc total:141 pass:124 dwarn:2 dfail:0 fail:0 skip:15 hsw-brixbox total:141 pass:134 dwarn:0 dfail:0 fail:0 skip:7 hsw-gt2 total:141 pass:137 dwarn:0 dfail:0 fail:0 skip:4 ivb-t430s total:135 pass:122 dwarn:3 dfail:4 fail:0 skip:6 skl-i5k-2 total:141 pass:132 dwarn:1 dfail:0 fail:0 skip:8 skl-i7k-2 total:141 pass:131 dwarn:2 dfail:0 fail:0 skip:8 snb-dellxps total:141 pass:122 dwarn:5 dfail:0 fail:0 skip:14 snb-x220t total:141 pass:122 dwarn:5 dfail:0 fail:1 skip:13
Results at /archive/results/CI_IGT_test/Patchwork_1203/
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915: Do not call API requiring struct_mutex where it is not available (rev3)
Quoted 5 lines · Patchwork
== Summary ==
Built on
0ea9000bcb6f394edde5111494a92b0607214cfadrm-intel-nightly: 2016y-01m-15d-19h-09m-45s UTC integration manifestTest
gem_ctx_basic:
Quoted 13 lines
pass -> FAIL (bdw-ultra)
Test gem_storedw_loop:
Subgroup basic-render:
dmesg-warn -> PASS (bdw-ultra) UNSTABLE
Test kms_flip:
Subgroup basic-flip-vs-wf_vblank:
dmesg-warn -> PASS (snb-dellxps)
Test kms_pipe_crc_basic:
Subgroup hang-read-crc-pipe-a:
pass -> DMESG-WARN (snb-dellxps)
Test pm_rpm:
Subgroup basic-rte:
dmesg-warn -> PASS (byt-nuc) UNSTABLEI've merged this series since the failures above are known and unrelated.
Regards,
Tvrtko
Quoted 12 lines
bdw-nuci7 total:138 pass:128 dwarn:1 dfail:0 fail:0 skip:9 bdw-ultra total:138 pass:131 dwarn:0 dfail:0 fail:1 skip:6 byt-nuc total:141 pass:124 dwarn:2 dfail:0 fail:0 skip:15 hsw-brixbox total:141 pass:134 dwarn:0 dfail:0 fail:0 skip:7 hsw-gt2 total:141 pass:137 dwarn:0 dfail:0 fail:0 skip:4 ivb-t430s total:135 pass:122 dwarn:3 dfail:4 fail:0 skip:6 skl-i5k-2 total:141 pass:132 dwarn:1 dfail:0 fail:0 skip:8 skl-i7k-2 total:141 pass:131 dwarn:2 dfail:0 fail:0 skip:8 snb-dellxps total:141 pass:122 dwarn:5 dfail:0 fail:0 skip:14 snb-x220t total:141 pass:122 dwarn:5 dfail:0 fail:1 skip:13
Quoted 3 lines
Results at /archive/results/CI_IGT_test/Patchwork_1203/
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx