Add guard padding around i915_vma
Subsystems (3)
v4 cover Add guard padding around i915_vma
Hi,
This series adds guards around vma's but setting a pages at the beginning and at the end that work as padding.
The first user of the vma guard are scanout objects which don't need anymore to add scratch to all the unused ggtt's and speeding up up considerably the boot and resume by several hundreds of milliseconds up to over a full second in slower machines.
Because of this we don't need anymore 2ef6efa79fec ("drm/i915:
Improve on suspend / resume time with VT-d enabled") which gets reverted.
Thanks Tvrtko and Chris for the review.
Andi
Changelog
=========
v3 -> v4:
- change the order of the patches: the 64->32 bit change of the memory alignment goes as first (Tvrtko).
- Use roundup instead of ALIGN to round up the guard padding (Chris).
- Restore the GEM_BUG_ON(2 * guard > end) as a paranoiac check and as mean of documentation (Chris).
v2 -> v3:
- fix Tvrtko's comments: explain in a comment why the guard is is alligned as the vma and remove a GEM_BUG_ON() in case the the total padding was exceeding the size of the va.
- the display_alignment is declared as u32 instead of a u64 in a separate patch.
v1 -> v2:
- Revert 2ef6efa79fec ("drm/i915: Improve on suspend / resume time with VT-d enabled")
Andi Shyti (2):
drm/i915: Limit the display memory alignment to 32 bit instead of 64 Revert "drm/i915: Improve on suspend / resume time with VT-d enabled"
Chris Wilson (3):
drm/i915: Wrap all access to i915_vma.node.start|size drm/i915: Introduce guard pages to i915_vma drm/i915: Refine VT-d scanout workaround
drivers/gpu/drm/i915/display/intel_fb_pin.c | 2 +- drivers/gpu/drm/i915/display/intel_fbdev.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_domain.c | 15 ++- .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 33 +++--- drivers/gpu/drm/i915/gem/i915_gem_mman.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_shrinker.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_tiling.c | 4 +- .../gpu/drm/i915/gem/selftests/huge_pages.c | 2 +- .../i915/gem/selftests/i915_gem_client_blt.c | 23 ++-- .../drm/i915/gem/selftests/i915_gem_context.c | 15 ++- .../drm/i915/gem/selftests/i915_gem_mman.c | 2 +- .../drm/i915/gem/selftests/igt_gem_utils.c | 7 +- drivers/gpu/drm/i915/gt/gen7_renderclear.c | 2 +- drivers/gpu/drm/i915/gt/intel_ggtt.c | 108 ++++-------------- drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c | 3 +- drivers/gpu/drm/i915/gt/intel_gtt.h | 24 ---- drivers/gpu/drm/i915/gt/intel_renderstate.c | 2 +- .../gpu/drm/i915/gt/intel_ring_submission.c | 2 +- drivers/gpu/drm/i915/gt/selftest_engine_cs.c | 8 +- drivers/gpu/drm/i915/gt/selftest_execlists.c | 18 +-- drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 15 +-- drivers/gpu/drm/i915/gt/selftest_lrc.c | 16 +-- .../drm/i915/gt/selftest_ring_submission.c | 2 +- drivers/gpu/drm/i915/gt/selftest_rps.c | 12 +- .../gpu/drm/i915/gt/selftest_workarounds.c | 8 +- drivers/gpu/drm/i915/i915_cmd_parser.c | 4 +- drivers/gpu/drm/i915/i915_debugfs.c | 2 +- drivers/gpu/drm/i915/i915_driver.c | 16 --- drivers/gpu/drm/i915/i915_gem_gtt.h | 3 +- drivers/gpu/drm/i915/i915_perf.c | 2 +- drivers/gpu/drm/i915/i915_vma.c | 63 +++++++--- drivers/gpu/drm/i915/i915_vma.h | 52 ++++++++- drivers/gpu/drm/i915/i915_vma_resource.c | 4 +- drivers/gpu/drm/i915/i915_vma_resource.h | 17 ++- drivers/gpu/drm/i915/i915_vma_types.h | 3 +- drivers/gpu/drm/i915/selftests/i915_request.c | 20 ++-- drivers/gpu/drm/i915/selftests/igt_spinner.c | 8 +- 37 files changed, 264 insertions(+), 259 deletions(-)
Signature · 1 line
2.38.1
PATCH v4 1/5 drm/i915: Limit the display memory alignment to 32 bit instead of 64
The coming commit "drm/i915: Introduce guard pages to i915_vma" from Chris, was originally changing display_alignment to u32 from u64. The reason is that the display GGTT is and will be limited o 4GB.
Put it in a separate patch and use "max(...)" instead of "max_t(64, ...)" when asigning the value. We can safely use max as we know beforehand that the comparison is between two u32 variables.
--- drivers/gpu/drm/i915/display/intel_fb_pin.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_domain.c | 2 +- drivers/gpu/drm/i915/i915_vma_types.h | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/display/intel_fb_pin.c +1 -1
@@ -91,7 +91,7 @@ intel_pin_fb_obj_dpt(struct drm_framebuffer *fb, goto err; } - vma->display_alignment =max_t (u64, vma->display_alignment, alignment); + vma->display_alignment =max (vma->display_alignment, alignment);i915_gem_object_flush_if_display (obj);
drivers/gpu/drm/i915/gem/i915_gem_domain.c +1 -1
@@ -444,7 +444,7 @@ i915_gem_object_pin_to_display_plane(struct drm_i915_gem_object *obj,if (IS_ERR (vma))return vma; - vma->display_alignment =max_t (u64, vma->display_alignment, alignment); + vma->display_alignment =max (vma->display_alignment, alignment);i915_vma_mark_scanout (vma);i915_gem_object_flush_if_display_locked (obj);
drivers/gpu/drm/i915/i915_vma_types.h +1 -1
@@ -197,7 +197,6 @@ struct i915_vma {struct i915_fence_reg *fence;u64 size; -u64 display_alignment;struct i915_page_sizes page_sizes;/* mmap-offset associated with fencing for this vma */
@@ -205,6 +204,7 @@ struct i915_vma {u32 fence_size;u32 fence_alignment; +u32 display_alignment;/** * Count of the number of times this vma has been opened by different
Signature · 1 line
2.38.1
PATCH v4 2/5 drm/i915: Wrap all access to i915_vma.node.start|size
In reply to Andi ShytiFrom: Chris Wilson <[email protected]>
We already wrap i915_vma.node.start for use with the GGTT, as there we can perform additional sanity checks that the node belongs to the GGTT and fits within the 32b registers. In the next couple of patches, we will introduce guard pages around the objects _inside_ the drm_mm_node allocation. That is we will offset the vma->pages so that the first page is at drm_mm_node.start + vma->guard (not 0 as is currently the case). All users must then not use i915_vma.node.start directly, but compute the guard offset, thus all users are converted to use a i915_vma_offset() wrapper.
The notable exceptions are the selftests that are testing exact behaviour of i915_vma_pin/i915_vma_insert.
--- drivers/gpu/drm/i915/display/intel_fbdev.c | 2 +- .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 33 ++++++------ drivers/gpu/drm/i915/gem/i915_gem_mman.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_shrinker.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_tiling.c | 4 +- .../gpu/drm/i915/gem/selftests/huge_pages.c | 2 +- .../i915/gem/selftests/i915_gem_client_blt.c | 23 +++++---- .../drm/i915/gem/selftests/i915_gem_context.c | 15 +++--- .../drm/i915/gem/selftests/i915_gem_mman.c | 2 +- .../drm/i915/gem/selftests/igt_gem_utils.c | 7 +-- drivers/gpu/drm/i915/gt/gen7_renderclear.c | 2 +- drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c | 3 +- drivers/gpu/drm/i915/gt/intel_renderstate.c | 2 +- .../gpu/drm/i915/gt/intel_ring_submission.c | 2 +- drivers/gpu/drm/i915/gt/selftest_engine_cs.c | 8 +-- drivers/gpu/drm/i915/gt/selftest_execlists.c | 18 +++---- drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 15 +++--- drivers/gpu/drm/i915/gt/selftest_lrc.c | 16 +++--- .../drm/i915/gt/selftest_ring_submission.c | 2 +- drivers/gpu/drm/i915/gt/selftest_rps.c | 12 ++--- .../gpu/drm/i915/gt/selftest_workarounds.c | 8 +-- drivers/gpu/drm/i915/i915_cmd_parser.c | 4 +- drivers/gpu/drm/i915/i915_debugfs.c | 2 +- drivers/gpu/drm/i915/i915_perf.c | 2 +- drivers/gpu/drm/i915/i915_vma.c | 25 ++++----- drivers/gpu/drm/i915/i915_vma.h | 51 +++++++++++++++++-- drivers/gpu/drm/i915/i915_vma_resource.h | 10 ++-- drivers/gpu/drm/i915/selftests/i915_request.c | 20 ++++---- drivers/gpu/drm/i915/selftests/igt_spinner.c | 8 +-- 29 files changed, 180 insertions(+), 122 deletions(-)
drivers/gpu/drm/i915/display/intel_fbdev.c +1 -1
@@ -286,7 +286,7 @@ static int intelfb_create(struct drm_fb_helper *helper,/* Our framebuffer is the entirety of fbdev's system memory */ info->fix.smem_start = - (unsigned long )(ggtt->gmadr.start + vma->node.start); + (unsigned long )(ggtt->gmadr.start +i915_ggtt_offset (vma)); info->fix.smem_len = vma->size; }
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c +18 -15
@@ -379,22 +379,25 @@ eb_vma_misplaced(const struct drm_i915_gem_exec_object2 *entry,const struct i915_vma *vma, unsigned int flags) { - if (vma->node.size < entry->pad_to_size) + const u64 start = i915_vma_offset(vma); +const u64 size =i915_vma_size (vma); + +if (size < entry->pad_to_size)return true; -if (entry->alignment && !IS_ALIGNED (vma->node.start, entry->alignment)) +if (entry->alignment && !IS_ALIGNED (start, entry->alignment))return true;if (flags &EXEC_OBJECT_PINNED && - vma->node.start != entry->offset) + start != entry->offset)return true;if (flags & __EXEC_OBJECT_NEEDS_BIAS && - vma->node.start <BATCH_OFFSET_BIAS ) + start <BATCH_OFFSET_BIAS )return true;if (!(flags &EXEC_OBJECT_SUPPORTS_48B_ADDRESS ) && - (vma->node.start + vma->node.size +4095 ) >>32 ) + (start + size +4095 ) >>32 )return true; if (flags & __EXEC_OBJECT_NEEDS_MAP &&
@@ -440,7 +443,7 @@ eb_pin_vma(struct i915_execbuffer *eb,int err;if (vma->node.size) - pin_flags = vma->node.start; + pin_flags =__i915_vma_offset (vma);else pin_flags = entry->offset &PIN_OFFSET_MASK ;
@@ -663,8 +666,8 @@ static int eb_reserve_vma(struct i915_execbuffer *eb,if (err)return err; -if (entry->offset != vma->node.start) { - entry->offset = vma->node.start |UPDATE ; +if (entry->offset !=i915_vma_offset (vma)) { + entry->offset =i915_vma_offset (vma) |UPDATE ; eb->args->flags |= __EXEC_HAS_RELOC; }
@@ -984,8 +987,8 @@ static int eb_validate_vmas(struct i915_execbuffer *eb)return err;if (!err) { -if (entry->offset != vma->node.start) { - entry->offset = vma->node.start |UPDATE ; +if (entry->offset !=i915_vma_offset (vma)) { + entry->offset =i915_vma_offset (vma) |UPDATE ; eb->args->flags |= __EXEC_HAS_RELOC; } }else {
@@ -1066,7 +1069,7 @@ static inline u64 relocation_target(const struct drm_i915_gem_relocation_entry *reloc, const struct i915_vma *target) { - return gen8_canonical_addr((int)reloc->delta + target->node.start); + return gen8_canonical_addr((int)reloc->delta + i915_vma_offset(target)); } static void reloc_cache_init(struct reloc_cache *cache,
@@ -1275,7 +1278,7 @@ static void *reloc_iomap(struct i915_vma *batch,if (err)/* no inactive aperture space, use cpu reloc */ return NULL ; }else { - cache->node.start = vma->node.start; + cache->node.start =i915_ggtt_offset (vma); cache->node.mm = (void *)vma; } }
@@ -1438,7 +1441,7 @@ eb_relocate_entry(struct i915_execbuffer *eb,* more work needs to be done. */ if (!DBG_FORCE_RELOC && -gen8_canonical_addr (target->vma->node.start) == reloc->presumed_offset) +gen8_canonical_addr (i915_vma_offset (target->vma)) == reloc->presumed_offset)return 0 ;/* Check that the relocation address is valid... */
@@ -2368,7 +2371,7 @@ static int eb_request_submit(struct i915_execbuffer *eb, } err = rq->context->engine->emit_bb_start (rq, - batch->node.start + +i915_vma_offset (batch) + eb->batch_start_offset, batch_len, eb->batch_flags);
@@ -2379,7 +2382,7 @@ static int eb_request_submit(struct i915_execbuffer *eb,GEM_BUG_ON (intel_context_is_parallel (rq->context));GEM_BUG_ON (eb->batch_start_offset); err = rq->context->engine->emit_bb_start (rq, - eb->trampoline->node.start + +i915_vma_offset (eb->trampoline) + batch_len,0 ,0 );if (err)return err;
drivers/gpu/drm/i915/gem/i915_gem_mman.c +1 -1
@@ -395,7 +395,7 @@ static vm_fault_t vm_fault_gtt(struct vm_fault *vmf)/* Finally, remap it using the new GTT offset */ ret =remap_io_mapping (area, area->vm_start + (vma->gtt_view.partial.offset <<PAGE_SHIFT ), - (ggtt->gmadr.start + vma->node.start) >>PAGE_SHIFT , + (ggtt->gmadr.start +i915_ggtt_offset (vma)) >>PAGE_SHIFT ,min_t (u64, vma->size, area->vm_end - area->vm_start), &ggtt->iomap);if (ret)
drivers/gpu/drm/i915/gem/i915_gem_shrinker.c +1 -1
@@ -400,7 +400,7 @@ i915_gem_shrinker_vmap(struct notifier_block *nb, unsigned long event, void *ptrmutex_lock (&to_gt (i915)->ggtt->vm.mutex);list_for_each_entry_safe (vma, next, &to_gt (i915)->ggtt->vm.bound_list, vm_link) { -unsigned long count = vma->node.size >>PAGE_SHIFT ; +unsigned long count =i915_vma_size (vma) >>PAGE_SHIFT ;struct drm_i915_gem_object *obj = vma->obj;if (!vma->iomap ||i915_vma_is_active (vma))
drivers/gpu/drm/i915/gem/i915_gem_tiling.c +2 -2
@@ -168,11 +168,11 @@ static bool i915_vma_fence_prepare(struct i915_vma *vma,return true; size =i915_gem_fence_size (i915, vma->size, tiling_mode, stride); -if (vma->node.size < size) +if (i915_vma_size (vma) < size)return false; alignment =i915_gem_fence_alignment (i915, vma->size, tiling_mode, stride); -if (!IS_ALIGNED (vma->node.start, alignment)) +if (!IS_ALIGNED (i915_ggtt_offset (vma), alignment))return false;return true;
drivers/gpu/drm/i915/gem/selftests/huge_pages.c +1 -1
@@ -400,7 +400,7 @@ static int igt_check_page_sizes(struct i915_vma *vma)* Maintaining alignment is required to utilise huge pages in the ppGGT. */ if (i915_gem_object_is_lmem (obj) && -IS_ALIGNED (vma->node.start,SZ_2M ) && +IS_ALIGNED (i915_vma_offset (vma),SZ_2M ) && vma->page_sizes.sg &SZ_2M && vma->resource->page_sizes_gtt <SZ_2M ) { pr_err("gtt pages mismatch for LMEM, expected 2M GTT pages, sg(%u), gtt(%u)\n",
drivers/gpu/drm/i915/gem/selftests/i915_gem_client_blt.c +12 -11
@@ -194,12 +194,12 @@ static int prepare_blit(const struct tiled_blits *t, *cs++ = src_4t | dst_4t |BLT_DEPTH_32 | dst_pitch; *cs++ =0 ; *cs++ = t->height <<16 | t->width; - *cs++ =lower_32_bits (dst->vma->node.start); - *cs++ =upper_32_bits (dst->vma->node.start); + *cs++ =lower_32_bits (i915_vma_offset (dst->vma)); + *cs++ =upper_32_bits (i915_vma_offset (dst->vma)); *cs++ =0 ; *cs++ = src_pitch; - *cs++ =lower_32_bits (src->vma->node.start); - *cs++ =upper_32_bits (src->vma->node.start); + *cs++ =lower_32_bits (i915_vma_offset (src->vma)); + *cs++ =upper_32_bits (i915_vma_offset (src->vma)); }else {if (ver >=6 ) { *cs++ =MI_LOAD_REGISTER_IMM (1 );
@@ -240,14 +240,14 @@ static int prepare_blit(const struct tiled_blits *t, *cs++ =BLT_DEPTH_32 |BLT_ROP_SRC_COPY | dst_pitch; *cs++ =0 ; *cs++ = t->height <<16 | t->width; - *cs++ =lower_32_bits (dst->vma->node.start); + *cs++ =lower_32_bits (i915_vma_offset (dst->vma));if (use_64b_reloc) - *cs++ =upper_32_bits (dst->vma->node.start); + *cs++ =upper_32_bits (i915_vma_offset (dst->vma)); *cs++ =0 ; *cs++ = src_pitch; - *cs++ =lower_32_bits (src->vma->node.start); + *cs++ =lower_32_bits (i915_vma_offset (src->vma));if (use_64b_reloc) - *cs++ =upper_32_bits (src->vma->node.start); + *cs++ =upper_32_bits (i915_vma_offset (src->vma)); } *cs++ =MI_BATCH_BUFFER_END ;
@@ -462,7 +462,7 @@ static int pin_buffer(struct i915_vma *vma, u64 addr) {int err; -if (drm_mm_node_allocated (&vma->node) && vma->node.start != addr) { +if (drm_mm_node_allocated (&vma->node) &&i915_vma_offset (vma) != addr) { err =i915_vma_unbind_unlocked (vma);if (err)return err;
@@ -472,6 +472,7 @@ static int pin_buffer(struct i915_vma *vma, u64 addr)if (err)return err; +GEM_BUG_ON (i915_vma_offset (vma) != addr);return 0 ; }
@@ -518,8 +519,8 @@ tiled_blit(struct tiled_blits *t, err =igt_vma_move_to_active_unlocked (dst->vma, rq,0 );if (!err) err = rq->engine->emit_bb_start (rq, - t->batch->node.start, - t->batch->node.size, +i915_vma_offset (t->batch), +i915_vma_size (t->batch),0 );i915_request_get (rq);i915_request_add (rq);
drivers/gpu/drm/i915/gem/selftests/i915_gem_context.c +9 -6
@@ -914,8 +914,8 @@ static int rpcs_query_batch(struct drm_i915_gem_object *rpcs, *cmd++ =MI_STORE_REGISTER_MEM_GEN8 ; *cmd++ =i915_mmio_reg_offset (GEN8_R_PWR_CLK_STATE (engine->mmio_base)); - *cmd++ =lower_32_bits (vma->node.start); - *cmd++ =upper_32_bits (vma->node.start); + *cmd++ =lower_32_bits (i915_vma_offset (vma)); + *cmd++ =upper_32_bits (i915_vma_offset (vma)); *cmd =MI_BATCH_BUFFER_END ;__i915_gem_object_flush_map (rpcs,0 ,64 );
@@ -999,7 +999,8 @@ emit_rpcs_query(struct drm_i915_gem_object *obj, } err = rq->engine->emit_bb_start (rq, - batch->node.start, batch->node.size, +i915_vma_offset (batch), +i915_vma_size (batch),0 );if (err) goto skip_request;
@@ -1560,7 +1561,8 @@ static int write_to_scratch(struct i915_gem_context *ctx, goto skip_request; } - err = engine->emit_bb_start (rq, vma->node.start, vma->node.size,0 ); + err = engine->emit_bb_start (rq,i915_vma_offset (vma), +i915_vma_size (vma),0 );if (err) goto skip_request;
@@ -1665,7 +1667,7 @@ static int read_from_scratch(struct i915_gem_context *ctx, *cmd++ = offset; *cmd++ =MI_STORE_REGISTER_MEM |MI_USE_GGTT ; *cmd++ = reg; - *cmd++ = vma->node.start + result; + *cmd++ =i915_vma_offset (vma) + result; *cmd =MI_BATCH_BUFFER_END ;i915_gem_object_flush_map (obj);
@@ -1694,7 +1696,8 @@ static int read_from_scratch(struct i915_gem_context *ctx, goto skip_request; } - err = engine->emit_bb_start (rq, vma->node.start, vma->node.size, flags); + err = engine->emit_bb_start (rq,i915_vma_offset (vma), +i915_vma_size (vma), flags);if (err) goto skip_request;
drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c +1 -1
@@ -1609,7 +1609,7 @@ static int __igt_mmap_gpu(struct drm_i915_private *i915, err =i915_vma_move_to_active (vma, rq,0 ); - err = engine->emit_bb_start (rq, vma->node.start,0 ,0 ); + err = engine->emit_bb_start (rq,i915_vma_offset (vma),0 ,0 );i915_request_get (rq);i915_request_add (rq);
drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c +4 -3
@@ -62,8 +62,8 @@ igt_emit_store_dw(struct i915_vma *vma, goto err; } -GEM_BUG_ON (offset + (count -1 ) *PAGE_SIZE > vma->node.size); - offset += vma->node.start; +GEM_BUG_ON (offset + (count -1 ) *PAGE_SIZE >i915_vma_size (vma)); + offset +=i915_vma_offset (vma);for (n =0 ; n < count; n++) {if (ver >=8 ) {
@@ -147,7 +147,8 @@ int igt_gpu_fill_dw(struct intel_context *ce, flags |=I915_DISPATCH_SECURE ; err = rq->engine->emit_bb_start (rq, - batch->node.start, batch->node.size, +i915_vma_offset (batch), +i915_vma_size (batch), flags); skip_request:
drivers/gpu/drm/i915/gt/gen7_renderclear.c +1 -1
@@ -106,7 +106,7 @@ static u32 batch_offset(const struct batch_chunk *bc, u32 *cs)static u32 batch_addr (const struct batch_chunk *bc) { -return bc->vma->node.start; +return i915_vma_offset (bc->vma); }static void batch_add (struct batch_chunk *bc,const u32 d)
drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c +2 -1
@@ -220,7 +220,8 @@ static int fence_update(struct i915_fence_reg *fence,return ret; } - fence->start = vma->node.start; +GEM_BUG_ON (vma->fence_size >i915_vma_size (vma)); + fence->start =i915_ggtt_offset (vma); fence->size = vma->fence_size; fence->stride =i915_gem_object_get_stride (vma->obj); fence->tiling =i915_gem_object_get_tiling (vma->obj);
drivers/gpu/drm/i915/gt/intel_renderstate.c +1 -1
@@ -63,7 +63,7 @@ static int render_state_setup(struct intel_renderstate *so,u32 s = rodata->batch[i];if (i *4 == rodata->reloc[reloc_index]) { -u64 r = s + so->vma->node.start; +u64 r = s +i915_vma_offset (so->vma); s =lower_32_bits (r);if (HAS_64BIT_RELOC (i915)) {
drivers/gpu/drm/i915/gt/intel_ring_submission.c +1 -1
@@ -897,7 +897,7 @@ static int clear_residuals(struct i915_request *rq) } ret = engine->emit_bb_start (rq, - engine->wa_ctx.vma->node.start,0 , +i915_vma_offset (engine->wa_ctx.vma),0 ,0 );if (ret)return ret;
drivers/gpu/drm/i915/gt/selftest_engine_cs.c +4 -4
@@ -178,7 +178,7 @@ static int perf_mi_bb_start(void *arg) goto out; err = rq->engine->emit_bb_start (rq, - batch->node.start,8 , +i915_vma_offset (batch),8 ,0 );if (err) goto out;
@@ -321,7 +321,7 @@ static int perf_mi_noop(void *arg) goto out; err = rq->engine->emit_bb_start (rq, - base->node.start,8 , +i915_vma_offset (base),8 ,0 );if (err) goto out;
@@ -331,8 +331,8 @@ static int perf_mi_noop(void *arg) goto out; err = rq->engine->emit_bb_start (rq, - nop->node.start, - nop->node.size, +i915_vma_offset (nop), +i915_vma_size (nop),0 );if (err) goto out;
drivers/gpu/drm/i915/gt/selftest_execlists.c +9 -9
@@ -2737,11 +2737,11 @@ static int create_gang(struct intel_engine_cs *engine,MI_SEMAPHORE_POLL |MI_SEMAPHORE_SAD_EQ_SDD ; *cs++ =0 ; - *cs++ =lower_32_bits (vma->node.start); - *cs++ =upper_32_bits (vma->node.start); + *cs++ =lower_32_bits (i915_vma_offset (vma)); + *cs++ =upper_32_bits (i915_vma_offset (vma));if (*prev) { -u64 offset = (*prev)->batch->node.start; +u64 offset =i915_vma_offset ((*prev)->batch);/* Terminate the spinner in the next lower priority batch. */ *cs++ =MI_STORE_DWORD_IMM_GEN4 ;
@@ -2767,7 +2767,7 @@ static int create_gang(struct intel_engine_cs *engine, err =i915_vma_move_to_active (vma, rq,0 );if (!err) err = rq->engine->emit_bb_start (rq, - vma->node.start, +i915_vma_offset (vma),PAGE_SIZE ,0 );i915_vma_unlock (vma);i915_request_add (rq);
@@ -3095,7 +3095,7 @@ create_gpr_user(struct intel_engine_cs *engine, *cs++ =MI_MATH_ADD ; *cs++ =MI_MATH_STORE (MI_MATH_REG (i),MI_MATH_REG_ACCU ); - addr = result->node.start + offset + i *sizeof (*cs); + addr =i915_vma_offset (result) + offset + i *sizeof (*cs); *cs++ =MI_STORE_REGISTER_MEM_GEN8 ; *cs++ =CS_GPR (engine,2 * i); *cs++ =lower_32_bits (addr);
@@ -3105,8 +3105,8 @@ create_gpr_user(struct intel_engine_cs *engine,MI_SEMAPHORE_POLL |MI_SEMAPHORE_SAD_GTE_SDD ; *cs++ = i; - *cs++ =lower_32_bits (result->node.start); - *cs++ =upper_32_bits (result->node.start); + *cs++ =lower_32_bits (i915_vma_offset (result)); + *cs++ =upper_32_bits (i915_vma_offset (result)); } *cs++ =MI_BATCH_BUFFER_END ;
@@ -3186,7 +3186,7 @@ create_gpr_client(struct intel_engine_cs *engine, err =i915_vma_move_to_active (batch, rq,0 );if (!err) err = rq->engine->emit_bb_start (rq, - batch->node.start, +i915_vma_offset (batch),PAGE_SIZE ,0 );i915_vma_unlock (batch);i915_vma_unpin (batch);
@@ -3518,7 +3518,7 @@ static int smoke_submit(struct preempt_smoke *smoke, err =i915_vma_move_to_active (vma, rq,0 );if (!err) err = rq->engine->emit_bb_start (rq, - vma->node.start, +i915_vma_offset (vma),PAGE_SIZE ,0 );i915_vma_unlock (vma); }
drivers/gpu/drm/i915/gt/selftest_hangcheck.c +8 -7
@@ -96,7 +96,8 @@ static int hang_init(struct hang *h, struct intel_gt *gt)static u64 hws_address (const struct i915_vma *hws,const struct i915_request *rq) { -return hws->node.start +offset_in_page (sizeof (u32)*rq->fence.context); +return i915_vma_offset (hws) + +offset_in_page (sizeof (u32) * rq->fence.context); } static struct i915_request *
@@ -180,8 +181,8 @@ hang_create_request(struct hang *h, struct intel_engine_cs *engine) *batch++ =MI_NOOP ; *batch++ =MI_BATCH_BUFFER_START |1 <<8 |1 ; - *batch++ =lower_32_bits (vma->node.start); - *batch++ =upper_32_bits (vma->node.start); + *batch++ =lower_32_bits (i915_vma_offset (vma)); + *batch++ =upper_32_bits (i915_vma_offset (vma)); }else if (GRAPHICS_VER (gt->i915) >=6 ) { *batch++ =MI_STORE_DWORD_IMM_GEN4 ; *batch++ =0 ;
@@ -194,7 +195,7 @@ hang_create_request(struct hang *h, struct intel_engine_cs *engine) *batch++ =MI_NOOP ; *batch++ =MI_BATCH_BUFFER_START |1 <<8 ; - *batch++ =lower_32_bits (vma->node.start); + *batch++ =lower_32_bits (i915_vma_offset (vma)); }else if (GRAPHICS_VER (gt->i915) >=4 ) { *batch++ =MI_STORE_DWORD_IMM_GEN4 |MI_USE_GGTT ; *batch++ =0 ;
@@ -207,7 +208,7 @@ hang_create_request(struct hang *h, struct intel_engine_cs *engine) *batch++ =MI_NOOP ; *batch++ =MI_BATCH_BUFFER_START |2 <<6 ; - *batch++ =lower_32_bits (vma->node.start); + *batch++ =lower_32_bits (i915_vma_offset (vma)); }else { *batch++ =MI_STORE_DWORD_IMM |MI_MEM_VIRTUAL ; *batch++ =lower_32_bits (hws_address (hws, rq));
@@ -219,7 +220,7 @@ hang_create_request(struct hang *h, struct intel_engine_cs *engine) *batch++ =MI_NOOP ; *batch++ =MI_BATCH_BUFFER_START |2 <<6 ; - *batch++ =lower_32_bits (vma->node.start); + *batch++ =lower_32_bits (i915_vma_offset (vma)); } *batch++ =MI_BATCH_BUFFER_END ;/* not reached */ intel_gt_chipset_flush (engine->gt);
@@ -234,7 +235,7 @@ hang_create_request(struct hang *h, struct intel_engine_cs *engine)if (GRAPHICS_VER (gt->i915) <=5 ) flags |=I915_DISPATCH_SECURE ; - err = rq->engine->emit_bb_start (rq, vma->node.start,PAGE_SIZE , flags); + err = rq->engine->emit_bb_start (rq,i915_vma_offset (vma),PAGE_SIZE , flags); cancel_rq:if (err) {
drivers/gpu/drm/i915/gt/selftest_lrc.c +8 -8
@@ -1030,8 +1030,8 @@ store_context(struct intel_context *ce, struct i915_vma *scratch)while (len--) { *cs++ =MI_STORE_REGISTER_MEM_GEN8 ; *cs++ = hw[dw]; - *cs++ =lower_32_bits (scratch->node.start + x); - *cs++ =upper_32_bits (scratch->node.start + x); + *cs++ =lower_32_bits (i915_vma_offset (scratch) + x); + *cs++ =upper_32_bits (i915_vma_offset (scratch) + x); dw +=2 ; x +=4 ;
@@ -1098,8 +1098,8 @@ record_registers(struct intel_context *ce, *cs++ =MI_ARB_ON_OFF |MI_ARB_DISABLE ; *cs++ =MI_BATCH_BUFFER_START_GEN8 |BIT (8 ); - *cs++ =lower_32_bits (b_before->node.start); - *cs++ =upper_32_bits (b_before->node.start); + *cs++ =lower_32_bits (i915_vma_offset (b_before)); + *cs++ =upper_32_bits (i915_vma_offset (b_before)); *cs++ =MI_ARB_ON_OFF |MI_ARB_ENABLE ; *cs++ = MI_SEMAPHORE_WAIT |
@@ -1114,8 +1114,8 @@ record_registers(struct intel_context *ce, *cs++ =MI_ARB_ON_OFF |MI_ARB_DISABLE ; *cs++ =MI_BATCH_BUFFER_START_GEN8 |BIT (8 ); - *cs++ =lower_32_bits (b_after->node.start); - *cs++ =upper_32_bits (b_after->node.start); + *cs++ =lower_32_bits (i915_vma_offset (b_after)); + *cs++ =upper_32_bits (i915_vma_offset (b_after));intel_ring_advance (rq, cs);
@@ -1236,8 +1236,8 @@ static int poison_registers(struct intel_context *ce, u32 poison, u32 *sema) *cs++ =MI_ARB_ON_OFF |MI_ARB_DISABLE ; *cs++ =MI_BATCH_BUFFER_START_GEN8 |BIT (8 ); - *cs++ =lower_32_bits (batch->node.start); - *cs++ =upper_32_bits (batch->node.start); + *cs++ =lower_32_bits (i915_vma_offset (batch)); + *cs++ =upper_32_bits (i915_vma_offset (batch)); *cs++ =MI_STORE_DWORD_IMM_GEN4 |MI_USE_GGTT ; *cs++ = i915_ggtt_offset(ce->engine->status_page.vma) +
drivers/gpu/drm/i915/gt/selftest_ring_submission.c +1 -1
@@ -50,7 +50,7 @@ static struct i915_vma *create_wally(struct intel_engine_cs *engine) }else { *cs++ =MI_STORE_DWORD_IMM |MI_MEM_VIRTUAL ; } - *cs++ = vma->node.start +4000 ; + *cs++ =i915_vma_offset (vma) +4000 ; *cs++ =STACK_MAGIC ; *cs++ =MI_BATCH_BUFFER_END ;
drivers/gpu/drm/i915/gt/selftest_rps.c +6 -6
@@ -122,14 +122,14 @@ create_spin_counter(struct intel_engine_cs *engine,if (srm) { *cs++ =MI_STORE_REGISTER_MEM_GEN8 ; *cs++ =i915_mmio_reg_offset (CS_GPR (COUNT )); - *cs++ =lower_32_bits (vma->node.start + end *sizeof (*cs)); - *cs++ =upper_32_bits (vma->node.start + end *sizeof (*cs)); + *cs++ =lower_32_bits (i915_vma_offset (vma) + end *sizeof (*cs)); + *cs++ =upper_32_bits (i915_vma_offset (vma) + end *sizeof (*cs)); } } *cs++ =MI_BATCH_BUFFER_START_GEN8 ; - *cs++ =lower_32_bits (vma->node.start + loop *sizeof (*cs)); - *cs++ =upper_32_bits (vma->node.start + loop *sizeof (*cs)); + *cs++ =lower_32_bits (i915_vma_offset (vma) + loop *sizeof (*cs)); + *cs++ =upper_32_bits (i915_vma_offset (vma) + loop *sizeof (*cs));GEM_BUG_ON (cs - base > end);i915_gem_object_flush_map (obj);
@@ -655,7 +655,7 @@ int live_rps_frequency_cs(void *arg) err =i915_vma_move_to_active (vma, rq,0 );if (!err) err = rq->engine->emit_bb_start (rq, - vma->node.start, +i915_vma_offset (vma),PAGE_SIZE ,0 );i915_request_add (rq);if (err)
@@ -794,7 +794,7 @@ int live_rps_frequency_srm(void *arg) err =i915_vma_move_to_active (vma, rq,0 );if (!err) err = rq->engine->emit_bb_start (rq, - vma->node.start, +i915_vma_offset (vma),PAGE_SIZE ,0 );i915_request_add (rq);if (err)
drivers/gpu/drm/i915/gt/selftest_workarounds.c +4 -4
@@ -521,7 +521,7 @@ static int check_dirty_whitelist(struct intel_context *ce)for (i =0 ; i < engine->whitelist.count; i++) {u32 reg =i915_mmio_reg_offset (engine->whitelist.list[i].reg);struct i915_gem_ww_ctx ww; -u64 addr = scratch->node.start; +u64 addr =i915_vma_offset (scratch);struct i915_request *rq;u32 srm, lrm, rsvd;u32 expect;
@@ -640,7 +640,7 @@ static int check_dirty_whitelist(struct intel_context *ce) goto err_request; err = engine->emit_bb_start (rq, - batch->node.start,PAGE_SIZE , +i915_vma_offset (batch),PAGE_SIZE ,0 );if (err) goto err_request;
@@ -870,7 +870,7 @@ static int read_whitelisted_registers(struct intel_context *ce, }for (i =0 ; i < engine->whitelist.count; i++) { -u64 offset = results->node.start +sizeof (u32) * i; +u64 offset =i915_vma_offset (results) +sizeof (u32) * i;u32 reg =i915_mmio_reg_offset (engine->whitelist.list[i].reg);/* Clear non priv flags */
@@ -942,7 +942,7 @@ static int scrub_whitelisted_registers(struct intel_context *ce) goto err_request;/* Perform the writes from an unprivileged "user" batch */ - err = engine->emit_bb_start (rq, batch->node.start,0 ,0 ); + err = engine->emit_bb_start (rq,i915_vma_offset (batch),0 ,0 ); err_request: err =request_add_sync (rq, err);
drivers/gpu/drm/i915/i915_cmd_parser.c +2 -2
@@ -1471,8 +1471,8 @@ int intel_engine_cmd_parser(struct intel_engine_cs *engine,/* Defer failure until attempted use */ jump_whitelist =alloc_whitelist (batch_length); - shadow_addr =gen8_canonical_addr (shadow->node.start); - batch_addr =gen8_canonical_addr (batch->node.start + batch_offset); + shadow_addr =gen8_canonical_addr (i915_vma_offset (shadow)); + batch_addr =gen8_canonical_addr (i915_vma_offset (batch) + batch_offset);/* * We use the batch length as size because the shadow object is as
drivers/gpu/drm/i915/i915_debugfs.c +1 -1
@@ -183,7 +183,7 @@ i915_debugfs_describe_obj(struct seq_file *m, struct drm_i915_gem_object *obj)seq_printf (m," (%s offset: %08llx, size: %08llx, pages: %s" ,stringify_vma_type (vma), - vma->node.start, vma->node.size, +i915_vma_offset (vma),i915_vma_size (vma),stringify_page_sizes (vma->resource->page_sizes_gtt,NULL ,0 ));if (i915_vma_is_ggtt (vma) ||i915_vma_is_dpt (vma)) {
drivers/gpu/drm/i915/i915_perf.c +1 -1
@@ -2259,7 +2259,7 @@ emit_oa_config(struct i915_perf_stream *stream, goto err_add_request; err = rq->engine->emit_bb_start (rq, - vma->node.start,0 , +i915_vma_offset (vma),0 ,I915_DISPATCH_SECURE );if (err) goto err_add_request;
drivers/gpu/drm/i915/i915_vma.c +13 -12
@@ -418,8 +418,8 @@ i915_vma_resource_init_from_vma(struct i915_vma_resource *vma_res,i915_vma_resource_init (vma_res, vma->vm, vma->pages, &vma->page_sizes, obj->mm.rsgt,i915_gem_object_is_readonly (obj),i915_gem_object_is_lmem (obj), obj->mm.region, - vma->ops, vma->private, vma->node.start, - vma->node.size, vma->size); + vma->ops, vma->private,__i915_vma_offset (vma), +__i915_vma_size (vma), vma->size); }/**
@@ -447,7 +447,7 @@ int i915_vma_bind(struct i915_vma *vma,lockdep_assert_held (&vma->vm->mutex);GEM_BUG_ON (!drm_mm_node_allocated (&vma->node)); -GEM_BUG_ON (vma->size > vma->node.size); +GEM_BUG_ON (vma->size >i915_vma_size (vma)); if (GEM_DEBUG_WARN_ON(range_overflows(vma->node.start, vma->node.size,
@@ -569,8 +569,8 @@ void __iomem *i915_vma_pin_iomap(struct i915_vma *vma) vma->obj->base.size); }else if (i915_vma_is_map_and_fenceable (vma)) { ptr =io_mapping_map_wc (&i915_vm_to_ggtt (vma->vm)->iomap, - vma->node.start, - vma->node.size); +i915_vma_offset (vma), +i915_vma_size (vma)); }else { ptr = (void __iomem *)i915_gem_object_pin_map (vma->obj,I915_MAP_WC );
@@ -659,22 +659,22 @@ bool i915_vma_misplaced(const struct i915_vma *vma,if (test_bit (I915_VMA_ERROR_BIT ,__i915_vma_flags (vma)))return true; -if (vma->node.size < size) +if (i915_vma_size (vma) < size)return true;GEM_BUG_ON (alignment && !is_power_of_2 (alignment)); -if (alignment && !IS_ALIGNED (vma->node.start, alignment)) +if (alignment && !IS_ALIGNED (i915_vma_offset (vma), alignment))return true;if (flags &PIN_MAPPABLE && !i915_vma_is_map_and_fenceable (vma))return true;if (flags &PIN_OFFSET_BIAS && - vma->node.start < (flags &PIN_OFFSET_MASK )) +i915_vma_offset (vma) < (flags &PIN_OFFSET_MASK ))return true;if (flags &PIN_OFFSET_FIXED && - vma->node.start != (flags &PIN_OFFSET_MASK )) +i915_vma_offset (vma) != (flags &PIN_OFFSET_MASK ))return true;return false;
@@ -687,10 +687,11 @@ void __i915_vma_set_map_and_fenceable(struct i915_vma *vma)GEM_BUG_ON (!i915_vma_is_ggtt (vma));GEM_BUG_ON (!vma->fence_size); - fenceable = (vma->node.size >= vma->fence_size && -IS_ALIGNED (vma->node.start, vma->fence_alignment)); + fenceable = (i915_vma_size (vma) >= vma->fence_size && +IS_ALIGNED (i915_vma_offset (vma), vma->fence_alignment)); - mappable = vma->node.start + vma->fence_size <=i915_vm_to_ggtt (vma->vm)->mappable_end; + mappable =i915_ggtt_offset (vma) + vma->fence_size <= +i915_vm_to_ggtt (vma->vm)->mappable_end;if (mappable && fenceable)set_bit (I915_VMA_CAN_FENCE_BIT ,__i915_vma_flags (vma));
drivers/gpu/drm/i915/i915_vma.h +48 -3
61 lines not on this page · raw message
drivers/gpu/drm/i915/i915_vma_resource.h +6 -4
@@ -52,8 +52,10 @@ struct i915_page_sizes {* @mr: The memory region of the object pointed to by the vma. * @ops: Pointer to the backend i915_vma_ops. * @private: Bind backend private info. -* @start: Offset into the address space of bind range start. -* @node_size: Size of the allocated range manager node. +* @start: Offset into the address space of bind range start. Note that +* this is after any padding that might have been allocated. +* @node_size: Size of the allocated range manager node with padding +* subtracted. * @vma_size: Bind size. * @page_sizes_gtt: Resulting page sizes from the bind operation. * @bound_flags: Flags indicating binding status.
@@ -174,8 +176,8 @@ static inline void i915_vma_resource_put(struct i915_vma_resource *vma_res)* @mr: The memory region of the object the vma points to. * @ops: The backend ops. * @private: Bind backend private info. -* @start: Offset into the address space of bind range start. -* @node_size: Size of the allocated range manager node. +* @start: Offset into the address space of bind range start after padding. +* @node_size: Size of the allocated range manager node minus padding. * @size: Bind size. * * Initializes a vma resource allocated using i915_vma_resource_alloc().
drivers/gpu/drm/i915/selftests/i915_request.c +10 -10
@@ -1017,8 +1017,8 @@ empty_request(struct intel_engine_cs *engine,return request; err = engine->emit_bb_start (request, - batch->node.start, - batch->node.size, +i915_vma_offset (batch), +i915_vma_size (batch),I915_DISPATCH_SECURE );if (err) goto out_request;
@@ -1138,14 +1138,14 @@ static struct i915_vma *recursive_batch(struct drm_i915_private *i915)if (ver >=8 ) { *cmd++ =MI_BATCH_BUFFER_START |1 <<8 |1 ; - *cmd++ =lower_32_bits (vma->node.start); - *cmd++ =upper_32_bits (vma->node.start); + *cmd++ =lower_32_bits (i915_vma_offset (vma)); + *cmd++ =upper_32_bits (i915_vma_offset (vma)); }else if (ver >=6 ) { *cmd++ =MI_BATCH_BUFFER_START |1 <<8 ; - *cmd++ =lower_32_bits (vma->node.start); + *cmd++ =lower_32_bits (i915_vma_offset (vma)); }else { *cmd++ =MI_BATCH_BUFFER_START |MI_BATCH_GTT ; - *cmd++ =lower_32_bits (vma->node.start); + *cmd++ =lower_32_bits (i915_vma_offset (vma)); } *cmd++ =MI_BATCH_BUFFER_END ;/* terminate early in case of error */
@@ -1227,8 +1227,8 @@ static int live_all_engines(void *arg)GEM_BUG_ON (err); err = engine->emit_bb_start (request[idx], - batch->node.start, - batch->node.size, +i915_vma_offset (batch), +i915_vma_size (batch),0 );GEM_BUG_ON (err); request[idx]->batch = batch;
@@ -1354,8 +1354,8 @@ static int live_sequential_engines(void *arg)GEM_BUG_ON (err); err = engine->emit_bb_start (request[idx], - batch->node.start, - batch->node.size, +i915_vma_offset (batch), +i915_vma_size (batch),0 );GEM_BUG_ON (err); request[idx]->batch = batch;
drivers/gpu/drm/i915/selftests/igt_spinner.c +4 -4
@@ -116,7 +116,7 @@ static unsigned int seqno_offset(u64 fence)static u64 hws_address (const struct i915_vma *hws,const struct i915_request *rq) { -return hws->node.start +seqno_offset (rq->fence.context); +return i915_vma_offset (hws) +seqno_offset (rq->fence.context); } struct i915_request *
@@ -187,8 +187,8 @@ igt_spinner_create_request(struct igt_spinner *spin, *batch++ =MI_BATCH_BUFFER_START ; else *batch++ = MI_BATCH_BUFFER_START | MI_BATCH_GTT; - *batch++ =lower_32_bits (vma->node.start); - *batch++ =upper_32_bits (vma->node.start); + *batch++ =lower_32_bits (i915_vma_offset (vma)); + *batch++ =upper_32_bits (i915_vma_offset (vma)); *batch++ =MI_BATCH_BUFFER_END ;/* not reached */
@@ -203,7 +203,7 @@ igt_spinner_create_request(struct igt_spinner *spin, flags =0 ;if (GRAPHICS_VER (rq->engine->i915) <=5 ) flags |=I915_DISPATCH_SECURE ; - err = engine->emit_bb_start (rq, vma->node.start,PAGE_SIZE , flags); + err = engine->emit_bb_start (rq,i915_vma_offset (vma),PAGE_SIZE , flags); cancel_rq:if (err) {
Signature · 1 line
2.38.1
PATCH v4 3/5 drm/i915: Introduce guard pages to i915_vma
In reply to Andi ShytiFrom: Chris Wilson <[email protected]>
Introduce the concept of padding the i915_vma with guard pages before and after. The major consequence is that all ordinary uses of i915_vma must use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as the drm_mm_node will include the guard pages that surround our object.
The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a PIN_OFFSET_FIXED must then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.
In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
--- drivers/gpu/drm/i915/gt/intel_ggtt.c | 14 ++++++--- drivers/gpu/drm/i915/i915_gem_gtt.h | 3 +- drivers/gpu/drm/i915/i915_vma.c | 40 +++++++++++++++++++----- drivers/gpu/drm/i915/i915_vma.h | 5 +-- drivers/gpu/drm/i915/i915_vma_resource.c | 4 +-- drivers/gpu/drm/i915/i915_vma_resource.h | 7 ++++- drivers/gpu/drm/i915/i915_vma_types.h | 1 + 7 files changed, 57 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/gt/intel_ggtt.c +10 -4
@@ -296,8 +296,11 @@ static void gen8_ggtt_insert_entries(struct i915_address_space *vm,*/ gte = (gen8_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +gen8_set_pte (gte++, vm->scratch[0 ]->encode); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)gen8_set_pte (gte++, pte_encode | addr);
@@ -347,9 +350,12 @@ static void gen6_ggtt_insert_entries(struct i915_address_space *vm,dma_addr_t addr; gte = (gen6_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +iowrite32 (vm->scratch[0 ]->encode, gte++); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)iowrite32 (vm->pte_encode (addr, level, flags), gte++);GEM_BUG_ON (gte > end);
drivers/gpu/drm/i915/i915_gem_gtt.h +2 -1
@@ -44,7 +44,8 @@ int i915_gem_gtt_insert(struct i915_address_space *vm,#define PIN_HIGH BIT_ULL(5)#define PIN_OFFSET_BIAS BIT_ULL(6)#define PIN_OFFSET_FIXED BIT_ULL(7) -#define PIN_VALIDATE BIT_ULL(8)/* validate placement only, no need to call unpin() */ +#define PIN_OFFSET_GUARD BIT_ULL(8) +#define PIN_VALIDATE BIT_ULL(9)/* validate placement only, no need to call unpin() */ #define PIN_GLOBAL BIT_ULL(10)/* I915_VMA_GLOBAL_BIND */ #define PIN_USER BIT_ULL(11)/* I915_VMA_LOCAL_BIND */
drivers/gpu/drm/i915/i915_vma.c +33 -7
@@ -419,7 +419,7 @@ i915_vma_resource_init_from_vma(struct i915_vma_resource *vma_res, obj->mm.rsgt,i915_gem_object_is_readonly (obj),i915_gem_object_is_lmem (obj), obj->mm.region, vma->ops, vma->private,__i915_vma_offset (vma), - __i915_vma_size(vma), vma->size); + __i915_vma_size(vma), vma->size, vma->guard); }/**
@@ -677,6 +677,10 @@ bool i915_vma_misplaced(const struct i915_vma *vma, i915_vma_offset(vma) != (flags & PIN_OFFSET_MASK))return true; +if (flags &PIN_OFFSET_GUARD && + vma->guard < (flags &PIN_OFFSET_MASK )) +return true; +return false; }
@@ -749,15 +753,16 @@ static int i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, u64 size, u64 alignment, u64 flags) { - unsigned long color; + unsigned long color, guard;u64 start, end;int ret;GEM_BUG_ON (i915_vma_is_bound (vma,I915_VMA_GLOBAL_BIND |I915_VMA_LOCAL_BIND ));GEM_BUG_ON (drm_mm_node_allocated (&vma->node)); +GEM_BUG_ON (hweight64 (flags & (PIN_OFFSET_GUARD |PIN_OFFSET_FIXED |PIN_OFFSET_BIAS )) >1 ); size =max (size, vma->size); - alignment =max (alignment, vma->display_alignment); + alignment =max_t (typeof (alignment), alignment, vma->display_alignment);if (flags &PIN_MAPPABLE ) { size =max_t (typeof (size), size, vma->fence_size); alignment = max_t(typeof(alignment),
@@ -768,8 +773,17 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!IS_ALIGNED (alignment,I915_GTT_MIN_ALIGNMENT ));GEM_BUG_ON (!is_power_of_2 (alignment)); + guard = vma->guard;/* retain guard across rebinds */ +if (flags &PIN_OFFSET_GUARD ) { +GEM_BUG_ON (overflows_type (flags &PIN_OFFSET_MASK , u32)); + guard =max_t (u32, guard, flags &PIN_OFFSET_MASK ); + } +roundup (guard,BIT (vma->vm->scratch_order +PAGE_SHIFT )); + start = flags &PIN_OFFSET_BIAS ? flags &PIN_OFFSET_MASK :0 ;GEM_BUG_ON (!IS_ALIGNED (start,I915_GTT_PAGE_SIZE )); +/* We need to be sure we do not ecceed the va area */ +GEM_BUG_ON (2 * guard > end); end = vma->vm->total;if (flags &PIN_MAPPABLE )
@@ -780,11 +794,12 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, alignment =max (alignment,i915_vm_obj_min_alignment (vma->vm, vma->obj)); -/* If binding the object/GGTT view requires more space than the entire +/* +* If binding the object/GGTT view requires more space than the entire * aperture has, reject it early before evicting everything in a vain * attempt to find space. */ -if (size > end) { +if (size > end -2 * guard) {drm_dbg (&to_i915 (vma->obj->base.dev)->drm,"Attempting to bind an object larger than the aperture: request=%llu > %s aperture=%llu\n" , size, flags &PIN_MAPPABLE ?"mappable" :"total" , end);
@@ -801,13 +816,23 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,if (!IS_ALIGNED (offset, alignment) ||range_overflows (offset, size, end))return -EINVAL ; +/* +* The caller knows not of the guard added by others and +* requests for the offset of the start of its buffer +* to be fixed, which may not be the same as the position +* of the vma->node due to the guard pages. +*/ +if (offset < guard || offset + size > end - guard) +return -ENOSPC ; ret =i915_gem_gtt_reserve (vma->vm, ww, &vma->node, - size, offset, color, - flags); + size +2 * guard, + offset - guard, + color, flags);if (ret)return ret; }else { + size +=2 * guard;/* * We only support huge gtt pages through the 48b PPGTT, * however we also don't want to force any alignment for
@@ -855,6 +880,7 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!i915_gem_valid_gtt_space (vma, color));list_move_tail (&vma->vm_link, &vma->vm->bound_list); + vma->guard = guard;return 0 ; }
drivers/gpu/drm/i915/i915_vma.h +3 -2
@@ -128,7 +128,7 @@ static inline bool i915_vma_is_closed(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_size (const struct i915_vma *vma) { -return vma->node.size; +return vma->node.size -2 * vma->guard; }/**
@@ -150,7 +150,8 @@ static inline u64 i915_vma_size(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_offset (const struct i915_vma *vma) { -return vma->node.start; +/* The actual start of the vma->pages is after the guard pages. */ +return vma->node.start + vma->guard; }/**
drivers/gpu/drm/i915/i915_vma_resource.c +2 -2
@@ -34,8 +34,8 @@ static struct kmem_cache *slab_vma_resources;* and removal of fences increases as O(ln(pending_unbinds)) instead of * O(1) for a single fence without interval tree. */ -#define VMA_RES_START (_node) ((_node)->start) -#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size - 1) +#define VMA_RES_START (_node) ((_node)->start - (_node)->guard) +#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1) INTERVAL_TREE_DEFINE(struct i915_vma_resource, rb, u64, __subtree_last, VMA_RES_START, VMA_RES_LAST, static, vma_res_itree);
drivers/gpu/drm/i915/i915_vma_resource.h +6 -1
@@ -57,6 +57,7 @@ struct i915_page_sizes {* @node_size: Size of the allocated range manager node with padding * subtracted. * @vma_size: Bind size. +* @guard: The size of guard area preceding and trailing the bind. * @page_sizes_gtt: Resulting page sizes from the bind operation. * @bound_flags: Flags indicating binding status. * @allocated: Backend private data. TODO: Should move into @private.
@@ -115,6 +116,7 @@ struct i915_vma_resource {u64 start;u64 node_size;u64 vma_size; +u32 guard;u32 page_sizes_gtt;u32 bound_flags;
@@ -179,6 +181,7 @@ static inline void i915_vma_resource_put(struct i915_vma_resource *vma_res)* @start: Offset into the address space of bind range start after padding. * @node_size: Size of the allocated range manager node minus padding. * @size: Bind size. +* @guard: The size of the guard area preceding and trailing the bind. * * Initializes a vma resource allocated using i915_vma_resource_alloc(). * The reason for having separate allocate and initialize function is that
@@ -197,7 +200,8 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res,void *private, u64 start, u64 node_size, - u64 size) + u64 size, + u32 guard) {__i915_vma_resource_init (vma_res ); vma_res->vm = vm;
@@ -215,6 +219,7 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res, vma_res->start = start; vma_res->node_size = node_size; vma_res->vma_size = size; + vma_res->guard = guard; }static inline void i915_vma_resource_fini (struct i915_vma_resource *vma_res)
drivers/gpu/drm/i915/i915_vma_types.h +1 -0
@@ -202,6 +202,7 @@ struct i915_vma {/* mmap-offset associated with fencing for this vma */ struct i915_mmap_offset *mmo; +u32 guard;/* padding allocated around vma->pages within the node */ u32 fence_size;u32 fence_alignment;u32 display_alignment;
Signature · 1 line
2.38.1
Re: [Intel-gfx] [PATCH v4 3/5] drm/i915: Introduce guard pages to i915_vma
Quoted 132 lines · Andi Shyti
From: Chris Wilson <[email protected]>
Introduce the concept of padding the
i915_vmawith guard pages before and after. The major consequence is that all ordinary uses ofi915_vmamust use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as thedrm_mm_nodewill include the guard pages that surround our object.The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a
PIN_OFFSET_FIXEDmust then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
Signed-off-by Chris Wilson <[email protected]>Signed-off-by Tejas Upadhyay <[email protected]>Signed-off-by Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>--- drivers/gpu/drm/i915/gt/intel_ggtt.c | 14 ++++++--- drivers/gpu/drm/i915/i915_gem_gtt.h | 3 +- drivers/gpu/drm/i915/i915_vma.c | 40 +++++++++++++++++++----- drivers/gpu/drm/i915/i915_vma.h | 5 +-- drivers/gpu/drm/i915/i915_vma_resource.c | 4 +-- drivers/gpu/drm/i915/i915_vma_resource.h | 7 ++++- drivers/gpu/drm/i915/i915_vma_types.h | 1 + 7 files changed, 57 insertions(+), 17 deletions(-)drivers/gpu/drm/i915/gt/intel_ggtt.c +10
-4@@ -296,8 +296,11 @@ static void gen8_ggtt_insert_entries(struct i915_address_space *vm,*/ gte = (gen8_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +gen8_set_pte (gte++, vm->scratch[0 ]->encode); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)gen8_set_pte (gte++, pte_encode | addr);@@ -347,9 +350,12 @@ static void gen6_ggtt_insert_entries(struct i915_address_space *vm,dma_addr_t addr; gte = (gen6_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +iowrite32 (vm->scratch[0 ]->encode, gte++); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)iowrite32 (vm->pte_encode (addr, level, flags), gte++);GEM_BUG_ON (gte > end);drivers/gpu/drm/i915/i915_gem_gtt.h +2
-1@@ -44,7 +44,8 @@ int i915_gem_gtt_insert(struct i915_address_space *vm,#define PIN_HIGH BIT_ULL(5)#define PIN_OFFSET_BIAS BIT_ULL(6)#define PIN_OFFSET_FIXED BIT_ULL(7) -#define PIN_VALIDATE BIT_ULL(8)/* validate placement only, no need to call unpin() */ +#define PIN_OFFSET_GUARD BIT_ULL(8) +#define PIN_VALIDATE BIT_ULL(9)/* validate placement only, no need to call unpin() */ #define PIN_GLOBAL BIT_ULL(10)/* I915_VMA_GLOBAL_BIND */ #define PIN_USER BIT_ULL(11)/* I915_VMA_LOCAL_BIND */ drivers/gpu/drm/i915/i915_vma.c +8
-3@@ -419,7 +419,7 @@ i915_vma_resource_init_from_vma(struct i915_vma_resource *vma_res, obj->mm.rsgt,i915_gem_object_is_readonly (obj),i915_gem_object_is_lmem (obj), obj->mm.region, vma->ops, vma->private,__i915_vma_offset (vma), - __i915_vma_size(vma), vma->size); + __i915_vma_size(vma), vma->size, vma->guard); }/** @@ -677,6 +677,10 @@ bool i915_vma_misplaced(const struct i915_vma *vma, i915_vma_offset(vma) != (flags & PIN_OFFSET_MASK))return true; +if (flags &PIN_OFFSET_GUARD && + vma->guard < (flags &PIN_OFFSET_MASK )) +return true; +return false; }@@ -749,15 +753,16 @@ static int i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, u64 size, u64 alignment, u64 flags) { - unsigned long color; + unsigned long color, guard;u64 start, end;int ret;GEM_BUG_ON (i915_vma_is_bound (vma,I915_VMA_GLOBAL_BIND |I915_VMA_LOCAL_BIND ));GEM_BUG_ON (drm_mm_node_allocated (&vma->node)); +GEM_BUG_ON (hweight64 (flags & (PIN_OFFSET_GUARD |PIN_OFFSET_FIXED |PIN_OFFSET_BIAS )) >1 ); size =max (size, vma->size); - alignment =max (alignment, vma->display_alignment); + alignment =max_t (typeof (alignment), alignment, vma->display_alignment);if (flags &PIN_MAPPABLE ) { size =max_t (typeof (size), size, vma->fence_size); alignment = max_t(typeof(alignment),
drivers/gpu/drm/i915/i915_vma.c i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, · line 781
Quoted 9 lines
drivers/gpu/drm/i915/i915_vma.c +6
-0@@ -768,8 +773,17 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!IS_ALIGNED (alignment,I915_GTT_MIN_ALIGNMENT ));GEM_BUG_ON (!is_power_of_2 (alignment)); + guard = vma->guard;/* retain guard across rebinds */ +if (flags &PIN_OFFSET_GUARD ) { +GEM_BUG_ON (overflows_type (flags &PIN_OFFSET_MASK , u32)); + guard =max_t (u32, guard, flags &PIN_OFFSET_MASK ); + } +roundup (guard,BIT (vma->vm->scratch_order +PAGE_SHIFT ));
roundup = ?
Lets have a comment here as well.
/*
* Be efficient with PTE use by using the native size for the guard. */
Would that be accurate?
drivers/gpu/drm/i915/i915_vma.c i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, · line 786
Quoted 5 lines
drivers/gpu/drm/i915/i915_vma.c +3
-0+ start = flags &PIN_OFFSET_BIAS ? flags &PIN_OFFSET_MASK :0 ;GEM_BUG_ON (!IS_ALIGNED (start,I915_GTT_PAGE_SIZE )); +/* We need to be sure we do not ecceed the va area */ +GEM_BUG_ON (2 * guard > end);
"exceed" but haven't we said this is not needed?
Regards,
Tvrtko
Quoted 148 lines
drivers/gpu/drm/i915/i915_vma.c +16
-4end = vma->vm->total;if (flags &PIN_MAPPABLE )@@ -780,11 +794,12 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, alignment =max (alignment,i915_vm_obj_min_alignment (vma->vm, vma->obj)); -/* If binding the object/GGTT view requires more space than the entire +/* +* If binding the object/GGTT view requires more space than the entire * aperture has, reject it early before evicting everything in a vain * attempt to find space. */ -if (size > end) { +if (size > end -2 * guard) {drm_dbg (&to_i915 (vma->obj->base.dev)->drm,"Attempting to bind an object larger than the aperture: request=%llu > %s aperture=%llu\n" , size, flags &PIN_MAPPABLE ?"mappable" :"total" , end);@@ -801,13 +816,23 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,if (!IS_ALIGNED (offset, alignment) ||range_overflows (offset, size, end))return -EINVAL ; +/* +* The caller knows not of the guard added by others and +* requests for the offset of the start of its buffer +* to be fixed, which may not be the same as the position +* of the vma->node due to the guard pages. +*/ +if (offset < guard || offset + size > end - guard) +return -ENOSPC ; ret =i915_gem_gtt_reserve (vma->vm, ww, &vma->node, - size, offset, color, - flags); + size +2 * guard, + offset - guard, + color, flags);if (ret)return ret; }else { + size +=2 * guard;/* * We only support huge gtt pages through the 48b PPGTT, * however we also don't want to force any alignment for @@ -855,6 +880,7 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!i915_gem_valid_gtt_space (vma, color));list_move_tail (&vma->vm_link, &vma->vm->bound_list); + vma->guard = guard;return 0 ; }drivers/gpu/drm/i915/i915_vma.h +3
-2@@ -128,7 +128,7 @@ static inline bool i915_vma_is_closed(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_size (const struct i915_vma *vma) { -return vma->node.size; +return vma->node.size -2 * vma->guard; }/** @@ -150,7 +150,8 @@ static inline u64 i915_vma_size(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_offset (const struct i915_vma *vma) { -return vma->node.start; +/* The actual start of the vma->pages is after the guard pages. */ +return vma->node.start + vma->guard; }/** drivers/gpu/drm/i915/i915_vma_resource.c +2
-2@@ -34,8 +34,8 @@ static struct kmem_cache *slab_vma_resources;* and removal of fences increases as O(ln(pending_unbinds)) instead of * O(1) for a single fence without interval tree. */ -#define VMA_RES_START (_node) ((_node)->start) -#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size - 1) +#define VMA_RES_START (_node) ((_node)->start - (_node)->guard) +#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1) INTERVAL_TREE_DEFINE(struct i915_vma_resource, rb, u64, __subtree_last, VMA_RES_START, VMA_RES_LAST, static, vma_res_itree);drivers/gpu/drm/i915/i915_vma_resource.h +6
-1@@ -57,6 +57,7 @@ struct i915_page_sizes {* @node_size: Size of the allocated range manager node with padding * subtracted. * @vma_size: Bind size. +* @guard: The size of guard area preceding and trailing the bind. * @page_sizes_gtt: Resulting page sizes from the bind operation. * @bound_flags: Flags indicating binding status. * @allocated: Backend private data. TODO: Should move into @private. @@ -115,6 +116,7 @@ struct i915_vma_resource {u64 start;u64 node_size;u64 vma_size; +u32 guard;u32 page_sizes_gtt;u32 bound_flags;@@ -179,6 +181,7 @@ static inline void i915_vma_resource_put(struct i915_vma_resource *vma_res)* @start: Offset into the address space of bind range start after padding. * @node_size: Size of the allocated range manager node minus padding. * @size: Bind size. +* @guard: The size of the guard area preceding and trailing the bind. * * Initializes a vma resource allocated using i915_vma_resource_alloc(). * The reason for having separate allocate and initialize function is that @@ -197,7 +200,8 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res,void *private, u64 start, u64 node_size, - u64 size) + u64 size, + u32 guard) {__i915_vma_resource_init (vma_res ); vma_res->vm = vm;@@ -215,6 +219,7 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res, vma_res->start = start; vma_res->node_size = node_size; vma_res->vma_size = size; + vma_res->guard = guard; }static inline void i915_vma_resource_fini (struct i915_vma_resource *vma_res)drivers/gpu/drm/i915/i915_vma_types.h +1
-0@@ -202,6 +202,7 @@ struct i915_vma {/* mmap-offset associated with fencing for this vma */ struct i915_mmap_offset *mmo; +u32 guard;/* padding allocated around vma->pages within the node */ u32 fence_size;u32 fence_alignment;u32 display_alignment;
Re: [Intel-gfx] [PATCH v4 3/5] drm/i915: Introduce guard pages to i915_vma
Hi Tvrtko,
[...]
Quoted 11 lines
drivers/gpu/drm/i915/i915_vma.c i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, · line 780
Quoted 9 lines
drivers/gpu/drm/i915/i915_vma.c +6
-0@@ -768,8 +773,17 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!IS_ALIGNED (alignment,I915_GTT_MIN_ALIGNMENT ));GEM_BUG_ON (!is_power_of_2 (alignment)); + guard = vma->guard;/* retain guard across rebinds */ +if (flags &PIN_OFFSET_GUARD ) { +GEM_BUG_ON (overflows_type (flags &PIN_OFFSET_MASK , u32)); + guard =max_t (u32, guard, flags &PIN_OFFSET_MASK ); + } +roundup (guard,BIT (vma->vm->scratch_order +PAGE_SHIFT ));roundup = ?
ehehe... yes, please ignore, that's some copy/paste error during the rebase...
Quoted 7 lines
Lets have a comment here as well.
/*
* Be efficient with PTE use by using the native size for the guard. */Would that be accurate?
and I also forgot the update of my previous comment... yours is quite accurate.
Quoted 7 lines
drivers/gpu/drm/i915/i915_vma.c i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, · line 786
Quoted 5 lines
drivers/gpu/drm/i915/i915_vma.c +3
-0+ start = flags &PIN_OFFSET_BIAS ? flags &PIN_OFFSET_MASK :0 ;GEM_BUG_ON (!IS_ALIGNED (start,I915_GTT_PAGE_SIZE )); +/* We need to be sure we do not ecceed the va area */ +GEM_BUG_ON (2 * guard > end);"exceed" but haven't we said this is not needed?
I wrote it in the cover letter. I had an offline chat with Chris and he was keen to have this check not only for overflow protection but also for a documentation purpose so that the reader knows better about the size and usage of the guard.
Does it make sense?
Thanks a lot!
Andi
Re: [Intel-gfx] [PATCH v4 3/5] drm/i915: Introduce guard pages to i915_vma
Quoted 38 lines · Andi Shyti
Hi Tvrtko,
[...]
Quoted 11 lines
drivers/gpu/drm/i915/i915_vma.c i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, · line 780
Quoted 9 lines
drivers/gpu/drm/i915/i915_vma.c +6
-0@@ -768,8 +773,17 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!IS_ALIGNED (alignment,I915_GTT_MIN_ALIGNMENT ));GEM_BUG_ON (!is_power_of_2 (alignment)); + guard = vma->guard;/* retain guard across rebinds */ +if (flags &PIN_OFFSET_GUARD ) { +GEM_BUG_ON (overflows_type (flags &PIN_OFFSET_MASK , u32)); + guard =max_t (u32, guard, flags &PIN_OFFSET_MASK ); + } +roundup (guard,BIT (vma->vm->scratch_order +PAGE_SHIFT ));roundup = ?
ehehe... yes, please ignore, that's some copy/paste error during the rebase...
Quoted 7 lines
Lets have a comment here as well.
/*
* Be efficient with PTE use by using the native size for the guard. */Would that be accurate?
and I also forgot the update of my previous comment... yours is quite accurate.
Quoted 7 lines
drivers/gpu/drm/i915/i915_vma.c i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, · line 786
Quoted 5 lines
drivers/gpu/drm/i915/i915_vma.c +3
-0+ start = flags &PIN_OFFSET_BIAS ? flags &PIN_OFFSET_MASK :0 ;GEM_BUG_ON (!IS_ALIGNED (start,I915_GTT_PAGE_SIZE )); +/* We need to be sure we do not ecceed the va area */ +GEM_BUG_ON (2 * guard > end);"exceed" but haven't we said this is not needed?
Quoted 6 lines
I wrote it in the cover letter. I had an offline chat with Chris and he was keen to have this check not only for overflow protection but also for a documentation purpose so that the reader knows better about the size and usage of the guard.
Does it make sense?
Not to me really, I have no idea how could anyone ever end up with guard size of half+ of GGTT. And the total 2 * guard + size is checked and rejected already. So I have no idea what it is supposed to be documenting. GEM_BUG_ON suggests really bad things would happen if that was passed in, like something would be incorrectly calculated. If that is not the case and things would just safely fail then it is just confusing to have it.
Regards,
Tvrtko
PATCH v5 3/5 drm/i915: Introduce guard pages to i915_vma
In reply to Andi ShytiFrom: Chris Wilson <[email protected]>
Introduce the concept of padding the i915_vma with guard pages before and after. The major consequence is that all ordinary uses of i915_vma must use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as the drm_mm_node will include the guard pages that surround our object.
The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a PIN_OFFSET_FIXED must then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.
In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
---
Hi,
this the v5 changelog, the overall changelog is in the v4 cover letter:
v4 -> v5:
- remove again the GEM_BUG_ON()
- fix an oversight where the rounding was called without assigning the value to the guard.
Thanks Tvrtko for the reviews.
Thanks,
Andi
drivers/gpu/drm/i915/gt/intel_ggtt.c | 14 +++++--- drivers/gpu/drm/i915/i915_gem_gtt.h | 3 +- drivers/gpu/drm/i915/i915_vma.c | 41 ++++++++++++++++++++---- drivers/gpu/drm/i915/i915_vma.h | 5 +-- drivers/gpu/drm/i915/i915_vma_resource.c | 4 +-- drivers/gpu/drm/i915/i915_vma_resource.h | 7 +++- drivers/gpu/drm/i915/i915_vma_types.h | 1 + 7 files changed, 58 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/gt/intel_ggtt.c +10 -4
@@ -296,8 +296,11 @@ static void gen8_ggtt_insert_entries(struct i915_address_space *vm,*/ gte = (gen8_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +gen8_set_pte (gte++, vm->scratch[0 ]->encode); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)gen8_set_pte (gte++, pte_encode | addr);
@@ -347,9 +350,12 @@ static void gen6_ggtt_insert_entries(struct i915_address_space *vm,dma_addr_t addr; gte = (gen6_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +iowrite32 (vm->scratch[0 ]->encode, gte++); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)iowrite32 (vm->pte_encode (addr, level, flags), gte++);GEM_BUG_ON (gte > end);
drivers/gpu/drm/i915/i915_gem_gtt.h +2 -1
@@ -44,7 +44,8 @@ int i915_gem_gtt_insert(struct i915_address_space *vm,#define PIN_HIGH BIT_ULL(5)#define PIN_OFFSET_BIAS BIT_ULL(6)#define PIN_OFFSET_FIXED BIT_ULL(7) -#define PIN_VALIDATE BIT_ULL(8)/* validate placement only, no need to call unpin() */ +#define PIN_OFFSET_GUARD BIT_ULL(8) +#define PIN_VALIDATE BIT_ULL(9)/* validate placement only, no need to call unpin() */ #define PIN_GLOBAL BIT_ULL(10)/* I915_VMA_GLOBAL_BIND */ #define PIN_USER BIT_ULL(11)/* I915_VMA_LOCAL_BIND */
drivers/gpu/drm/i915/i915_vma.c +34 -7
98 lines not on this page · raw message
drivers/gpu/drm/i915/i915_vma.h +3 -2
@@ -128,7 +128,7 @@ static inline bool i915_vma_is_closed(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_size (const struct i915_vma *vma) { -return vma->node.size; +return vma->node.size -2 * vma->guard; }/**
@@ -150,7 +150,8 @@ static inline u64 i915_vma_size(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_offset (const struct i915_vma *vma) { -return vma->node.start; +/* The actual start of the vma->pages is after the guard pages. */ +return vma->node.start + vma->guard; }/**
drivers/gpu/drm/i915/i915_vma_resource.c +2 -2
@@ -34,8 +34,8 @@ static struct kmem_cache *slab_vma_resources;* and removal of fences increases as O(ln(pending_unbinds)) instead of * O(1) for a single fence without interval tree. */ -#define VMA_RES_START (_node) ((_node)->start) -#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size - 1) +#define VMA_RES_START (_node) ((_node)->start - (_node)->guard) +#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1) INTERVAL_TREE_DEFINE(struct i915_vma_resource, rb, u64, __subtree_last, VMA_RES_START, VMA_RES_LAST, static, vma_res_itree);
drivers/gpu/drm/i915/i915_vma_resource.h +6 -1
@@ -57,6 +57,7 @@ struct i915_page_sizes {* @node_size: Size of the allocated range manager node with padding * subtracted. * @vma_size: Bind size. +* @guard: The size of guard area preceding and trailing the bind. * @page_sizes_gtt: Resulting page sizes from the bind operation. * @bound_flags: Flags indicating binding status. * @allocated: Backend private data. TODO: Should move into @private.
@@ -115,6 +116,7 @@ struct i915_vma_resource {u64 start;u64 node_size;u64 vma_size; +u32 guard;u32 page_sizes_gtt;u32 bound_flags;
@@ -179,6 +181,7 @@ static inline void i915_vma_resource_put(struct i915_vma_resource *vma_res)* @start: Offset into the address space of bind range start after padding. * @node_size: Size of the allocated range manager node minus padding. * @size: Bind size. +* @guard: The size of the guard area preceding and trailing the bind. * * Initializes a vma resource allocated using i915_vma_resource_alloc(). * The reason for having separate allocate and initialize function is that
@@ -197,7 +200,8 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res,void *private, u64 start, u64 node_size, - u64 size) + u64 size, + u32 guard) {__i915_vma_resource_init (vma_res ); vma_res->vm = vm;
@@ -215,6 +219,7 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res, vma_res->start = start; vma_res->node_size = node_size; vma_res->vma_size = size; + vma_res->guard = guard; }static inline void i915_vma_resource_fini (struct i915_vma_resource *vma_res)
drivers/gpu/drm/i915/i915_vma_types.h +1 -0
@@ -202,6 +202,7 @@ struct i915_vma {/* mmap-offset associated with fencing for this vma */ struct i915_mmap_offset *mmo; +u32 guard;/* padding allocated around vma->pages within the node */ u32 fence_size;u32 fence_alignment;u32 display_alignment;
Signature · 1 line
2.38.1
Re: [Intel-gfx] [PATCH v5 3/5] drm/i915: Introduce guard pages to i915_vma
Quoted 34 lines · Andi Shyti
From: Chris Wilson <[email protected]>
Introduce the concept of padding the
i915_vmawith guard pages before and after. The major consequence is that all ordinary uses ofi915_vmamust use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as thedrm_mm_nodewill include the guard pages that surround our object.The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a
PIN_OFFSET_FIXEDmust then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
Signed-off-by Chris Wilson <[email protected]>Signed-off-by Tejas Upadhyay <[email protected]>Signed-off-by Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,
Quoted 8 lines
this the v5 changelog, the overall changelog is in the v4 cover letter:
v4 -> v5:
- remove again theGEM_BUG_ON()
- fix an oversight where the rounding was called without assigning the value to the guard.Thanks Tvrtko for the reviews.
I think that was the last open I had so LGTM now. Thanks for the respins!
Regards,
Tvrtko
Quoted 264 lines
Thanks,
Andidrivers/gpu/drm/i915/gt/intel_ggtt.c | 14 +++++--- drivers/gpu/drm/i915/i915_gem_gtt.h | 3 +- drivers/gpu/drm/i915/i915_vma.c | 41 ++++++++++++++++++++---- drivers/gpu/drm/i915/i915_vma.h | 5 +-- drivers/gpu/drm/i915/i915_vma_resource.c | 4 +-- drivers/gpu/drm/i915/i915_vma_resource.h | 7 +++- drivers/gpu/drm/i915/i915_vma_types.h | 1 + 7 files changed, 58 insertions(+), 17 deletions(-)drivers/gpu/drm/i915/gt/intel_ggtt.c +10
-4@@ -296,8 +296,11 @@ static void gen8_ggtt_insert_entries(struct i915_address_space *vm,*/ gte = (gen8_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +gen8_set_pte (gte++, vm->scratch[0 ]->encode); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)gen8_set_pte (gte++, pte_encode | addr);@@ -347,9 +350,12 @@ static void gen6_ggtt_insert_entries(struct i915_address_space *vm,dma_addr_t addr; gte = (gen6_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +iowrite32 (vm->scratch[0 ]->encode, gte++); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)iowrite32 (vm->pte_encode (addr, level, flags), gte++);GEM_BUG_ON (gte > end);drivers/gpu/drm/i915/i915_gem_gtt.h +2
-1@@ -44,7 +44,8 @@ int i915_gem_gtt_insert(struct i915_address_space *vm,#define PIN_HIGH BIT_ULL(5)#define PIN_OFFSET_BIAS BIT_ULL(6)#define PIN_OFFSET_FIXED BIT_ULL(7) -#define PIN_VALIDATE BIT_ULL(8)/* validate placement only, no need to call unpin() */ +#define PIN_OFFSET_GUARD BIT_ULL(8) +#define PIN_VALIDATE BIT_ULL(9)/* validate placement only, no need to call unpin() */ #define PIN_GLOBAL BIT_ULL(10)/* I915_VMA_GLOBAL_BIND */ #define PIN_USER BIT_ULL(11)/* I915_VMA_LOCAL_BIND */ drivers/gpu/drm/i915/i915_vma.c +34
-7@@ -419,7 +419,7 @@ i915_vma_resource_init_from_vma(struct i915_vma_resource *vma_res, obj->mm.rsgt,i915_gem_object_is_readonly (obj),i915_gem_object_is_lmem (obj), obj->mm.region, vma->ops, vma->private,__i915_vma_offset (vma), - __i915_vma_size(vma), vma->size); + __i915_vma_size(vma), vma->size, vma->guard); }/** @@ -677,6 +677,10 @@ bool i915_vma_misplaced(const struct i915_vma *vma, i915_vma_offset(vma) != (flags & PIN_OFFSET_MASK))return true; +if (flags &PIN_OFFSET_GUARD && + vma->guard < (flags &PIN_OFFSET_MASK )) +return true; +return false; }@@ -749,15 +753,16 @@ static int i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, u64 size, u64 alignment, u64 flags) { - unsigned long color; + unsigned long color, guard;u64 start, end;int ret;GEM_BUG_ON (i915_vma_is_bound (vma,I915_VMA_GLOBAL_BIND |I915_VMA_LOCAL_BIND ));GEM_BUG_ON (drm_mm_node_allocated (&vma->node)); +GEM_BUG_ON (hweight64 (flags & (PIN_OFFSET_GUARD |PIN_OFFSET_FIXED |PIN_OFFSET_BIAS )) >1 ); size =max (size, vma->size); - alignment =max (alignment, vma->display_alignment); + alignment =max_t (typeof (alignment), alignment, vma->display_alignment);if (flags &PIN_MAPPABLE ) { size =max_t (typeof (size), size, vma->fence_size); alignment = max_t(typeof(alignment),@@ -768,6 +773,16 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!IS_ALIGNED (alignment,I915_GTT_MIN_ALIGNMENT ));GEM_BUG_ON (!is_power_of_2 (alignment)); + guard = vma->guard;/* retain guard across rebinds */ +if (flags &PIN_OFFSET_GUARD ) { +GEM_BUG_ON (overflows_type (flags &PIN_OFFSET_MASK , u32)); + guard =max_t (u32, guard, flags &PIN_OFFSET_MASK ); + } +/* +* Be efficient with PTE use by using the native size for the guard. +*/ + guard =roundup (guard,BIT (vma->vm->scratch_order +PAGE_SHIFT )); + start = flags &PIN_OFFSET_BIAS ? flags &PIN_OFFSET_MASK :0 ;GEM_BUG_ON (!IS_ALIGNED (start,I915_GTT_PAGE_SIZE ));@@ -780,11 +795,12 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, alignment =max (alignment,i915_vm_obj_min_alignment (vma->vm, vma->obj)); -/* If binding the object/GGTT view requires more space than the entire +/* +* If binding the object/GGTT view requires more space than the entire * aperture has, reject it early before evicting everything in a vain * attempt to find space. */ -if (size > end) { +if (size > end -2 * guard) {drm_dbg (&to_i915 (vma->obj->base.dev)->drm,"Attempting to bind an object larger than the aperture: request=%llu > %s aperture=%llu\n" , size, flags &PIN_MAPPABLE ?"mappable" :"total" , end);@@ -801,13 +817,23 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,if (!IS_ALIGNED (offset, alignment) ||range_overflows (offset, size, end))return -EINVAL ; +/* +* The caller knows not of the guard added by others and +* requests for the offset of the start of its buffer +* to be fixed, which may not be the same as the position +* of the vma->node due to the guard pages. +*/ +if (offset < guard || offset + size > end - guard) +return -ENOSPC ; ret =i915_gem_gtt_reserve (vma->vm, ww, &vma->node, - size, offset, color, - flags); + size +2 * guard, + offset - guard, + color, flags);if (ret)return ret; }else { + size +=2 * guard;/* * We only support huge gtt pages through the 48b PPGTT, * however we also don't want to force any alignment for @@ -855,6 +881,7 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!i915_gem_valid_gtt_space (vma, color));list_move_tail (&vma->vm_link, &vma->vm->bound_list); + vma->guard = guard;return 0 ; }drivers/gpu/drm/i915/i915_vma.h +3
-2@@ -128,7 +128,7 @@ static inline bool i915_vma_is_closed(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_size (const struct i915_vma *vma) { -return vma->node.size; +return vma->node.size -2 * vma->guard; }/** @@ -150,7 +150,8 @@ static inline u64 i915_vma_size(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_offset (const struct i915_vma *vma) { -return vma->node.start; +/* The actual start of the vma->pages is after the guard pages. */ +return vma->node.start + vma->guard; }/** drivers/gpu/drm/i915/i915_vma_resource.c +2
-2@@ -34,8 +34,8 @@ static struct kmem_cache *slab_vma_resources;* and removal of fences increases as O(ln(pending_unbinds)) instead of * O(1) for a single fence without interval tree. */ -#define VMA_RES_START (_node) ((_node)->start) -#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size - 1) +#define VMA_RES_START (_node) ((_node)->start - (_node)->guard) +#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1) INTERVAL_TREE_DEFINE(struct i915_vma_resource, rb, u64, __subtree_last, VMA_RES_START, VMA_RES_LAST, static, vma_res_itree);drivers/gpu/drm/i915/i915_vma_resource.h +6
-1@@ -57,6 +57,7 @@ struct i915_page_sizes {* @node_size: Size of the allocated range manager node with padding * subtracted. * @vma_size: Bind size. +* @guard: The size of guard area preceding and trailing the bind. * @page_sizes_gtt: Resulting page sizes from the bind operation. * @bound_flags: Flags indicating binding status. * @allocated: Backend private data. TODO: Should move into @private. @@ -115,6 +116,7 @@ struct i915_vma_resource {u64 start;u64 node_size;u64 vma_size; +u32 guard;u32 page_sizes_gtt;u32 bound_flags;@@ -179,6 +181,7 @@ static inline void i915_vma_resource_put(struct i915_vma_resource *vma_res)* @start: Offset into the address space of bind range start after padding. * @node_size: Size of the allocated range manager node minus padding. * @size: Bind size. +* @guard: The size of the guard area preceding and trailing the bind. * * Initializes a vma resource allocated using i915_vma_resource_alloc(). * The reason for having separate allocate and initialize function is that @@ -197,7 +200,8 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res,void *private, u64 start, u64 node_size, - u64 size) + u64 size, + u32 guard) {__i915_vma_resource_init (vma_res ); vma_res->vm = vm;@@ -215,6 +219,7 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res, vma_res->start = start; vma_res->node_size = node_size; vma_res->vma_size = size; + vma_res->guard = guard; }static inline void i915_vma_resource_fini (struct i915_vma_resource *vma_res)drivers/gpu/drm/i915/i915_vma_types.h +1
-0@@ -202,6 +202,7 @@ struct i915_vma {/* mmap-offset associated with fencing for this vma */ struct i915_mmap_offset *mmo; +u32 guard;/* padding allocated around vma->pages within the node */ u32 fence_size;u32 fence_alignment;u32 display_alignment;
PATCH v6 3/5 drm/i915: Introduce guard pages to i915_vma
In reply to Andi ShytiFrom: Chris Wilson <[email protected]>
Introduce the concept of padding the i915_vma with guard pages before and after. The major consequence is that all ordinary uses of i915_vma must use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as the drm_mm_node will include the guard pages that surround our object.
The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a PIN_OFFSET_FIXED must then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.
In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
---
Hi Tvrtko,
I removed your r-b in this version because I restored the original value of the guard being aligned with the vma size alignment. Turns out that CI failed with the latest version because the guard was becoming too big (we would have hit the GEM_BUG_ON)[*].
The reason why now the guard is aligned with the vma alignment is that the area is already aligned and if we use as a starting address start + guard, guard needs to be aligned, otherwise we screw up all the memory alignment.
Let me know if it makes sense to you.
Thanks,
Andi
Changelog
=========
v5 -> v6:
- restore the original alignment of guard so that it's aligned coherently with the vma area's alignment.
v4 -> v5:
- remove again the GEM_BUG_ON()
- fix an oversight where the rounding was called without assigning the value to the guard.
v1 -> v4:
- refer to the cover letter.
drivers/gpu/drm/i915/gt/intel_ggtt.c | 14 +++++--- drivers/gpu/drm/i915/i915_gem_gtt.h | 3 +- drivers/gpu/drm/i915/i915_vma.c | 43 ++++++++++++++++++++---- drivers/gpu/drm/i915/i915_vma.h | 5 +-- drivers/gpu/drm/i915/i915_vma_resource.c | 4 +-- drivers/gpu/drm/i915/i915_vma_resource.h | 7 +++- drivers/gpu/drm/i915/i915_vma_types.h | 1 + 7 files changed, 60 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/gt/intel_ggtt.c +10 -4
@@ -296,8 +296,11 @@ static void gen8_ggtt_insert_entries(struct i915_address_space *vm,*/ gte = (gen8_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +gen8_set_pte (gte++, vm->scratch[0 ]->encode); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)gen8_set_pte (gte++, pte_encode | addr);
@@ -347,9 +350,12 @@ static void gen6_ggtt_insert_entries(struct i915_address_space *vm,dma_addr_t addr; gte = (gen6_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +iowrite32 (vm->scratch[0 ]->encode, gte++); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)iowrite32 (vm->pte_encode (addr, level, flags), gte++);GEM_BUG_ON (gte > end);
drivers/gpu/drm/i915/i915_gem_gtt.h +2 -1
@@ -44,7 +44,8 @@ int i915_gem_gtt_insert(struct i915_address_space *vm,#define PIN_HIGH BIT_ULL(5)#define PIN_OFFSET_BIAS BIT_ULL(6)#define PIN_OFFSET_FIXED BIT_ULL(7) -#define PIN_VALIDATE BIT_ULL(8)/* validate placement only, no need to call unpin() */ +#define PIN_OFFSET_GUARD BIT_ULL(8) +#define PIN_VALIDATE BIT_ULL(9)/* validate placement only, no need to call unpin() */ #define PIN_GLOBAL BIT_ULL(10)/* I915_VMA_GLOBAL_BIND */ #define PIN_USER BIT_ULL(11)/* I915_VMA_LOCAL_BIND */
drivers/gpu/drm/i915/i915_vma.c +36 -7
100 lines not on this page · raw message
drivers/gpu/drm/i915/i915_vma.h +3 -2
@@ -128,7 +128,7 @@ static inline bool i915_vma_is_closed(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_size (const struct i915_vma *vma) { -return vma->node.size; +return vma->node.size -2 * vma->guard; }/**
@@ -150,7 +150,8 @@ static inline u64 i915_vma_size(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_offset (const struct i915_vma *vma) { -return vma->node.start; +/* The actual start of the vma->pages is after the guard pages. */ +return vma->node.start + vma->guard; }/**
drivers/gpu/drm/i915/i915_vma_resource.c +2 -2
@@ -34,8 +34,8 @@ static struct kmem_cache *slab_vma_resources;* and removal of fences increases as O(ln(pending_unbinds)) instead of * O(1) for a single fence without interval tree. */ -#define VMA_RES_START (_node) ((_node)->start) -#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size - 1) +#define VMA_RES_START (_node) ((_node)->start - (_node)->guard) +#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1) INTERVAL_TREE_DEFINE(struct i915_vma_resource, rb, u64, __subtree_last, VMA_RES_START, VMA_RES_LAST, static, vma_res_itree);
drivers/gpu/drm/i915/i915_vma_resource.h +6 -1
@@ -57,6 +57,7 @@ struct i915_page_sizes {* @node_size: Size of the allocated range manager node with padding * subtracted. * @vma_size: Bind size. +* @guard: The size of guard area preceding and trailing the bind. * @page_sizes_gtt: Resulting page sizes from the bind operation. * @bound_flags: Flags indicating binding status. * @allocated: Backend private data. TODO: Should move into @private.
@@ -115,6 +116,7 @@ struct i915_vma_resource {u64 start;u64 node_size;u64 vma_size; +u32 guard;u32 page_sizes_gtt;u32 bound_flags;
@@ -179,6 +181,7 @@ static inline void i915_vma_resource_put(struct i915_vma_resource *vma_res)* @start: Offset into the address space of bind range start after padding. * @node_size: Size of the allocated range manager node minus padding. * @size: Bind size. +* @guard: The size of the guard area preceding and trailing the bind. * * Initializes a vma resource allocated using i915_vma_resource_alloc(). * The reason for having separate allocate and initialize function is that
@@ -197,7 +200,8 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res,void *private, u64 start, u64 node_size, - u64 size) + u64 size, + u32 guard) {__i915_vma_resource_init (vma_res ); vma_res->vm = vm;
@@ -215,6 +219,7 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res, vma_res->start = start; vma_res->node_size = node_size; vma_res->vma_size = size; + vma_res->guard = guard; }static inline void i915_vma_resource_fini (struct i915_vma_resource *vma_res)
drivers/gpu/drm/i915/i915_vma_types.h +1 -0
@@ -202,6 +202,7 @@ struct i915_vma {/* mmap-offset associated with fencing for this vma */ struct i915_mmap_offset *mmo; +u32 guard;/* padding allocated around vma->pages within the node */ u32 fence_size;u32 fence_alignment;u32 display_alignment;
Signature · 1 line
2.38.1
Re: [Intel-gfx] [PATCH v6 3/5] drm/i915: Introduce guard pages to i915_vma
Quoted 39 lines · Andi Shyti
From: Chris Wilson <[email protected]>
Introduce the concept of padding the
i915_vmawith guard pages before and after. The major consequence is that all ordinary uses ofi915_vmamust use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as thedrm_mm_nodewill include the guard pages that surround our object.The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a
PIN_OFFSET_FIXEDmust then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
Signed-off-by Chris Wilson <[email protected]>Signed-off-by Tejas Upadhyay <[email protected]>Signed-off-by Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi Tvrtko,I removed your r-b in this version because I restored the original value of the guard being aligned with the vma size alignment. Turns out that CI failed with the latest version because the guard was becoming too big (we would have hit the GEM_BUG_ON)[*].
Quoted 6 lines
The reason why now the guard is aligned with the vma alignment is that the area is already aligned and if we use as a starting address start + guard, guard needs to be aligned, otherwise we screw up all the memory alignment.
Let me know if it makes sense to you.
Conditional to promise of a prioritised follow up improvement, if it turns out GGTT wastage due a bit over zealous guard size comes to bite.
Regards,
Tvrtko
Quoted 281 lines
Thanks,
AndiChangelog
=========
v5 -> v6:
- restore the original alignment of guard so that it's aligned coherently with the vma area's alignment.
v4 -> v5:
- remove again theGEM_BUG_ON()
- fix an oversight where the rounding was called without assigning the value to the guard.
v1 -> v4:
- refer to the cover letter.drivers/gpu/drm/i915/gt/intel_ggtt.c | 14 +++++--- drivers/gpu/drm/i915/i915_gem_gtt.h | 3 +- drivers/gpu/drm/i915/i915_vma.c | 43 ++++++++++++++++++++---- drivers/gpu/drm/i915/i915_vma.h | 5 +-- drivers/gpu/drm/i915/i915_vma_resource.c | 4 +-- drivers/gpu/drm/i915/i915_vma_resource.h | 7 +++- drivers/gpu/drm/i915/i915_vma_types.h | 1 + 7 files changed, 60 insertions(+), 17 deletions(-)drivers/gpu/drm/i915/gt/intel_ggtt.c +10
-4@@ -296,8 +296,11 @@ static void gen8_ggtt_insert_entries(struct i915_address_space *vm,*/ gte = (gen8_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +gen8_set_pte (gte++, vm->scratch[0 ]->encode); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)gen8_set_pte (gte++, pte_encode | addr);@@ -347,9 +350,12 @@ static void gen6_ggtt_insert_entries(struct i915_address_space *vm,dma_addr_t addr; gte = (gen6_pte_t __iomem *)ggtt->gsm; - gte += vma_res->start /I915_GTT_PAGE_SIZE ; - end = gte + vma_res->node_size /I915_GTT_PAGE_SIZE ; + gte += (vma_res->start - vma_res->guard) /I915_GTT_PAGE_SIZE ; + end = gte + vma_res->guard /I915_GTT_PAGE_SIZE ; +while (gte < end) +iowrite32 (vm->scratch[0 ]->encode, gte++); + end += (vma_res->node_size + vma_res->guard) /I915_GTT_PAGE_SIZE ;for_each_sgt_daddr (addr, iter, vma_res->bi.pages)iowrite32 (vm->pte_encode (addr, level, flags), gte++);GEM_BUG_ON (gte > end);drivers/gpu/drm/i915/i915_gem_gtt.h +2
-1@@ -44,7 +44,8 @@ int i915_gem_gtt_insert(struct i915_address_space *vm,#define PIN_HIGH BIT_ULL(5)#define PIN_OFFSET_BIAS BIT_ULL(6)#define PIN_OFFSET_FIXED BIT_ULL(7) -#define PIN_VALIDATE BIT_ULL(8)/* validate placement only, no need to call unpin() */ +#define PIN_OFFSET_GUARD BIT_ULL(8) +#define PIN_VALIDATE BIT_ULL(9)/* validate placement only, no need to call unpin() */ #define PIN_GLOBAL BIT_ULL(10)/* I915_VMA_GLOBAL_BIND */ #define PIN_USER BIT_ULL(11)/* I915_VMA_LOCAL_BIND */ drivers/gpu/drm/i915/i915_vma.c +36
-7@@ -419,7 +419,7 @@ i915_vma_resource_init_from_vma(struct i915_vma_resource *vma_res, obj->mm.rsgt,i915_gem_object_is_readonly (obj),i915_gem_object_is_lmem (obj), obj->mm.region, vma->ops, vma->private,__i915_vma_offset (vma), - __i915_vma_size(vma), vma->size); + __i915_vma_size(vma), vma->size, vma->guard); }/** @@ -677,6 +677,10 @@ bool i915_vma_misplaced(const struct i915_vma *vma, i915_vma_offset(vma) != (flags & PIN_OFFSET_MASK))return true; +if (flags &PIN_OFFSET_GUARD && + vma->guard < (flags &PIN_OFFSET_MASK )) +return true; +return false; }@@ -749,15 +753,16 @@ static int i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, u64 size, u64 alignment, u64 flags) { - unsigned long color; + unsigned long color, guard;u64 start, end;int ret;GEM_BUG_ON (i915_vma_is_bound (vma,I915_VMA_GLOBAL_BIND |I915_VMA_LOCAL_BIND ));GEM_BUG_ON (drm_mm_node_allocated (&vma->node)); +GEM_BUG_ON (hweight64 (flags & (PIN_OFFSET_GUARD |PIN_OFFSET_FIXED |PIN_OFFSET_BIAS )) >1 ); size =max (size, vma->size); - alignment =max (alignment, vma->display_alignment); + alignment =max_t (typeof (alignment), alignment, vma->display_alignment);if (flags &PIN_MAPPABLE ) { size =max_t (typeof (size), size, vma->fence_size); alignment = max_t(typeof(alignment),@@ -768,6 +773,18 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!IS_ALIGNED (alignment,I915_GTT_MIN_ALIGNMENT ));GEM_BUG_ON (!is_power_of_2 (alignment)); + guard = vma->guard;/* retain guard across rebinds */ +if (flags &PIN_OFFSET_GUARD ) { +GEM_BUG_ON (overflows_type (flags &PIN_OFFSET_MASK , u32)); + guard =max_t (u32, guard, flags &PIN_OFFSET_MASK ); + } +/* +* As we align the node upon insertion, but the hardware gets +* node.start + guard, the easiest way to make that work is +* to make the guard a multiple of the alignment size. +*/ + guard =ALIGN (guard, alignment); + start = flags &PIN_OFFSET_BIAS ? flags &PIN_OFFSET_MASK :0 ;GEM_BUG_ON (!IS_ALIGNED (start,I915_GTT_PAGE_SIZE ));@@ -780,11 +797,12 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww, alignment =max (alignment,i915_vm_obj_min_alignment (vma->vm, vma->obj)); -/* If binding the object/GGTT view requires more space than the entire +/* +* If binding the object/GGTT view requires more space than the entire * aperture has, reject it early before evicting everything in a vain * attempt to find space. */ -if (size > end) { +if (size > end -2 * guard) {drm_dbg (&to_i915 (vma->obj->base.dev)->drm,"Attempting to bind an object larger than the aperture: request=%llu > %s aperture=%llu\n" , size, flags &PIN_MAPPABLE ?"mappable" :"total" , end);@@ -801,13 +819,23 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,if (!IS_ALIGNED (offset, alignment) ||range_overflows (offset, size, end))return -EINVAL ; +/* +* The caller knows not of the guard added by others and +* requests for the offset of the start of its buffer +* to be fixed, which may not be the same as the position +* of the vma->node due to the guard pages. +*/ +if (offset < guard || offset + size > end - guard) +return -ENOSPC ; ret =i915_gem_gtt_reserve (vma->vm, ww, &vma->node, - size, offset, color, - flags); + size +2 * guard, + offset - guard, + color, flags);if (ret)return ret; }else { + size +=2 * guard;/* * We only support huge gtt pages through the 48b PPGTT, * however we also don't want to force any alignment for @@ -855,6 +883,7 @@ i915_vma_insert(struct i915_vma *vma, struct i915_gem_ww_ctx *ww,GEM_BUG_ON (!i915_gem_valid_gtt_space (vma, color));list_move_tail (&vma->vm_link, &vma->vm->bound_list); + vma->guard = guard;return 0 ; }drivers/gpu/drm/i915/i915_vma.h +3
-2@@ -128,7 +128,7 @@ static inline bool i915_vma_is_closed(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_size (const struct i915_vma *vma) { -return vma->node.size; +return vma->node.size -2 * vma->guard; }/** @@ -150,7 +150,8 @@ static inline u64 i915_vma_size(const struct i915_vma *vma)/* Internal use only. */ static inline u64 __i915_vma_offset (const struct i915_vma *vma) { -return vma->node.start; +/* The actual start of the vma->pages is after the guard pages. */ +return vma->node.start + vma->guard; }/** drivers/gpu/drm/i915/i915_vma_resource.c +2
-2@@ -34,8 +34,8 @@ static struct kmem_cache *slab_vma_resources;* and removal of fences increases as O(ln(pending_unbinds)) instead of * O(1) for a single fence without interval tree. */ -#define VMA_RES_START (_node) ((_node)->start) -#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size - 1) +#define VMA_RES_START (_node) ((_node)->start - (_node)->guard) +#define VMA_RES_LAST (_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1) INTERVAL_TREE_DEFINE(struct i915_vma_resource, rb, u64, __subtree_last, VMA_RES_START, VMA_RES_LAST, static, vma_res_itree);drivers/gpu/drm/i915/i915_vma_resource.h +6
-1@@ -57,6 +57,7 @@ struct i915_page_sizes {* @node_size: Size of the allocated range manager node with padding * subtracted. * @vma_size: Bind size. +* @guard: The size of guard area preceding and trailing the bind. * @page_sizes_gtt: Resulting page sizes from the bind operation. * @bound_flags: Flags indicating binding status. * @allocated: Backend private data. TODO: Should move into @private. @@ -115,6 +116,7 @@ struct i915_vma_resource {u64 start;u64 node_size;u64 vma_size; +u32 guard;u32 page_sizes_gtt;u32 bound_flags;@@ -179,6 +181,7 @@ static inline void i915_vma_resource_put(struct i915_vma_resource *vma_res)* @start: Offset into the address space of bind range start after padding. * @node_size: Size of the allocated range manager node minus padding. * @size: Bind size. +* @guard: The size of the guard area preceding and trailing the bind. * * Initializes a vma resource allocated using i915_vma_resource_alloc(). * The reason for having separate allocate and initialize function is that @@ -197,7 +200,8 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res,void *private, u64 start, u64 node_size, - u64 size) + u64 size, + u32 guard) {__i915_vma_resource_init (vma_res ); vma_res->vm = vm;@@ -215,6 +219,7 @@ static inline void i915_vma_resource_init(struct i915_vma_resource *vma_res, vma_res->start = start; vma_res->node_size = node_size; vma_res->vma_size = size; + vma_res->guard = guard; }static inline void i915_vma_resource_fini (struct i915_vma_resource *vma_res)drivers/gpu/drm/i915/i915_vma_types.h +1
-0@@ -202,6 +202,7 @@ struct i915_vma {/* mmap-offset associated with fencing for this vma */ struct i915_mmap_offset *mmo; +u32 guard;/* padding allocated around vma->pages within the node */ u32 fence_size;u32 fence_alignment;u32 display_alignment;
Re: [Intel-gfx] [PATCH v6 3/5] drm/i915: Introduce guard pages to i915_vma
Hi Tvrtko,
Quoted 46 lines · Tvrtko Ursulin
Quoted 44 lines · Andi Shyti
From: Chris Wilson <[email protected]>
Introduce the concept of padding the
i915_vmawith guard pages before and after. The major consequence is that all ordinary uses ofi915_vmamust use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as thedrm_mm_nodewill include the guard pages that surround our object.The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a
PIN_OFFSET_FIXEDmust then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
Signed-off-by Chris Wilson <[email protected]>Signed-off-by Tejas Upadhyay <[email protected]>Signed-off-by Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi Tvrtko,I removed your r-b in this version because I restored the original value of the guard being aligned with the vma size alignment. Turns out that CI failed with the latest version because the guard was becoming too big (we would have hit the GEM_BUG_ON)[*].
The reason why now the guard is aligned with the vma alignment is that the area is already aligned and if we use as a starting address start + guard, guard needs to be aligned, otherwise we screw up all the memory alignment.
Quoted 6 lines
Quoted 1 line
Let me know if it makes sense to you.
Reviewed-by Tvrtko Ursulin <[email protected]>Conditional to promise of a prioritised follow up improvement, if it turns out GGTT wastage due a bit over zealous guard size comes to bite.
Sure! I'll be alert!
There are some unrelated failures from CI, just to be sure I sent last night a trybot run.
Thanks, Tvrtko!
Andi
Re: [Intel-gfx] [PATCH v6 3/5] drm/i915: Introduce guard pages to i915_vma
Quoted 53 lines · Andi Shyti
Hi Tvrtko,
Quoted 50 lines · Tvrtko Ursulin
Quoted 39 lines · Andi Shyti
From: Chris Wilson <[email protected]>
Introduce the concept of padding the
i915_vmawith guard pages before and after. The major consequence is that all ordinary uses ofi915_vmamust use i915_vma_offset/i915_vma_size and not i915_vma.node.start/size directly, as thedrm_mm_nodewill include the guard pages that surround our object.The biggest connundrum is how exactly to mix requesting a fixed address with guard pages, particularly through the existing uABI. The user does not know about guard pages, so such must be transparent to the user, and so the execobj.offset must be that of the object itself excluding the guard. So a
PIN_OFFSET_FIXEDmust then be exclusive of the guard pages. The caveat is that some placements will be impossible with guard pages, as wrap arounds need to be avoided, and the vma itself will require a larger node. We must not report EINVAL but ENOSPC as these are unavailable locations within the GTT rather than conflicting user requirements.In the next patch, we start using guard pages for scanout objects. While these are limited to GGTT vma, on a few platforms these vma (or at least an alias of the vma) is shared with userspace, so we may leak the existence of such guards if we are not careful to ensure that the execobj.offset is transparent and excludes the guards. (On such platforms like ivb, without full-ppgtt, userspace has to use relocations so the presence of more untouchable regions within its GTT such be of no further issue.)
Signed-off-by Chris Wilson <[email protected]>Signed-off-by Tejas Upadhyay <[email protected]>Signed-off-by Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi Tvrtko,I removed your r-b in this version because I restored the original value of the guard being aligned with the vma size alignment. Turns out that CI failed with the latest version because the guard was becoming too big (we would have hit the GEM_BUG_ON)[*].
Quoted 6 lines
The reason why now the guard is aligned with the vma alignment is that the area is already aligned and if we use as a starting address start + guard, guard needs to be aligned, otherwise we screw up all the memory alignment.
Let me know if it makes sense to you.
Reviewed-by Tvrtko Ursulin <[email protected]>
Quoted 7 lines
Quoted 2 lines
Conditional to promise of a prioritised follow up improvement, if it turns out GGTT wastage due a bit over zealous guard size comes to bite.
Sure! I'll be alert!
There are some unrelated failures from CI, just to be sure I sent last night a trybot run.
Trybot looked okay, and I just pressed re-test for the intel-gfx series so lets see that too.
Regards,
Tvrtko
PATCH v4 4/5 drm/i915: Refine VT-d scanout workaround
In reply to Andi ShytiFrom: Chris Wilson <[email protected]>
VT-d may cause overfetch of the scanout PTE, both before and after the vma (depending on the scanout orientation). bspec recommends that we provide a tile-row in either directions, and suggests using 168 PTE, warning that the accesses will wrap around the ends of the GGTT. Currently, we fill the entire GGTT with scratch pages when using VT-d to always ensure there are valid entries around every vma, including scanout. However, writing every PTE is slow as on recent devices we perform 8MiB of uncached writes, incurring an extra 100ms during resume.
If instead we focus on only putting guard pages around scanout, we can avoid touching the whole GGTT. To avoid having to introduce extra nodes around each scanout vma, we adjust the scanout drm_mm_node to be smaller than the allocated space, and fixup the extra PTE during dma binding.
--- drivers/gpu/drm/i915/gem/i915_gem_domain.c | 13 +++++++++++ drivers/gpu/drm/i915/gt/intel_ggtt.c | 25 +--------------------- 2 files changed, 14 insertions(+), 24 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_domain.c +13 -0
@@ -17,6 +17,8 @@#include "i915_gem_object.h" #include "i915_vma.h" +#define VTD_GUARD (168u * I915_GTT_PAGE_SIZE)/* 168 or tile-row PTE padding */ +static bool gpu_write_needs_clflush (struct drm_i915_gem_object *obj) {struct drm_i915_private *i915 =to_i915 (obj->base.dev);
@@ -424,6 +426,17 @@ i915_gem_object_pin_to_display_plane(struct drm_i915_gem_object *obj,if (ret)return ERR_PTR (ret); +/* VT-d may overfetch before/after the vma, so pad with scratch */ +if (intel_scanout_needs_vtd_wa (i915)) { +unsigned int guard =VTD_GUARD ; + +if (i915_gem_object_is_tiled (obj)) + guard =max (guard, +i915_gem_object_get_tile_row_size (obj)); + + flags |=PIN_OFFSET_GUARD | guard; + } +/* * As the user may map the buffer once pinned in the display plane * (e.g. libkms for the bootup splash), we have to ensure that we
drivers/gpu/drm/i915/gt/intel_ggtt.c +1 -24
@@ -376,27 +376,6 @@ static void nop_clear_range(struct i915_address_space *vm, { } -static void gen8_ggtt_clear_range (struct i915_address_space *vm, -u64 start,u64 length) -{ -struct i915_ggtt *ggtt =i915_vm_to_ggtt (vm); -unsigned int first_entry = start /I915_GTT_PAGE_SIZE ; -unsigned int num_entries = length /I915_GTT_PAGE_SIZE ; -const gen8_pte_t scratch_pte = vm->scratch[0 ]->encode; -gen8_pte_t __iomem *gtt_base = - (gen8_pte_t __iomem *)ggtt->gsm + first_entry; -const int max_entries =ggtt_total_entries (ggtt) - first_entry; -int i; - -if (WARN (num_entries > max_entries, -"First entry = %d; Num entries = %d (max=%d)\n" , - first_entry, num_entries, max_entries)) - num_entries = max_entries; - -for (i =0 ; i < num_entries; i++) -gen8_set_pte (>t_base[i], scratch_pte); -} -static void bxt_vtd_ggtt_wa (struct i915_address_space *vm) {/*
@@ -968,8 +947,6 @@ static int gen8_gmch_probe(struct i915_ggtt *ggtt) ggtt->vm.cleanup = gen6_gmch_remove; ggtt->vm.insert_page = gen8_ggtt_insert_page; ggtt->vm.clear_range = nop_clear_range; -if (intel_scanout_needs_vtd_wa (i915)) - ggtt->vm.clear_range = gen8_ggtt_clear_range; ggtt->vm.insert_entries = gen8_ggtt_insert_entries;
@@ -1128,7 +1105,7 @@ static int gen6_gmch_probe(struct i915_ggtt *ggtt) ggtt->vm.alloc_scratch_dma = alloc_pt_dma; ggtt->vm.clear_range = nop_clear_range; -if (!HAS_FULL_PPGTT (i915) ||intel_scanout_needs_vtd_wa (i915)) +if (!HAS_FULL_PPGTT (i915)) ggtt->vm.clear_range = gen6_ggtt_clear_range; ggtt->vm.insert_page = gen6_ggtt_insert_page; ggtt->vm.insert_entries = gen6_ggtt_insert_entries;
Signature · 1 line
2.38.1
Re: [Intel-gfx] [PATCH v4 4/5] drm/i915: Refine VT-d scanout workaround
Quoted 98 lines · Andi Shyti
From: Chris Wilson <[email protected]>
VT-d may cause overfetch of the scanout PTE, both before and after the vma (depending on the scanout orientation). bspec recommends that we provide a tile-row in either directions, and suggests using 168 PTE, warning that the accesses will wrap around the ends of the GGTT. Currently, we fill the entire GGTT with scratch pages when using VT-d to always ensure there are valid entries around every vma, including scanout. However, writing every PTE is slow as on recent devices we perform 8MiB of uncached writes, incurring an extra 100ms during resume.
If instead we focus on only putting guard pages around scanout, we can avoid touching the whole GGTT. To avoid having to introduce extra nodes around each scanout vma, we adjust the scanout
drm_mm_nodeto be smaller than the allocated space, and fixup the extra PTE during dma binding.Signed-off-by Chris Wilson <[email protected]>Signed-off-by Tejas Upadhyay <[email protected]>Signed-off-by Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>--- drivers/gpu/drm/i915/gem/i915_gem_domain.c | 13 +++++++++++ drivers/gpu/drm/i915/gt/intel_ggtt.c | 25 +--------------------- 2 files changed, 14 insertions(+), 24 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_domain.c +13
-0@@ -17,6 +17,8 @@#include "i915_gem_object.h" #include "i915_vma.h" +#define VTD_GUARD (168u * I915_GTT_PAGE_SIZE)/* 168 or tile-row PTE padding */ +static bool gpu_write_needs_clflush (struct drm_i915_gem_object *obj) {struct drm_i915_private *i915 =to_i915 (obj->base.dev);@@ -424,6 +426,17 @@ i915_gem_object_pin_to_display_plane(struct drm_i915_gem_object *obj,if (ret)return ERR_PTR (ret); +/* VT-d may overfetch before/after the vma, so pad with scratch */ +if (intel_scanout_needs_vtd_wa (i915)) { +unsigned int guard =VTD_GUARD ; + +if (i915_gem_object_is_tiled (obj)) + guard =max (guard, +i915_gem_object_get_tile_row_size (obj)); + + flags |=PIN_OFFSET_GUARD | guard; + } +/* * As the user may map the buffer once pinned in the display plane * (e.g. libkms for the bootup splash), we have to ensure that we drivers/gpu/drm/i915/gt/intel_ggtt.c +0
-23@@ -376,27 +376,6 @@ static void nop_clear_range(struct i915_address_space *vm, { } -static void gen8_ggtt_clear_range (struct i915_address_space *vm, -u64 start,u64 length) -{ -struct i915_ggtt *ggtt =i915_vm_to_ggtt (vm); -unsigned int first_entry = start /I915_GTT_PAGE_SIZE ; -unsigned int num_entries = length /I915_GTT_PAGE_SIZE ; -const gen8_pte_t scratch_pte = vm->scratch[0 ]->encode; -gen8_pte_t __iomem *gtt_base = - (gen8_pte_t __iomem *)ggtt->gsm + first_entry; -const int max_entries =ggtt_total_entries (ggtt) - first_entry; -int i; - -if (WARN (num_entries > max_entries, -"First entry = %d; Num entries = %d (max=%d)\n" , - first_entry, num_entries, max_entries)) - num_entries = max_entries; - -for (i =0 ; i < num_entries; i++) -gen8_set_pte (>t_base[i], scratch_pte); -} -static void bxt_vtd_ggtt_wa (struct i915_address_space *vm) {/* @@ -968,8 +947,6 @@ static int gen8_gmch_probe(struct i915_ggtt *ggtt) ggtt->vm.cleanup = gen6_gmch_remove; ggtt->vm.insert_page = gen8_ggtt_insert_page; ggtt->vm.clear_range = nop_clear_range; -if (intel_scanout_needs_vtd_wa (i915)) - ggtt->vm.clear_range = gen8_ggtt_clear_range; ggtt->vm.insert_entries = gen8_ggtt_insert_entries;
drivers/gpu/drm/i915/gt/intel_ggtt.c static int gen6_gmch_probe(struct i915_ggtt *ggtt) · line 1111
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_ggtt.c +1
-1@@ -1128,7 +1105,7 @@ static int gen6_gmch_probe(struct i915_ggtt *ggtt) ggtt->vm.alloc_scratch_dma = alloc_pt_dma; ggtt->vm.clear_range = nop_clear_range; -if (!HAS_FULL_PPGTT (i915) ||intel_scanout_needs_vtd_wa (i915)) +if (!HAS_FULL_PPGTT (i915)) ggtt->vm.clear_range = gen6_ggtt_clear_range; ggtt->vm.insert_page = gen6_ggtt_insert_page; ggtt->vm.insert_entries = gen6_ggtt_insert_entries;
Regards,
Tvrtko
PATCH v4 5/5 Revert "drm/i915: Improve on suspend / resume time with VT-d enabled"
In reply to Andi ShytiThis reverts commit 2ef6efa79fecd5e3457b324155d35524d95f2b6b.
Checking the presence if the IRST (Intel Rapid Start Technology) through the ACPI to decide whether to rebuild or not the GGTT puts us at the mercy of the boot firmware and we need to unnecessarily rely on third parties.
Because now we avoid adding scratch pages to the entire GGTT we don't need this hack anymore.
--- drivers/gpu/drm/i915/gt/intel_ggtt.c | 69 ++++++---------------------- drivers/gpu/drm/i915/gt/intel_gtt.h | 24 ---------- drivers/gpu/drm/i915/i915_driver.c | 16 ------- 3 files changed, 13 insertions(+), 96 deletions(-)
drivers/gpu/drm/i915/gt/intel_ggtt.c +13 -56
@@ -27,13 +27,6 @@#include "intel_gtt.h" #include "gen8_ppgtt.h" -static inline bool suspend_retains_ptes (struct i915_address_space *vm) -{ -return GRAPHICS_VER (vm->i915) >=8 && - !HAS_LMEM (vm->i915) && - vm->is_ggtt; -} - static void i915_ggtt_color_adjust(const struct drm_mm_node *node, unsigned long color, u64 *start,
@@ -105,23 +98,6 @@ int i915_ggtt_init_hw(struct drm_i915_private *i915)return 0 ; } -/* -* Return the value of the last GGTT pte cast to an u64, if -* the system is supposed to retain ptes across resume. 0 otherwise. -*/ -static u64 read_last_pte (struct i915_address_space *vm) -{ -struct i915_ggtt *ggtt =i915_vm_to_ggtt (vm); -gen8_pte_t __iomem *ptep; - -if (!suspend_retains_ptes (vm)) -return 0 ; - -GEM_BUG_ON (GRAPHICS_VER (vm->i915) <8 ); - ptep = (typeof (ptep ))ggtt->gsm + (ggtt_total_entries (ggtt) -1 ); -return readq (ptep); -} -/** * i915_ggtt_suspend_vm - Suspend the memory mappings for a GGTT or DPT VM * @vm: The VM to suspend the mappings for
@@ -185,10 +161,7 @@ void i915_ggtt_suspend_vm(struct i915_address_space *vm)i915_gem_object_unlock (obj); } -if (!suspend_retains_ptes (vm)) - vm->clear_range (vm,0 , vm->total); -else -i915_vm_to_ggtt (vm)->probed_pte =read_last_pte (vm); + vm->clear_range (vm,0 , vm->total); vm->skip_pte_rewrite = save_skip_rewrite;
@@ -545,8 +518,6 @@ static int init_ggtt(struct i915_ggtt *ggtt)struct drm_mm_node *entry;int ret; - ggtt->pte_lost = true; -/* * GuC requires all resources that we're sharing with it to be placed in * non-WOPCM memory. If GuC is not present or not in use we still need a
@@ -1263,20 +1234,11 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm) {struct i915_vma *vma;bool write_domain_objs = false; -bool retained_ptes;drm_WARN_ON (&vm->i915->drm, !vm->is_ggtt && !vm->is_dpt); -/* -* First fill our portion of the GTT with scratch pages if -* they were not retained across suspend. -*/ - retained_ptes =suspend_retains_ptes (vm) && - !i915_vm_to_ggtt (vm)->pte_lost && - !GEM_WARN_ON (i915_vm_to_ggtt (vm)->probed_pte !=read_last_pte (vm)); - -if (!retained_ptes) - vm->clear_range (vm,0 , vm->total); +/* First fill our portion of the GTT with scratch pages */ + vm->clear_range (vm,0 , vm->total);/* clflush objects bound into the GGTT and rebind them. */ list_for_each_entry (vma, &vm->bound_list, vm_link) {
@@ -1285,16 +1247,16 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm)atomic_read (&vma->flags) &I915_VMA_BIND_MASK ;GEM_BUG_ON (!was_bound); -if (!retained_ptes) { -/* -* Clear the bound flags of the vma resource to allow -* ptes to be repopulated. -*/ - vma->resource->bound_flags =0 ; - vma->ops->bind_vma (vm,NULL , vma->resource, - obj ? obj->cache_level :0 , - was_bound); - } + +/* +* Clear the bound flags of the vma resource to allow +* ptes to be repopulated. +*/ + vma->resource->bound_flags =0 ; + vma->ops->bind_vma (vm,NULL , vma->resource, + obj ? obj->cache_level :0 , + was_bound); +if (obj) {/* only used during resume => exclusive access */ write_domain_objs |=fetch_and_zero (&obj->write_domain); obj->read_domains |=I915_GEM_DOMAIN_GTT ;
@@ -1321,8 +1283,3 @@ void i915_ggtt_resume(struct i915_ggtt *ggtt)intel_ggtt_restore_fences (ggtt); } - -void i915_ggtt_mark_pte_lost (struct drm_i915_private *i915,bool val) -{ -to_gt (i915)->ggtt->pte_lost = val; -}
drivers/gpu/drm/i915/gt/intel_gtt.h +0 -24
@@ -355,19 +355,6 @@ struct i915_ggtt {bool do_idle_maps; -/** -* @pte_lost: Are ptes lost on resume? -* -* Whether the system was recently restored from hibernate and -* thus may have lost pte content. -*/ -bool pte_lost; - -/** -* @probed_pte: Probed pte value on suspend. Re-checked on resume. -*/ -u64 probed_pte; -int mtrr;/** Bit 6 swizzling required for X tiling */
@@ -604,17 +591,6 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm);void i915_ggtt_suspend (struct i915_ggtt *gtt);void i915_ggtt_resume (struct i915_ggtt *ggtt); -/** -* i915_ggtt_mark_pte_lost - Mark ggtt ptes as lost or clear such a marking -* @i915 The device private. -* @val whether the ptes should be marked as lost. -* -* In some cases pte content is retained across suspend, but typically lost -* across hibernate. Typically they should be marked as lost on -* hibernation restore and such marking cleared on suspend. -*/ -void i915_ggtt_mark_pte_lost (struct drm_i915_private *i915,bool val); -void fill_page_dma (struct drm_i915_gem_object *p,const u64 val,unsigned int count);
drivers/gpu/drm/i915/i915_driver.c +0 -16
@@ -102,9 +102,6 @@#include "intel_region_ttm.h" #include "vlv_suspend.h" -/* Intel Rapid Start Technology ACPI device name */ -static const char irst_name[] ="INT3392" ; -static const struct drm_driver i915_drm_driver; static void i915_release_bridge_dev(struct drm_device *dev,
@@ -1496,8 +1493,6 @@ static int i915_pm_suspend(struct device *kdev)return -ENODEV ; } -i915_ggtt_mark_pte_lost (i915, false); -if (i915->drm.switch_power_state ==DRM_SWITCH_POWER_OFF )return 0 ;
@@ -1550,14 +1545,6 @@ static int i915_pm_resume(struct device *kdev)if (i915->drm.switch_power_state ==DRM_SWITCH_POWER_OFF )return 0 ; -/* -* If IRST is enabled, or if we can't detect whether it's enabled, -* then we must assume we lost the GGTT page table entries, since -* they are not retained if IRST decided to enter S4. -*/ -if (!IS_ENABLED (CONFIG_ACPI ) ||acpi_dev_present (irst_name,NULL ,-1 )) -i915_ggtt_mark_pte_lost (i915, true); -return i915_drm_resume (&i915->drm); }
@@ -1617,9 +1604,6 @@ static int i915_pm_restore_early(struct device *kdev)static int i915_pm_restore (struct device *kdev) { -struct drm_i915_private *i915 =kdev_to_i915 (kdev); - -i915_ggtt_mark_pte_lost (i915, true);return i915_pm_resume (kdev); }
Signature · 1 line
2.38.1
Re: [Intel-gfx] [PATCH v4 5/5] Revert "drm/i915: Improve on suspend / resume time with VT-d enabled"
Quoted 223 lines · Andi Shyti
This reverts commit
2ef6efa79fecd5e3457b324155d35524d95f2b6b.Checking the presence if the IRST (Intel Rapid Start Technology) through the ACPI to decide whether to rebuild or not the GGTT puts us at the mercy of the boot firmware and we need to unnecessarily rely on third parties.
Because now we avoid adding scratch pages to the entire GGTT we don't need this hack anymore.
Signed-off-by Andi Shyti <[email protected]>Cc Thomas Hellström <[email protected]>Cc Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>--- drivers/gpu/drm/i915/gt/intel_ggtt.c | 69 ++++++---------------------- drivers/gpu/drm/i915/gt/intel_gtt.h | 24 ---------- drivers/gpu/drm/i915/i915_driver.c | 16 ------- 3 files changed, 13 insertions(+), 96 deletions(-)drivers/gpu/drm/i915/gt/intel_ggtt.c +13
-56@@ -27,13 +27,6 @@#include "intel_gtt.h" #include "gen8_ppgtt.h" -static inline bool suspend_retains_ptes (struct i915_address_space *vm) -{ -return GRAPHICS_VER (vm->i915) >=8 && - !HAS_LMEM (vm->i915) && - vm->is_ggtt; -} - static void i915_ggtt_color_adjust(const struct drm_mm_node *node, unsigned long color, u64 *start,@@ -105,23 +98,6 @@ int i915_ggtt_init_hw(struct drm_i915_private *i915)return 0 ; } -/* -* Return the value of the last GGTT pte cast to an u64, if -* the system is supposed to retain ptes across resume. 0 otherwise. -*/ -static u64 read_last_pte (struct i915_address_space *vm) -{ -struct i915_ggtt *ggtt =i915_vm_to_ggtt (vm); -gen8_pte_t __iomem *ptep; - -if (!suspend_retains_ptes (vm)) -return 0 ; - -GEM_BUG_ON (GRAPHICS_VER (vm->i915) <8 ); - ptep = (typeof (ptep ))ggtt->gsm + (ggtt_total_entries (ggtt) -1 ); -return readq (ptep); -} -/** * i915_ggtt_suspend_vm - Suspend the memory mappings for a GGTT or DPT VM * @vm: The VM to suspend the mappings for @@ -185,10 +161,7 @@ void i915_ggtt_suspend_vm(struct i915_address_space *vm)i915_gem_object_unlock (obj); } -if (!suspend_retains_ptes (vm)) - vm->clear_range (vm,0 , vm->total); -else -i915_vm_to_ggtt (vm)->probed_pte =read_last_pte (vm); + vm->clear_range (vm,0 , vm->total); vm->skip_pte_rewrite = save_skip_rewrite;@@ -545,8 +518,6 @@ static int init_ggtt(struct i915_ggtt *ggtt)struct drm_mm_node *entry;int ret; - ggtt->pte_lost = true; -/* * GuC requires all resources that we're sharing with it to be placed in * non-WOPCM memory. If GuC is not present or not in use we still need a @@ -1263,20 +1234,11 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm) {struct i915_vma *vma;bool write_domain_objs = false; -bool retained_ptes;drm_WARN_ON (&vm->i915->drm, !vm->is_ggtt && !vm->is_dpt); -/* -* First fill our portion of the GTT with scratch pages if -* they were not retained across suspend. -*/ - retained_ptes =suspend_retains_ptes (vm) && - !i915_vm_to_ggtt (vm)->pte_lost && - !GEM_WARN_ON (i915_vm_to_ggtt (vm)->probed_pte !=read_last_pte (vm)); - -if (!retained_ptes) - vm->clear_range (vm,0 , vm->total); +/* First fill our portion of the GTT with scratch pages */ + vm->clear_range (vm,0 , vm->total);/* clflush objects bound into the GGTT and rebind them. */ list_for_each_entry (vma, &vm->bound_list, vm_link) {@@ -1285,16 +1247,16 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm)atomic_read (&vma->flags) &I915_VMA_BIND_MASK ;GEM_BUG_ON (!was_bound); -if (!retained_ptes) { -/* -* Clear the bound flags of the vma resource to allow -* ptes to be repopulated. -*/ - vma->resource->bound_flags =0 ; - vma->ops->bind_vma (vm,NULL , vma->resource, - obj ? obj->cache_level :0 , - was_bound); - } + +/* +* Clear the bound flags of the vma resource to allow +* ptes to be repopulated. +*/ + vma->resource->bound_flags =0 ; + vma->ops->bind_vma (vm,NULL , vma->resource, + obj ? obj->cache_level :0 , + was_bound); +if (obj) {/* only used during resume => exclusive access */ write_domain_objs |=fetch_and_zero (&obj->write_domain); obj->read_domains |=I915_GEM_DOMAIN_GTT ;@@ -1321,8 +1283,3 @@ void i915_ggtt_resume(struct i915_ggtt *ggtt)intel_ggtt_restore_fences (ggtt); } - -void i915_ggtt_mark_pte_lost (struct drm_i915_private *i915,bool val) -{ -to_gt (i915)->ggtt->pte_lost = val; -}drivers/gpu/drm/i915/gt/intel_gtt.h +0
-24@@ -355,19 +355,6 @@ struct i915_ggtt {bool do_idle_maps; -/** -* @pte_lost: Are ptes lost on resume? -* -* Whether the system was recently restored from hibernate and -* thus may have lost pte content. -*/ -bool pte_lost; - -/** -* @probed_pte: Probed pte value on suspend. Re-checked on resume. -*/ -u64 probed_pte; -int mtrr;/** Bit 6 swizzling required for X tiling */ @@ -604,17 +591,6 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm);void i915_ggtt_suspend (struct i915_ggtt *gtt);void i915_ggtt_resume (struct i915_ggtt *ggtt); -/** -* i915_ggtt_mark_pte_lost - Mark ggtt ptes as lost or clear such a marking -* @i915 The device private. -* @val whether the ptes should be marked as lost. -* -* In some cases pte content is retained across suspend, but typically lost -* across hibernate. Typically they should be marked as lost on -* hibernation restore and such marking cleared on suspend. -*/ -void i915_ggtt_mark_pte_lost (struct drm_i915_private *i915,bool val); -void fill_page_dma (struct drm_i915_gem_object *p,const u64 val,unsigned int count);drivers/gpu/drm/i915/i915_driver.c +0
-13@@ -102,9 +102,6 @@#include "intel_region_ttm.h" #include "vlv_suspend.h" -/* Intel Rapid Start Technology ACPI device name */ -static const char irst_name[] ="INT3392" ; -static const struct drm_driver i915_drm_driver; static void i915_release_bridge_dev(struct drm_device *dev,@@ -1496,8 +1493,6 @@ static int i915_pm_suspend(struct device *kdev)return -ENODEV ; } -i915_ggtt_mark_pte_lost (i915, false); -if (i915->drm.switch_power_state ==DRM_SWITCH_POWER_OFF )return 0 ;@@ -1550,14 +1545,6 @@ static int i915_pm_resume(struct device *kdev)if (i915->drm.switch_power_state ==DRM_SWITCH_POWER_OFF )return 0 ; -/* -* If IRST is enabled, or if we can't detect whether it's enabled, -* then we must assume we lost the GGTT page table entries, since -* they are not retained if IRST decided to enter S4. -*/ -if (!IS_ENABLED (CONFIG_ACPI ) ||acpi_dev_present (irst_name,NULL ,-1 )) -i915_ggtt_mark_pte_lost (i915, true); -return i915_drm_resume (&i915->drm); }
drivers/gpu/drm/i915/i915_driver.c static int i915_pm_restore_early(struct device *kdev) · line 1609
Quoted 9 lines
drivers/gpu/drm/i915/i915_driver.c +0
-3@@ -1617,9 +1604,6 @@ static int i915_pm_restore_early(struct device *kdev)static int i915_pm_restore (struct device *kdev) { -struct drm_i915_private *i915 =kdev_to_i915 (kdev); - -i915_ggtt_mark_pte_lost (i915, true);return i915_pm_resume (kdev); }
Regards,
Tvrtko
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for add guard padding around i915_vma (rev4)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev4)
URL : https://patchwork.freedesktop.org/series/110720/
State : warning
== Summary ==
Error: dim checkpatch failed6a062612120d drm/i915: Limit the display memory alignment to 32 bit instead of 64ab5c06d48524 drm/i915: Wrap all access to i915_vma.node.start|size
-:264: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #264: FILE: drivers/gpu/drm/i915/gem/selftests/i915_gem_client_blt.c:475:
+ GEM_BUG_ON(i915_vma_offset(vma) != addr);
-:356: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #356: FILE: drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c:65:
+ GEM_BUG_ON(offset + (count - 1) * PAGE_SIZE > i915_vma_size(vma));
-:393: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #393: FILE: drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c:223:
+ GEM_BUG_ON(vma->fence_size > i915_vma_size(vma));
-:787: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #787: FILE: drivers/gpu/drm/i915/i915_vma.c:450:
+ GEM_BUG_ON(vma->size > i915_vma_size(vma));
-:870: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #870: FILE: drivers/gpu/drm/i915/i915_vma.h:146:
+ GEM_BUG_ON(!drm_mm_node_allocated(&vma->node));
-:892: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #892: FILE: drivers/gpu/drm/i915/i915_vma.h:168:
+ GEM_BUG_ON(!drm_mm_node_allocated(&vma->node));
-:903: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #903: FILE: drivers/gpu/drm/i915/i915_vma.h:176:
+ GEM_BUG_ON(upper_32_bits(i915_vma_offset(vma)));
-:904: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #904: FILE: drivers/gpu/drm/i915/i915_vma.h:177:
+ GEM_BUG_ON(upper_32_bits(i915_vma_offset(vma) +
total: 0 errors, 8 warnings, 0 checks, 805 lines checkeda4f3a8fe82af drm/i915: Introduce guard pages to i915_vma
-:118: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #118: FILE: drivers/gpu/drm/i915/i915_vma.c:762:
+ GEM_BUG_ON(hweight64(flags & (PIN_OFFSET_GUARD | PIN_OFFSET_FIXED | PIN_OFFSET_BIAS)) > 1);
-:132: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #132: FILE: drivers/gpu/drm/i915/i915_vma.c:778:
+ GEM_BUG_ON(overflows_type(flags & PIN_OFFSET_MASK, u32));
-:140: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #140: FILE: drivers/gpu/drm/i915/i915_vma.c:786:
+ GEM_BUG_ON(2 * guard > end);
-:226: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_node' - possible side-effects? #226: FILE: drivers/gpu/drm/i915/i915_vma_resource.c:37:
+#define VMA_RES_START(_node) ((_node)->start - (_node)->guard)
-:227: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_node' - possible side-effects? #227: FILE: drivers/gpu/drm/i915/i915_vma_resource.c:38:
+#define VMA_RES_LAST(_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1)
total: 0 errors, 3 warnings, 2 checks, 206 lines checked6b9ed1df2f64 drm/i915: Refine VT-d scanout workaround0a415a58613e Revert "drm/i915: Improve on suspend / resume time with VT-d enabled"
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for add guard padding around i915_vma (rev4)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev4)
URL : https://patchwork.freedesktop.org/series/110720/
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: failure for add guard padding around i915_vma (rev4)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev4)
URL : https://patchwork.freedesktop.org/series/110720/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12457 -> Patchwork_110720v4
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_110720v4 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_110720v4, 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_110720v4/index.html
Participating hosts (38 -> 35)
------------------------------
Missing (3): fi-ilk-m540 fi-cfl-8700k fi-tgl-dsi
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_110720v4:
### IGT changes ###
#### Possible regressions ####
* igt@i915_module_load@load:
- fi-rkl-11600: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-rkl-11600/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-rkl-11600/igt@[email protected]
- fi-icl-u2: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-icl-u2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-icl-u2/igt@[email protected]
- fi-apl-guc: [PASS][5] -> [INCOMPLETE][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-apl-guc/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-apl-guc/igt@[email protected]
- fi-glk-j4005: [PASS][7] -> [INCOMPLETE][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-glk-j4005/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-glk-j4005/igt@[email protected]
- fi-rkl-guc: [PASS][9] -> [INCOMPLETE][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-rkl-guc/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-rkl-guc/igt@[email protected]
- fi-skl-guc: [PASS][11] -> [INCOMPLETE][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-skl-guc/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-skl-guc/igt@[email protected]
- bat-dg1-6: [PASS][13] -> [INCOMPLETE][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-dg1-6/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-dg1-6/igt@[email protected]
- fi-adl-ddr5: [PASS][15] -> [INCOMPLETE][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-adl-ddr5/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-adl-ddr5/igt@[email protected]
- fi-kbl-x1275: [PASS][17] -> [INCOMPLETE][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-kbl-x1275/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-kbl-x1275/igt@[email protected]
- fi-cfl-8109u: [PASS][19] -> [INCOMPLETE][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-cfl-8109u/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-cfl-8109u/igt@[email protected]
- fi-ivb-3770: [PASS][21] -> [INCOMPLETE][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-ivb-3770/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-ivb-3770/igt@[email protected]
* igt@kms_force_connector_basic@prune-stale-modes:
- fi-kbl-8809g: [PASS][23] -> [DMESG-WARN][24] +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-kbl-8809g/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-kbl-8809g/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@i915_module_load@load:
- {bat-jsl-1}: [PASS][25] -> [INCOMPLETE][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-jsl-1/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-jsl-1/igt@[email protected]
- {fi-jsl-1}: [PASS][27] -> [INCOMPLETE][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-jsl-1/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-jsl-1/igt@[email protected]
- {bat-adlp-6}: [PASS][29] -> [INCOMPLETE][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-adlp-6/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-adlp-6/igt@[email protected]
- {fi-ehl-2}: [PASS][31] -> [INCOMPLETE][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-ehl-2/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-ehl-2/igt@[email protected]
- {bat-adln-1}: [PASS][33] -> [INCOMPLETE][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-adln-1/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-adln-1/igt@[email protected]
- {bat-rplp-1}: [PASS][35] -> [INCOMPLETE][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-rplp-1/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-rplp-1/igt@[email protected]
- {bat-rpls-2}: [PASS][37] -> [INCOMPLETE][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-rpls-2/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-rpls-2/igt@[email protected]
* igt@kms_force_connector_basic@force-connector-state:
- {bat-adlm-1}: [PASS][39] -> [DMESG-WARN][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-adlm-1/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-adlm-1/igt@[email protected]
- {bat-rpls-1}: [PASS][41] -> [DMESG-WARN][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-rpls-1/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-rpls-1/igt@[email protected]
- {bat-dg1-7}: [PASS][43] -> [DMESG-WARN][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-dg1-7/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-dg1-7/igt@[email protected]
- {bat-kbl-2}: [PASS][45] -> [DMESG-WARN][46] +2 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/bat-kbl-2/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-kbl-2/igt@[email protected]
New tests
---------
New tests have been introduced between CI_DRM_12457 and Patchwork_110720v4:
### New IGT tests (1) ###
* igt@kms_frontbuffer_tracking:
- Statuses :
- Exec time: [None] s
Known issues
------------
Here are the changes found in Patchwork_110720v4 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@runner@aborted:
- fi-kbl-x1275: NOTRUN -> [FAIL][47] ([i915#4312])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-kbl-x1275/igt@[email protected]
- fi-cfl-8109u: NOTRUN -> [FAIL][48] ([i915#4312])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-cfl-8109u/igt@[email protected]
- fi-ivb-3770: NOTRUN -> [FAIL][49] ([i915#4312])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-ivb-3770/igt@[email protected]
- fi-icl-u2: NOTRUN -> [FAIL][50] ([i915#4312])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-icl-u2/igt@[email protected]
- fi-apl-guc: NOTRUN -> [FAIL][51] ([i915#4312])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-apl-guc/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [FAIL][52] ([i915#4312])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-glk-j4005/igt@[email protected]
- fi-rkl-guc: NOTRUN -> [FAIL][53] ([i915#4312])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-rkl-guc/igt@[email protected]
- fi-skl-guc: NOTRUN -> [FAIL][54] ([i915#4312])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-skl-guc/igt@[email protected]
- bat-dg1-6: NOTRUN -> [FAIL][55] ([i915#4312])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/bat-dg1-6/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [FAIL][56] ([i915#4312])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-rkl-11600/igt@[email protected]
- fi-adl-ddr5: NOTRUN -> [FAIL][57] ([i915#4312])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-adl-ddr5/igt@[email protected]
#### Possible fixes ####
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions:
- fi-bsw-kefka: [FAIL][58] ([i915#6298]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
#### Warnings ####
* igt@runner@aborted:
- fi-kbl-8809g: [FAIL][60] ([i915#4312] / [i915#4991]) -> [FAIL][61] ([fdo#109271] / [i915#4312] / [i915#4991])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12457/fi-kbl-8809g/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/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#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
Build changes
-------------
* Linux: CI_DRM_12457 -> Patchwork_110720v4
CI-20190529: 20190529
CI_DRM_12457: 42273934c8b473fd88e6689a589e9b4050c46bec @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7076: 888725538e0d6bbb94bbbb1ac278d4afcbbbdad0 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_110720v4: 42273934c8b473fd88e6689a589e9b4050c46bec @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
d770dfeeb7b4 Revert "drm/i915: Improve on suspend / resume time with VT-d enabled" 0b1ccc1b9e69 drm/i915: Refine VT-d scanout workaround2a323dee7872 drm/i915: Introduce guard pages to i915_vma7da558d1d002 drm/i915: Wrap all access to i915_vma.node.start|size 1b98e8d440cc drm/i915: Limit the display memory alignment to 32 bit instead of 64
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v4/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for add guard padding around i915_vma (rev5)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev5)
URL : https://patchwork.freedesktop.org/series/110720/
State : warning
== Summary ==
Error: dim checkpatch failed009020c6bd1a drm/i915: Limit the display memory alignment to 32 bit instead of 64724ab32df37d drm/i915: Wrap all access to i915_vma.node.start|size
-:264: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #264: FILE: drivers/gpu/drm/i915/gem/selftests/i915_gem_client_blt.c:475:
+ GEM_BUG_ON(i915_vma_offset(vma) != addr);
-:356: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #356: FILE: drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c:65:
+ GEM_BUG_ON(offset + (count - 1) * PAGE_SIZE > i915_vma_size(vma));
-:393: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #393: FILE: drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c:223:
+ GEM_BUG_ON(vma->fence_size > i915_vma_size(vma));
-:787: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #787: FILE: drivers/gpu/drm/i915/i915_vma.c:450:
+ GEM_BUG_ON(vma->size > i915_vma_size(vma));
-:870: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #870: FILE: drivers/gpu/drm/i915/i915_vma.h:146:
+ GEM_BUG_ON(!drm_mm_node_allocated(&vma->node));
-:892: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #892: FILE: drivers/gpu/drm/i915/i915_vma.h:168:
+ GEM_BUG_ON(!drm_mm_node_allocated(&vma->node));
-:903: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #903: FILE: drivers/gpu/drm/i915/i915_vma.h:176:
+ GEM_BUG_ON(upper_32_bits(i915_vma_offset(vma)));
-:904: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #904: FILE: drivers/gpu/drm/i915/i915_vma.h:177:
+ GEM_BUG_ON(upper_32_bits(i915_vma_offset(vma) +
total: 0 errors, 8 warnings, 0 checks, 805 lines checkeda37e430ffc37 drm/i915: Introduce guard pages to i915_vma
-:119: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #119: FILE: drivers/gpu/drm/i915/i915_vma.c:762:
+ GEM_BUG_ON(hweight64(flags & (PIN_OFFSET_GUARD | PIN_OFFSET_FIXED | PIN_OFFSET_BIAS)) > 1);
-:133: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #133: FILE: drivers/gpu/drm/i915/i915_vma.c:778:
+ GEM_BUG_ON(overflows_type(flags & PIN_OFFSET_MASK, u32));
-:226: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_node' - possible side-effects? #226: FILE: drivers/gpu/drm/i915/i915_vma_resource.c:37:
+#define VMA_RES_START(_node) ((_node)->start - (_node)->guard)
-:227: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_node' - possible side-effects? #227: FILE: drivers/gpu/drm/i915/i915_vma_resource.c:38:
+#define VMA_RES_LAST(_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1)
total: 0 errors, 2 warnings, 2 checks, 205 lines checked3e29ca8fdd75 drm/i915: Refine VT-d scanout workaround7cc593c798e7 Revert "drm/i915: Improve on suspend / resume time with VT-d enabled"
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for add guard padding around i915_vma (rev5)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev5)
URL : https://patchwork.freedesktop.org/series/110720/
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: failure for add guard padding around i915_vma (rev5)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev5)
URL : https://patchwork.freedesktop.org/series/110720/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12459 -> Patchwork_110720v5
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_110720v5 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_110720v5, 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_110720v5/index.html
Participating hosts (41 -> 46)
------------------------------
Additional (6): bat-dg1-6 bat-dg1-5 fi-tgl-dsi bat-atsm-1 bat-rpls-1 bat-rpls-2
Missing (1): fi-ilk-m540
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_110720v5:
### IGT changes ###
#### Possible regressions ####
* igt@i915_module_load@load:
- fi-rkl-11600: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-rkl-11600/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-rkl-11600/igt@[email protected]
- fi-icl-u2: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-icl-u2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-icl-u2/igt@[email protected]
- fi-apl-guc: [PASS][5] -> [INCOMPLETE][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-apl-guc/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-apl-guc/igt@[email protected]
- bat-dg1-5: NOTRUN -> [INCOMPLETE][7]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg1-5/igt@[email protected]
- fi-glk-j4005: [PASS][8] -> [INCOMPLETE][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-glk-j4005/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-glk-j4005/igt@[email protected]
- fi-rkl-guc: [PASS][10] -> [INCOMPLETE][11]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-rkl-guc/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-rkl-guc/igt@[email protected]
- fi-skl-guc: [PASS][12] -> [INCOMPLETE][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-skl-guc/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-skl-guc/igt@[email protected]
- fi-kbl-soraka: [PASS][14] -> [INCOMPLETE][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-kbl-soraka/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-kbl-soraka/igt@[email protected]
- bat-dg1-6: NOTRUN -> [INCOMPLETE][16]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg1-6/igt@[email protected]
- fi-adl-ddr5: [PASS][17] -> [INCOMPLETE][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-adl-ddr5/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-adl-ddr5/igt@[email protected]
- fi-cfl-8109u: [PASS][19] -> [INCOMPLETE][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-cfl-8109u/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-cfl-8109u/igt@[email protected]
- bat-adlp-4: [PASS][21] -> [INCOMPLETE][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-adlp-4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-adlp-4/igt@[email protected]
- fi-ivb-3770: [PASS][23] -> [INCOMPLETE][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-ivb-3770/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-ivb-3770/igt@[email protected]
* igt@kms_force_connector_basic@prune-stale-modes:
- fi-kbl-8809g: [PASS][25] -> [DMESG-WARN][26] +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-kbl-8809g/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-kbl-8809g/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@i915_module_load@load:
- {bat-jsl-1}: [PASS][27] -> [INCOMPLETE][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-jsl-1/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-jsl-1/igt@[email protected]
- {fi-jsl-1}: [PASS][29] -> [INCOMPLETE][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-jsl-1/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-jsl-1/igt@[email protected]
- {bat-adlp-6}: [PASS][31] -> [INCOMPLETE][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-adlp-6/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-adlp-6/igt@[email protected]
- {fi-ehl-2}: [PASS][33] -> [INCOMPLETE][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-ehl-2/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-ehl-2/igt@[email protected]
- {bat-jsl-3}: [PASS][35] -> [INCOMPLETE][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-jsl-3/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-jsl-3/igt@[email protected]
- {bat-dg2-11}: [PASS][37] -> [INCOMPLETE][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-dg2-11/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg2-11/igt@[email protected]
- {bat-adln-1}: [PASS][39] -> [INCOMPLETE][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-adln-1/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-adln-1/igt@[email protected]
- {bat-rplp-1}: [PASS][41] -> [INCOMPLETE][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-rplp-1/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-rplp-1/igt@[email protected]
- {bat-dg2-9}: [PASS][43] -> [INCOMPLETE][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-dg2-9/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg2-9/igt@[email protected]
- {bat-rpls-2}: NOTRUN -> [INCOMPLETE][45]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-rpls-2/igt@[email protected]
* igt@kms_force_connector_basic@force-connector-state:
- {bat-adlm-1}: [PASS][46] -> [DMESG-WARN][47] +2 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-adlm-1/igt@[email protected]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-adlm-1/igt@[email protected]
- {bat-rpls-1}: NOTRUN -> [DMESG-WARN][48] +2 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-rpls-1/igt@[email protected]
- {bat-dg1-7}: [PASS][49] -> [DMESG-WARN][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-dg1-7/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg1-7/igt@[email protected]
- {bat-kbl-2}: [PASS][51] -> [DMESG-WARN][52] +2 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-kbl-2/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-kbl-2/igt@[email protected]
- {bat-dg2-8}: [PASS][53] -> [DMESG-WARN][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/bat-dg2-8/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg2-8/igt@[email protected]
New tests
---------
New tests have been introduced between CI_DRM_12459 and Patchwork_110720v5:
### New IGT tests (1) ###
* igt@kms_frontbuffer_tracking:
- Statuses :
- Exec time: [None] s
Known issues
------------
Here are the changes found in Patchwork_110720v5 that come from known issues:
### CI changes ###
#### Issues hit ####
* boot:
- fi-skl-6700k2: [PASS][55] -> [FAIL][56] ([i915#5032])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-skl-6700k2/boot.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-skl-6700k2/boot.html
### IGT changes ###
#### Issues hit ####
* igt@runner@aborted:
- fi-cfl-8109u: NOTRUN -> [FAIL][57] ([i915#4312])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-cfl-8109u/igt@[email protected]
- fi-ivb-3770: NOTRUN -> [FAIL][58] ([i915#4312])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-ivb-3770/igt@[email protected]
- fi-icl-u2: NOTRUN -> [FAIL][59] ([i915#4312])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-icl-u2/igt@[email protected]
- fi-apl-guc: NOTRUN -> [FAIL][60] ([i915#4312])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-apl-guc/igt@[email protected]
- bat-dg1-5: NOTRUN -> [FAIL][61] ([i915#4312])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg1-5/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [FAIL][62] ([i915#4312])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-glk-j4005/igt@[email protected]
- fi-rkl-guc: NOTRUN -> [FAIL][63] ([i915#4312])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-rkl-guc/igt@[email protected]
- fi-skl-guc: NOTRUN -> [FAIL][64] ([i915#4312])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-skl-guc/igt@[email protected]
- fi-kbl-soraka: NOTRUN -> [FAIL][65] ([i915#4312] / [i915#4991])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-kbl-soraka/igt@[email protected]
- bat-dg1-6: NOTRUN -> [FAIL][66] ([i915#4312])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/bat-dg1-6/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [FAIL][67] ([i915#4312])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-rkl-11600/igt@[email protected]
- fi-adl-ddr5: NOTRUN -> [FAIL][68] ([i915#4312])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/fi-adl-ddr5/igt@[email protected]
#### Warnings ####
* igt@runner@aborted:
- fi-kbl-8809g: [FAIL][69] ([i915#4312] / [i915#4991]) -> [FAIL][70] ([fdo#109271] / [i915#4312] / [i915#4991])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12459/fi-kbl-8809g/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/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
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1836]: https://gitlab.freedesktop.org/drm/intel/issues/1836
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[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#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5032]: https://gitlab.freedesktop.org/drm/intel/issues/5032
[i915#6077]: https://gitlab.freedesktop.org/drm/intel/issues/6077
[i915#6078]: https://gitlab.freedesktop.org/drm/intel/issues/6078
[i915#6093]: https://gitlab.freedesktop.org/drm/intel/issues/6093
[i915#6094]: https://gitlab.freedesktop.org/drm/intel/issues/6094
[i915#6166]: https://gitlab.freedesktop.org/drm/intel/issues/6166
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6856]: https://gitlab.freedesktop.org/drm/intel/issues/6856
[i915#7125]: https://gitlab.freedesktop.org/drm/intel/issues/7125
[i915#7357]: https://gitlab.freedesktop.org/drm/intel/issues/7357
[i915#7456]: https://gitlab.freedesktop.org/drm/intel/issues/7456
[i915#7535]: https://gitlab.freedesktop.org/drm/intel/issues/7535
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
Build changes
-------------
* Linux: CI_DRM_12459 -> Patchwork_110720v5
CI-20190529: 20190529
CI_DRM_12459: 7d2ea1515d919f6e630c7f0f216bc0498322c3aa @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7077: ffe1b3ba95630cb1883e89fffb9e69bf95d31f62 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_110720v5: 7d2ea1515d919f6e630c7f0f216bc0498322c3aa @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
4d50ff77a8d7 Revert "drm/i915: Improve on suspend / resume time with VT-d enabled" dbc6307a79e8 drm/i915: Refine VT-d scanout workarounda72046688622 drm/i915: Introduce guard pages to i915_vma5de56b9a5899 drm/i915: Wrap all access to i915_vma.node.start|size fce44a2d553a drm/i915: Limit the display memory alignment to 32 bit instead of 64
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v5/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for add guard padding around i915_vma (rev6)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev6)
URL : https://patchwork.freedesktop.org/series/110720/
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: failure for add guard padding around i915_vma (rev6)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev6)
URL : https://patchwork.freedesktop.org/series/110720/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12460 -> Patchwork_110720v6
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_110720v6 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_110720v6, 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_110720v6/index.html
Participating hosts (43 -> 42)
------------------------------
Additional (2): fi-tgl-dsi bat-dg1-6
Missing (3): fi-glk-dsi fi-ilk-m540 fi-rkl-11600
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_110720v6:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@guc_multi_lrc:
- fi-kbl-soraka: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12460/fi-kbl-soraka/igt@i915_selftest@live@guc_multi_lrc.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/fi-kbl-soraka/igt@i915_selftest@live@guc_multi_lrc.html
Known issues
------------
Here are the changes found in Patchwork_110720v6 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_mmap@basic:
- bat-dg1-6: NOTRUN -> [SKIP][3] ([i915#4083])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@gem_render_tiled_blits@basic:
- bat-dg1-6: NOTRUN -> [SKIP][4] ([i915#4079]) +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@gem_tiled_fence_blits@basic:
- bat-dg1-6: NOTRUN -> [SKIP][5] ([i915#4077]) +2 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@i915_pm_backlight@basic-brightness:
- bat-dg1-6: NOTRUN -> [SKIP][6] ([i915#7561])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@i915_pm_rps@basic-api:
- bat-dg1-6: NOTRUN -> [SKIP][7] ([i915#6621])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@kms_addfb_basic@basic-y-tiled-legacy:
- bat-dg1-6: NOTRUN -> [SKIP][8] ([i915#4215])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@kms_addfb_basic@tile-pitch-mismatch:
- bat-dg1-6: NOTRUN -> [SKIP][9] ([i915#4212]) +7 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@kms_chamelium@hdmi-crc-fast:
- bat-dg1-6: NOTRUN -> [SKIP][10] ([fdo#111827]) +8 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- bat-dg1-6: NOTRUN -> [SKIP][11] ([i915#4103] / [i915#4213])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@kms_force_connector_basic@force-load-detect:
- bat-dg1-6: NOTRUN -> [SKIP][12] ([fdo#109285])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@kms_psr@sprite_plane_onoff:
- bat-dg1-6: NOTRUN -> [SKIP][13] ([i915#1072] / [i915#4078]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@kms_psr@sprite_plane_onoff.html
* igt@kms_setmode@basic-clone-single-crtc:
- bat-dg1-6: NOTRUN -> [SKIP][14] ([i915#3555])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@prime_vgem@basic-gtt:
- bat-dg1-6: NOTRUN -> [SKIP][15] ([i915#3708] / [i915#4077]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@prime_vgem@basic-userptr:
- bat-dg1-6: NOTRUN -> [SKIP][16] ([i915#3708] / [i915#4873])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
* igt@prime_vgem@basic-write:
- bat-dg1-6: NOTRUN -> [SKIP][17] ([i915#3708]) +3 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-dg1-6/igt@[email protected]
#### Possible fixes ####
* igt@i915_pm_rpm@module-reload:
- {bat-rpls-2}: [WARN][18] ([i915#7346]) -> [PASS][19]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12460/bat-rpls-2/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/bat-rpls-2/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions-varying-size:
- fi-bsw-kefka: [FAIL][20] ([i915#6298]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12460/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions-varying-size.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@varying-size:
- fi-bsw-kefka: [FAIL][22] -> [PASS][23]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12460/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1759]: https://gitlab.freedesktop.org/drm/intel/issues/1759
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[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#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6949]: https://gitlab.freedesktop.org/drm/intel/issues/6949
[i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997
[i915#7058]: https://gitlab.freedesktop.org/drm/intel/issues/7058
[i915#7346]: https://gitlab.freedesktop.org/drm/intel/issues/7346
[i915#7456]: https://gitlab.freedesktop.org/drm/intel/issues/7456
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
Build changes
-------------
* Linux: CI_DRM_12460 -> Patchwork_110720v6
CI-20190529: 20190529
CI_DRM_12460: 0b96883d5e7a2baa9f75d50656e722c61d96c08f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7078: 71bce31c26998d5d53cff3138049261fd6c4fbaf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_110720v6: 0b96883d5e7a2baa9f75d50656e722c61d96c08f @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
84ebc259986c Revert "drm/i915: Improve on suspend / resume time with VT-d enabled" ee65f7a7efd9 drm/i915: Refine VT-d scanout workaround36390d0ee838 drm/i915: Introduce guard pages to i915_vma51b72c41bbe9 drm/i915: Wrap all access to i915_vma.node.start|size 70f437156786 drm/i915: Limit the display memory alignment to 32 bit instead of 64
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v6/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for add guard padding around i915_vma (rev7)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev7)
URL : https://patchwork.freedesktop.org/series/110720/
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.CHECKPATCH: warning for add guard padding around i915_vma (rev7)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev7)
URL : https://patchwork.freedesktop.org/series/110720/
State : warning
== Summary ==
Error: dim checkpatch failedc2fb33553511 drm/i915: Limit the display memory alignment to 32 bit instead of 6433310e629b69 drm/i915: Wrap all access to i915_vma.node.start|size
-:264: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #264: FILE: drivers/gpu/drm/i915/gem/selftests/i915_gem_client_blt.c:475:
+ GEM_BUG_ON(i915_vma_offset(vma) != addr);
-:356: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #356: FILE: drivers/gpu/drm/i915/gem/selftests/igt_gem_utils.c:65:
+ GEM_BUG_ON(offset + (count - 1) * PAGE_SIZE > i915_vma_size(vma));
-:393: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #393: FILE: drivers/gpu/drm/i915/gt/intel_ggtt_fencing.c:223:
+ GEM_BUG_ON(vma->fence_size > i915_vma_size(vma));
-:787: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #787: FILE: drivers/gpu/drm/i915/i915_vma.c:450:
+ GEM_BUG_ON(vma->size > i915_vma_size(vma));
-:870: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #870: FILE: drivers/gpu/drm/i915/i915_vma.h:146:
+ GEM_BUG_ON(!drm_mm_node_allocated(&vma->node));
-:892: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #892: FILE: drivers/gpu/drm/i915/i915_vma.h:168:
+ GEM_BUG_ON(!drm_mm_node_allocated(&vma->node));
-:903: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #903: FILE: drivers/gpu/drm/i915/i915_vma.h:176:
+ GEM_BUG_ON(upper_32_bits(i915_vma_offset(vma)));
-:904: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #904: FILE: drivers/gpu/drm/i915/i915_vma.h:177:
+ GEM_BUG_ON(upper_32_bits(i915_vma_offset(vma) +
total: 0 errors, 8 warnings, 0 checks, 805 lines checked79c9e923c812 drm/i915: Introduce guard pages to i915_vma
-:119: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #119: FILE: drivers/gpu/drm/i915/i915_vma.c:762:
+ GEM_BUG_ON(hweight64(flags & (PIN_OFFSET_GUARD | PIN_OFFSET_FIXED | PIN_OFFSET_BIAS)) > 1);
-:133: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants #133: FILE: drivers/gpu/drm/i915/i915_vma.c:778:
+ GEM_BUG_ON(overflows_type(flags & PIN_OFFSET_MASK, u32));
-:228: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_node' - possible side-effects? #228: FILE: drivers/gpu/drm/i915/i915_vma_resource.c:37:
+#define VMA_RES_START(_node) ((_node)->start - (_node)->guard)
-:229: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_node' - possible side-effects? #229: FILE: drivers/gpu/drm/i915/i915_vma_resource.c:38:
+#define VMA_RES_LAST(_node) ((_node)->start + (_node)->node_size + (_node)->guard - 1)
total: 0 errors, 2 warnings, 2 checks, 207 lines checked64b125b71bc2 drm/i915: Refine VT-d scanout workaroundcaf63d28fa49 Revert "drm/i915: Improve on suspend / resume time with VT-d enabled"
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for add guard padding around i915_vma (rev7)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev7)
URL : https://patchwork.freedesktop.org/series/110720/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12462 -> Patchwork_110720v7
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/index.html
Participating hosts (42 -> 42)
------------------------------
Additional (2): bat-dg1-7 bat-adlp-9
Missing (2): fi-ilk-m540 bat-atsm-1
Known issues
------------
Here are the changes found in Patchwork_110720v7 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@execlists:
- fi-kbl-soraka: [PASS][1] -> [INCOMPLETE][2] ([i915#7156])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/fi-kbl-soraka/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/fi-kbl-soraka/igt@i915_selftest@[email protected]
* igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1:
- fi-bsw-kefka: [PASS][3] -> [FAIL][4] ([i915#2122])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/fi-bsw-kefka/igt@kms_flip@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/fi-bsw-kefka/igt@kms_flip@[email protected]
#### Possible fixes ####
* igt@fbdev@read:
- {bat-rpls-2}: [SKIP][5] ([i915#2582]) -> [PASS][6] +4 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/bat-rpls-2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/bat-rpls-2/igt@[email protected]
* igt@i915_selftest@live@requests:
- {bat-rpls-2}: [INCOMPLETE][7] ([i915#4983] / [i915#6257]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/bat-rpls-2/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/bat-rpls-2/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@slpc:
- {bat-adln-1}: [DMESG-FAIL][9] ([i915#6997]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/bat-adln-1/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/bat-adln-1/igt@i915_selftest@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions:
- fi-bsw-kefka: [FAIL][11] ([i915#6298]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
* igt@kms_psr@primary_page_flip:
- fi-kbl-soraka: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/fi-kbl-soraka/igt@kms_psr@primary_page_flip.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/fi-kbl-soraka/igt@kms_psr@primary_page_flip.html
#### Warnings ####
* igt@i915_module_load@load:
- fi-bsw-n3050: [DMESG-WARN][15] ([i915#7430]) -> [DMESG-WARN][16] ([i915#1982] / [i915#7430])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/fi-bsw-n3050/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/fi-bsw-n3050/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#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[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#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215
[i915#4303]: https://gitlab.freedesktop.org/drm/intel/issues/4303
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#6257]: https://gitlab.freedesktop.org/drm/intel/issues/6257
[i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997
[i915#7156]: https://gitlab.freedesktop.org/drm/intel/issues/7156
[i915#7308]: https://gitlab.freedesktop.org/drm/intel/issues/7308
[i915#7346]: https://gitlab.freedesktop.org/drm/intel/issues/7346
[i915#7348]: https://gitlab.freedesktop.org/drm/intel/issues/7348
[i915#7430]: https://gitlab.freedesktop.org/drm/intel/issues/7430
[i915#7456]: https://gitlab.freedesktop.org/drm/intel/issues/7456
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
Build changes
-------------
* Linux: CI_DRM_12462 -> Patchwork_110720v7
CI-20190529: 20190529
CI_DRM_12462: 00b10bdfd8b9edc9b2c681d806fbb6ae2e5f31a3 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7078: 71bce31c26998d5d53cff3138049261fd6c4fbaf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_110720v7: 00b10bdfd8b9edc9b2c681d806fbb6ae2e5f31a3 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
e8d09c4ea106 Revert "drm/i915: Improve on suspend / resume time with VT-d enabled" 1d741c266397 drm/i915: Refine VT-d scanout workaroundffc6471df620 drm/i915: Introduce guard pages to i915_vmae5fa734d2a07 drm/i915: Wrap all access to i915_vma.node.start|size 6b7423ec0d85 drm/i915: Limit the display memory alignment to 32 bit instead of 64
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for add guard padding around i915_vma (rev7)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: add guard padding around i915_vma (rev7)
URL : https://patchwork.freedesktop.org/series/110720/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12462_full -> Patchwork_110720v7_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_110720v7_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_110720v7_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (13 -> 11)
------------------------------
Missing (2): shard-tglu shard-tglu-10
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_110720v7_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_atomic_transition@modeset-transition-nonblocking-fencing@1x-outputs:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-tglb6/igt@kms_atomic_transition@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb6/igt@kms_atomic_transition@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@v3d/v3d_get_param@get-bad-flags}:
- {shard-dg1}: NOTRUN -> [SKIP][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-dg1-15/igt@v3d/[email protected]
Known issues
------------
Here are the changes found in Patchwork_110720v7_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@display-3x:
- shard-tglb: NOTRUN -> [SKIP][4] ([i915#1839])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
* igt@gem_ctx_exec@basic-nohangcheck:
- shard-tglb: [PASS][5] -> [FAIL][6] ([i915#6268])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-tglb5/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb5/igt@[email protected]
* igt@gem_ctx_persistence@hang:
- shard-skl: NOTRUN -> [SKIP][7] ([fdo#109271]) +39 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl9/igt@[email protected]
* igt@gem_exec_fair@basic-none@bcs0:
- shard-tglb: NOTRUN -> [FAIL][8] ([i915#2842]) +4 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@gem_exec_fair@[email protected]
* igt@gem_pxp@protected-raw-src-copy-not-readible:
- shard-tglb: NOTRUN -> [SKIP][9] ([i915#4270])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
* igt@gen3_render_linear_blits:
- shard-tglb: NOTRUN -> [SKIP][10] ([fdo#109289])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@gen3_render_linear_blits.html
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [PASS][11] -> [DMESG-WARN][12] ([i915#5566] / [i915#716])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl9/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl7/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([i915#5566] / [i915#716])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-apl3/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-apl7/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- shard-skl: NOTRUN -> [WARN][15] ([i915#1804])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl6/igt@i915_pm_rc6_residency@[email protected]
* igt@i915_query@query-topology-known-pci-ids:
- shard-tglb: NOTRUN -> [SKIP][16] ([fdo#109303])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
* igt@i915_selftest@live@gt_pm:
- shard-tglb: NOTRUN -> [DMESG-FAIL][17] ([i915#1759])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@i915_selftest@live@gt_pm.html
* igt@kms_big_fb@4-tiled-32bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][18] ([i915#5286]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-tglb: NOTRUN -> [SKIP][19] ([fdo#111615])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
* igt@kms_ccs@pipe-a-bad-pixel-format-4_tiled_dg2_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][20] ([i915#6095]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_ccs@pipe-a-bad-pixel-format-4_tiled_dg2_mc_ccs.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][21] ([fdo#109271] / [i915#3886]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl6/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-bad-rotation-90-4_tiled_dg2_rc_ccs:
- shard-tglb: NOTRUN -> [SKIP][22] ([i915#3689] / [i915#6095])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_ccs@pipe-c-bad-rotation-90-4_tiled_dg2_rc_ccs.html
* igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][23] ([i915#3689] / [i915#3886])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-d-ccs-on-another-bo-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][24] ([fdo#111615] / [i915#3689])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_ccs@pipe-d-ccs-on-another-bo-yf_tiled_ccs.html
* igt@kms_ccs@pipe-d-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][25] ([i915#3689])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_ccs@pipe-d-crc-primary-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_chamelium@dp-crc-multiple:
- shard-tglb: NOTRUN -> [SKIP][26] ([fdo#109284] / [fdo#111827]) +2 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
* igt@kms_color_chamelium@ctm-0-50:
- shard-skl: NOTRUN -> [SKIP][27] ([fdo#109271] / [fdo#111827]) +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl6/igt@[email protected]
* igt@kms_flip@2x-flip-vs-absolute-wf_vblank:
- shard-tglb: NOTRUN -> [SKIP][28] ([fdo#109274] / [fdo#111825] / [i915#3637]) +3 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_flip@2x-flip-vs-absolute-wf_vblank.html
* igt@kms_flip@plain-flip-fb-recreate@c-edp1:
- shard-skl: [PASS][29] -> [FAIL][30] ([i915#2122]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl1/igt@kms_flip@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-upscaling@pipe-a-valid-mode:
- shard-tglb: NOTRUN -> [SKIP][31] ([i915#2587] / [i915#2672])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-upscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][32] ([i915#2587] / [i915#2672]) +3 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb6/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][33] ([i915#2672]) +4 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-16bpp-xtile-downscaling@pipe-a-default-mode:
- shard-iclb: [PASS][34] -> [SKIP][35] ([i915#3555]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb3/igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-16bpp-xtile-downscaling@pipe-a-default-mode.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-16bpp-xtile-downscaling@pipe-a-default-mode.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render:
- shard-tglb: NOTRUN -> [SKIP][36] ([i915#6497]) +3 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-onoff:
- shard-tglb: NOTRUN -> [SKIP][37] ([fdo#109280] / [fdo#111825]) +8 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-rgb565-draw-render:
- shard-skl: [PASS][38] -> [DMESG-WARN][39] ([i915#1982]) +2 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl7/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl1/igt@[email protected]
* igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-5@pipe-b-edp-1:
- shard-iclb: [PASS][40] -> [SKIP][41] ([i915#5176]) +2 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb6/igt@kms_plane_scaling@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb2/igt@kms_plane_scaling@[email protected]
* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf:
- shard-skl: NOTRUN -> [SKIP][42] ([fdo#109271] / [i915#658])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl6/igt@[email protected]
* igt@kms_psr2_su@page_flip-nv12:
- shard-iclb: NOTRUN -> [SKIP][43] ([fdo#109642] / [fdo#111068] / [i915#658])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb6/igt@kms_psr2_su@page_flip-nv12.html
* igt@kms_psr@psr2_primary_blt:
- shard-tglb: NOTRUN -> [FAIL][44] ([i915#132] / [i915#3467])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@kms_psr@psr2_primary_blt.html
* igt@kms_psr@psr2_sprite_blt:
- shard-iclb: [PASS][45] -> [SKIP][46] ([fdo#109441]) +4 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb2/igt@kms_psr@psr2_sprite_blt.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb6/igt@kms_psr@psr2_sprite_blt.html
* igt@kms_psr_stress_test@invalidate-primary-flip-overlay:
- shard-tglb: [PASS][47] -> [SKIP][48] ([i915#5519])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-tglb5/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb5/igt@[email protected]
* igt@kms_writeback@writeback-check-output:
- shard-skl: NOTRUN -> [SKIP][49] ([fdo#109271] / [i915#2437])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl6/igt@[email protected]
* igt@perf_pmu@interrupts:
- shard-skl: [PASS][50] -> [FAIL][51] ([i915#7318])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl7/igt@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl1/igt@[email protected]
* igt@sysfs_clients@recycle-many:
- shard-tglb: NOTRUN -> [SKIP][52] ([i915#2994])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb7/igt@[email protected]
#### Possible fixes ####
* igt@drm_read@short-buffer-nonblock:
- {shard-rkl}: [SKIP][53] ([i915#4098]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@[email protected]
* igt@fbdev@nullptr:
- shard-skl: [DMESG-WARN][55] ([i915#1982]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl6/igt@[email protected]
* igt@fbdev@pan:
- {shard-rkl}: [SKIP][57] ([i915#2582]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@[email protected]
* igt@feature_discovery@psr1:
- {shard-rkl}: [SKIP][59] ([i915#658]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-2/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@[email protected]
* igt@gem_exec_balancer@parallel-contexts:
- shard-iclb: [SKIP][61] ([i915#4525]) -> [PASS][62] +1 similar issue
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb5/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb1/igt@[email protected]
* igt@gem_exec_endless@dispatch@bcs0:
- {shard-rkl}: [SKIP][63] ([i915#6247]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-5/igt@gem_exec_endless@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-1/igt@gem_exec_endless@[email protected]
* igt@gem_exec_fair@basic-deadline:
- {shard-rkl}: [FAIL][65] ([i915#2846]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-4/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-3/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [FAIL][67] ([i915#2842]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-tglb3/igt@gem_exec_fair@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_reloc@basic-cpu-read-noreloc:
- {shard-rkl}: [SKIP][69] ([i915#3281]) -> [PASS][70] +3 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-5/igt@[email protected]
* igt@gem_userptr_blits@forbidden-operations:
- {shard-rkl}: [SKIP][71] ([i915#3282]) -> [PASS][72] +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-5/igt@[email protected]
* igt@gen9_exec_parse@batch-without-end:
- {shard-rkl}: [SKIP][73] ([i915#2527]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-5/igt@[email protected]
* igt@i915_pm_rpm@pm-tiling:
- {shard-rkl}: [SKIP][75] ([fdo#109308]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@[email protected]
* igt@i915_suspend@forcewake:
- shard-skl: [INCOMPLETE][77] ([i915#4817] / [i915#7233]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl10/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl6/igt@[email protected]
* igt@kms_atomic@plane-overlay-legacy:
- {shard-rkl}: [SKIP][79] ([i915#1845] / [i915#4098]) -> [PASS][80] +17 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@b-edp1:
- shard-skl: [FAIL][81] ([i915#79]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl10/igt@kms_flip@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
- shard-skl: [FAIL][83] ([i915#2122]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl10/igt@kms_flip@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl1/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-stridechange:
- {shard-rkl}: [SKIP][85] ([i915#1849] / [i915#4098]) -> [PASS][86] +11 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-2/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@[email protected]
* igt@kms_plane@pixel-format@pipe-b-planes:
- {shard-rkl}: [SKIP][87] ([i915#3558]) -> [PASS][88] +1 similar issue
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-1/igt@kms_plane@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@kms_plane@[email protected]
* igt@kms_plane@plane-position-covered@pipe-a-planes:
- {shard-rkl}: [SKIP][89] ([i915#1849] / [i915#3558]) -> [PASS][90] +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-2/igt@kms_plane@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@kms_plane@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [SKIP][91] ([fdo#109441]) -> [PASS][92] +2 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb3/igt@kms_psr@psr2_no_drrs.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
* igt@kms_psr@sprite_mmap_gtt:
- {shard-rkl}: [SKIP][93] ([i915#1072]) -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-2/igt@kms_psr@sprite_mmap_gtt.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@kms_psr@sprite_mmap_gtt.html
* igt@kms_sequence@queue-busy@edp-1-pipe-b:
- shard-skl: [FAIL][95] ([i915#7413]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl7/igt@kms_sequence@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl7/igt@kms_sequence@[email protected]
* igt@kms_universal_plane@universal-plane-pipe-b-functional:
- {shard-rkl}: [SKIP][97] ([i915#1845] / [i915#4070] / [i915#4098]) -> [PASS][98] +1 similar issue
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-rkl-2/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-rkl-6/igt@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- shard-skl: [INCOMPLETE][99] ([i915#7404]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-skl10/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-skl9/igt@[email protected]
#### Warnings ####
* igt@gem_exec_balancer@parallel-ordering:
- shard-iclb: [SKIP][101] ([i915#4525]) -> [FAIL][102] ([i915#6117])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb7/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb2/igt@[email protected]
* igt@gem_pread@exhaustion:
- shard-apl: [INCOMPLETE][103] ([i915#7248]) -> [WARN][104] ([i915#2658])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-apl6/igt@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-apl3/igt@[email protected]
* igt@gem_pwrite@basic-exhaustion:
- shard-tglb: [INCOMPLETE][105] ([i915#7248]) -> [WARN][106] ([i915#2658])
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-tglb7/igt@[email protected]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-tglb5/igt@[email protected]
* igt@kms_plane_alpha_blend@alpha-basic@pipe-c-dp-1:
- shard-apl: [FAIL][107] ([i915#4573]) -> [DMESG-FAIL][108] ([IGT#6]) +1 similar issue
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-apl6/igt@kms_plane_alpha_blend@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-apl2/igt@kms_plane_alpha_blend@[email protected]
* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf:
- shard-iclb: [SKIP][109] ([i915#2920]) -> [SKIP][110] ([i915#658])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb2/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb8/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][111] ([fdo#111068] / [i915#658]) -> [SKIP][112] ([i915#2920])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-iclb7/igt@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-iclb2/igt@[email protected]
* igt@runner@aborted:
- shard-apl: ([FAIL][113], [FAIL][114]) ([i915#3002] / [i915#4312]) -> ([FAIL][115], [FAIL][116], [FAIL][117]) ([fdo#109271] / [i915#3002] / [i915#4312])
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-apl1/igt@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12462/shard-apl6/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-apl7/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-apl7/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/shard-apl6/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109303]: https://bugs.freedesktop.org/show_bug.cgi?id=109303
[fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1759]: https://gitlab.freedesktop.org/drm/intel/issues/1759
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2435]: https://gitlab.freedesktop.org/drm/intel/issues/2435
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2705]: https://gitlab.freedesktop.org/drm/intel/issues/2705
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3361]: https://gitlab.freedesktop.org/drm/intel/issues/3361
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3467]: https://gitlab.freedesktop.org/drm/intel/issues/3467
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3952]: https://gitlab.freedesktop.org/drm/intel/issues/3952
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4817]: https://gitlab.freedesktop.org/drm/intel/issues/4817
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4859]: https://gitlab.freedesktop.org/drm/intel/issues/4859
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5519]: https://gitlab.freedesktop.org/drm/intel/issues/5519
[i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6230]: https://gitlab.freedesktop.org/drm/intel/issues/6230
[i915#6247]: https://gitlab.freedesktop.org/drm/intel/issues/6247
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6433]: https://gitlab.freedesktop.org/drm/intel/issues/6433
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#6524]: https://gitlab.freedesktop.org/drm/intel/issues/6524
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6946]: https://gitlab.freedesktop.org/drm/intel/issues/6946
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#7233]: https://gitlab.freedesktop.org/drm/intel/issues/7233
[i915#7248]: https://gitlab.freedesktop.org/drm/intel/issues/7248
[i915#7276]: https://gitlab.freedesktop.org/drm/intel/issues/7276
[i915#7318]: https://gitlab.freedesktop.org/drm/intel/issues/7318
[i915#7404]: https://gitlab.freedesktop.org/drm/intel/issues/7404
[i915#7413]: https://gitlab.freedesktop.org/drm/intel/issues/7413
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_12462 -> Patchwork_110720v7
CI-20190529: 20190529
CI_DRM_12462: 00b10bdfd8b9edc9b2c681d806fbb6ae2e5f31a3 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7078: 71bce31c26998d5d53cff3138049261fd6c4fbaf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_110720v7: 00b10bdfd8b9edc9b2c681d806fbb6ae2e5f31a3 @ 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_110720v7/index.html
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for add guard padding around i915_vma (rev7)
Quoted 31 lines · Patchwork
Patch Details
Series: add guard padding around i915_vma (rev7) URL: https://patchwork.freedesktop.org/series/110720/ State: failure Details: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110720v7/index.htmlCI Bug Log - changes from
CI_DRM_12462_full->Patchwork_110720v7_fullSummary
FAILURE
Serious unknown changes coming with
Patchwork_110720v7_fullabsolutely need to be
verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_110720v7_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.Participating hosts (13 -> 11)
Missing (2): shard-tglu shard-tglu-10
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_110720v7_full:
Quoted 6 lines
IGT changes
Possible regressions
• igt@kms_atomic_transition@modeset-transition-nonblocking-fencing@1x-outputs:
□ shard-tglb: PASS -> INCOMPLETE
This looks unrelated