* [PATCH 0/4] Flat-CCS eviction enhancements @ 2022-04-21 11:38 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Flat-CCS eviction enhancements. Ramalingam C (4): drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking drm/i915/gt: optimize the ccs_sz calculation per chunk drm/i915/gt: Extend doc on Flat-CCS obj eviction uapi/drm/i915: Update the placement list impact on obj residency drivers/gpu/drm/i915/gt/intel_migrate.c | 78 ++++++++++++++----------- include/uapi/drm/i915_drm.h | 14 +++++ 2 files changed, 59 insertions(+), 33 deletions(-) -- 2.20.1 ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Intel-gfx] [PATCH 0/4] Flat-CCS eviction enhancements @ 2022-04-21 11:38 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Flat-CCS eviction enhancements. Ramalingam C (4): drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking drm/i915/gt: optimize the ccs_sz calculation per chunk drm/i915/gt: Extend doc on Flat-CCS obj eviction uapi/drm/i915: Update the placement list impact on obj residency drivers/gpu/drm/i915/gt/intel_migrate.c | 78 ++++++++++++++----------- include/uapi/drm/i915_drm.h | 14 +++++ 2 files changed, 59 insertions(+), 33 deletions(-) -- 2.20.1 ^ permalink raw reply [flat|nested] 24+ messages in thread
* [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C @ 2022-04-21 11:38 ` Ramalingam C -1 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld While locating the start of ccs scatterlist in smem scatterlist, that has to be the size of lmem obj size + corresponding ccs data size. Report bug if scatterlist terminate before that length. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- drivers/gpu/drm/i915/gt/intel_migrate.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c index 9d552f30b627..29d761da02c4 100644 --- a/drivers/gpu/drm/i915/gt/intel_migrate.c +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c @@ -687,6 +687,12 @@ static void get_ccs_sg_sgt(struct sgt_dma *it, u32 bytes_to_cpy) bytes_to_cpy -= len; it->sg = __sg_next(it->sg); + + /* + * scatterlist supposed to be the size of + * bytes_to_cpy + GET_CCS_BYTES(bytes_to_copy). + */ + GEM_BUG_ON(!it->sg); it->dma = sg_dma_address(it->sg); it->max = it->dma + sg_dma_len(it->sg); } while (bytes_to_cpy); -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* [Intel-gfx] [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking @ 2022-04-21 11:38 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld While locating the start of ccs scatterlist in smem scatterlist, that has to be the size of lmem obj size + corresponding ccs data size. Report bug if scatterlist terminate before that length. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- drivers/gpu/drm/i915/gt/intel_migrate.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c index 9d552f30b627..29d761da02c4 100644 --- a/drivers/gpu/drm/i915/gt/intel_migrate.c +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c @@ -687,6 +687,12 @@ static void get_ccs_sg_sgt(struct sgt_dma *it, u32 bytes_to_cpy) bytes_to_cpy -= len; it->sg = __sg_next(it->sg); + + /* + * scatterlist supposed to be the size of + * bytes_to_cpy + GET_CCS_BYTES(bytes_to_copy). + */ + GEM_BUG_ON(!it->sg); it->dma = sg_dma_address(it->sg); it->max = it->dma + sg_dma_len(it->sg); } while (bytes_to_cpy); -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* Re: [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C @ 2022-04-21 13:27 ` Hellstrom, Thomas -1 siblings, 0 replies; 24+ messages in thread From: Hellstrom, Thomas @ 2022-04-21 13:27 UTC (permalink / raw) To: dri-devel, C, Ramalingam, intel-gfx; +Cc: Auld, Matthew On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > While locating the start of ccs scatterlist in smem scatterlist, that > has > to be the size of lmem obj size + corresponding ccs data size. Report > bug > if scatterlist terminate before that length. > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > --- > drivers/gpu/drm/i915/gt/intel_migrate.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > b/drivers/gpu/drm/i915/gt/intel_migrate.c > index 9d552f30b627..29d761da02c4 100644 > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > @@ -687,6 +687,12 @@ static void get_ccs_sg_sgt(struct sgt_dma *it, > u32 bytes_to_cpy) > bytes_to_cpy -= len; > > it->sg = __sg_next(it->sg); If bytes_to_cpy == 0 here, couldn't it->sg be NULL then? > + > + /* > + * scatterlist supposed to be the size of > + * bytes_to_cpy + GET_CCS_BYTES(bytes_to_copy). > + */ > + GEM_BUG_ON(!it->sg); > it->dma = sg_dma_address(it->sg); > it->max = it->dma + sg_dma_len(it->sg); > } while (bytes_to_cpy); /Thomas ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Intel-gfx] [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking @ 2022-04-21 13:27 ` Hellstrom, Thomas 0 siblings, 0 replies; 24+ messages in thread From: Hellstrom, Thomas @ 2022-04-21 13:27 UTC (permalink / raw) To: dri-devel, C, Ramalingam, intel-gfx; +Cc: Auld, Matthew On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > While locating the start of ccs scatterlist in smem scatterlist, that > has > to be the size of lmem obj size + corresponding ccs data size. Report > bug > if scatterlist terminate before that length. > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > --- > drivers/gpu/drm/i915/gt/intel_migrate.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > b/drivers/gpu/drm/i915/gt/intel_migrate.c > index 9d552f30b627..29d761da02c4 100644 > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > @@ -687,6 +687,12 @@ static void get_ccs_sg_sgt(struct sgt_dma *it, > u32 bytes_to_cpy) > bytes_to_cpy -= len; > > it->sg = __sg_next(it->sg); If bytes_to_cpy == 0 here, couldn't it->sg be NULL then? > + > + /* > + * scatterlist supposed to be the size of > + * bytes_to_cpy + GET_CCS_BYTES(bytes_to_copy). > + */ > + GEM_BUG_ON(!it->sg); > it->dma = sg_dma_address(it->sg); > it->max = it->dma + sg_dma_len(it->sg); > } while (bytes_to_cpy); /Thomas ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking 2022-04-21 13:27 ` [Intel-gfx] " Hellstrom, Thomas @ 2022-04-21 14:04 ` Ramalingam C -1 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 14:04 UTC (permalink / raw) To: Hellstrom, Thomas; +Cc: intel-gfx, Auld, Matthew, dri-devel On 2022-04-21 at 18:57:59 +0530, Hellstrom, Thomas wrote: > On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > > While locating the start of ccs scatterlist in smem scatterlist, that > > has > > to be the size of lmem obj size + corresponding ccs data size. Report > > bug > > if scatterlist terminate before that length. > > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > > --- > > drivers/gpu/drm/i915/gt/intel_migrate.c | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > > b/drivers/gpu/drm/i915/gt/intel_migrate.c > > index 9d552f30b627..29d761da02c4 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > > @@ -687,6 +687,12 @@ static void get_ccs_sg_sgt(struct sgt_dma *it, > > u32 bytes_to_cpy) > > bytes_to_cpy -= len; > > > > > > it->sg = __sg_next(it->sg); > > If bytes_to_cpy == 0 here, couldn't it->sg be NULL then? Hi, bytes_to_cpy is the lmem size and the scatterlist is the length of bytes_to_cpy + GET_CCS_BYTES(bytes_to_cpy). So this should not be null. when bytes_to_cpy reduces to zero we will be having the start of the scatterlist for ccs. Ram. > > > + > > + /* > > + * scatterlist supposed to be the size of > > + * bytes_to_cpy + GET_CCS_BYTES(bytes_to_copy). > > + */ > > + GEM_BUG_ON(!it->sg); > > it->dma = sg_dma_address(it->sg); > > it->max = it->dma + sg_dma_len(it->sg); > > } while (bytes_to_cpy); > > /Thomas > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Intel-gfx] [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking @ 2022-04-21 14:04 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 14:04 UTC (permalink / raw) To: Hellstrom, Thomas; +Cc: intel-gfx, Auld, Matthew, dri-devel On 2022-04-21 at 18:57:59 +0530, Hellstrom, Thomas wrote: > On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > > While locating the start of ccs scatterlist in smem scatterlist, that > > has > > to be the size of lmem obj size + corresponding ccs data size. Report > > bug > > if scatterlist terminate before that length. > > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > > --- > > drivers/gpu/drm/i915/gt/intel_migrate.c | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > > b/drivers/gpu/drm/i915/gt/intel_migrate.c > > index 9d552f30b627..29d761da02c4 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > > @@ -687,6 +687,12 @@ static void get_ccs_sg_sgt(struct sgt_dma *it, > > u32 bytes_to_cpy) > > bytes_to_cpy -= len; > > > > > > it->sg = __sg_next(it->sg); > > If bytes_to_cpy == 0 here, couldn't it->sg be NULL then? Hi, bytes_to_cpy is the lmem size and the scatterlist is the length of bytes_to_cpy + GET_CCS_BYTES(bytes_to_cpy). So this should not be null. when bytes_to_cpy reduces to zero we will be having the start of the scatterlist for ccs. Ram. > > > + > > + /* > > + * scatterlist supposed to be the size of > > + * bytes_to_cpy + GET_CCS_BYTES(bytes_to_copy). > > + */ > > + GEM_BUG_ON(!it->sg); > > it->dma = sg_dma_address(it->sg); > > it->max = it->dma + sg_dma_len(it->sg); > > } while (bytes_to_cpy); > > /Thomas > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Intel-gfx] [PATCH 2/4] drm/i915/gt: optimize the ccs_sz calculation per chunk 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C @ 2022-04-21 11:38 ` Ramalingam C -1 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Calculate the ccs_sz that needs to be emitted based on the src and dst pages emitted per chunk. And handle the return value of emit_pte for the ccs pages. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- drivers/gpu/drm/i915/gt/intel_migrate.c | 36 +++++++++---------------- 1 file changed, 12 insertions(+), 24 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c index 29d761da02c4..463a6a14b5f9 100644 --- a/drivers/gpu/drm/i915/gt/intel_migrate.c +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c @@ -647,17 +647,9 @@ static int scatter_list_length(struct scatterlist *sg) static void calculate_chunk_sz(struct drm_i915_private *i915, bool src_is_lmem, - int *src_sz, int *ccs_sz, u32 bytes_to_cpy, - u32 ccs_bytes_to_cpy) + int *src_sz, u32 bytes_to_cpy, u32 ccs_bytes_to_cpy) { if (ccs_bytes_to_cpy) { - /* - * We can only copy the ccs data corresponding to - * the CHUNK_SZ of lmem which is - * GET_CCS_BYTES(i915, CHUNK_SZ)) - */ - *ccs_sz = min_t(int, ccs_bytes_to_cpy, GET_CCS_BYTES(i915, CHUNK_SZ)); - if (!src_is_lmem) /* * When CHUNK_SZ is passed all the pages upto CHUNK_SZ @@ -713,10 +705,10 @@ intel_context_migrate_copy(struct intel_context *ce, struct drm_i915_private *i915 = ce->engine->i915; u32 ccs_bytes_to_cpy = 0, bytes_to_cpy; enum i915_cache_level ccs_cache_level; - int src_sz, dst_sz, ccs_sz; u32 src_offset, dst_offset; u8 src_access, dst_access; struct i915_request *rq; + int src_sz, dst_sz; bool ccs_is_src; int err; @@ -770,7 +762,7 @@ intel_context_migrate_copy(struct intel_context *ce, } do { - int len; + int len, ccs_sz; rq = i915_request_create(ce); if (IS_ERR(rq)) { @@ -797,7 +789,7 @@ intel_context_migrate_copy(struct intel_context *ce, if (err) goto out_rq; - calculate_chunk_sz(i915, src_is_lmem, &src_sz, &ccs_sz, + calculate_chunk_sz(i915, src_is_lmem, &src_sz, bytes_to_cpy, ccs_bytes_to_cpy); len = emit_pte(rq, &it_src, src_cache_level, src_is_lmem, @@ -835,33 +827,29 @@ intel_context_migrate_copy(struct intel_context *ce, if (err) goto out_rq; + ccs_sz = GET_CCS_BYTES(i915, len); err = emit_pte(rq, &it_ccs, ccs_cache_level, false, ccs_is_src ? src_offset : dst_offset, ccs_sz); + if (err < 0) + goto out_rq; + if (err < ccs_sz) { + err = -EINVAL; + goto out_rq; + } err = rq->engine->emit_flush(rq, EMIT_INVALIDATE); if (err) goto out_rq; - /* - * Using max of src_sz and dst_sz, as we need to - * pass the lmem size corresponding to the ccs - * blocks we need to handle. - */ - ccs_sz = max_t(int, ccs_is_src ? ccs_sz : src_sz, - ccs_is_src ? dst_sz : ccs_sz); - err = emit_copy_ccs(rq, dst_offset, dst_access, - src_offset, src_access, ccs_sz); + src_offset, src_access, len); if (err) goto out_rq; err = rq->engine->emit_flush(rq, EMIT_INVALIDATE); if (err) goto out_rq; - - /* Converting back to ccs bytes */ - ccs_sz = GET_CCS_BYTES(rq->engine->i915, ccs_sz); ccs_bytes_to_cpy -= ccs_sz; } -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* [PATCH 2/4] drm/i915/gt: optimize the ccs_sz calculation per chunk @ 2022-04-21 11:38 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Calculate the ccs_sz that needs to be emitted based on the src and dst pages emitted per chunk. And handle the return value of emit_pte for the ccs pages. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- drivers/gpu/drm/i915/gt/intel_migrate.c | 36 +++++++++---------------- 1 file changed, 12 insertions(+), 24 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c index 29d761da02c4..463a6a14b5f9 100644 --- a/drivers/gpu/drm/i915/gt/intel_migrate.c +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c @@ -647,17 +647,9 @@ static int scatter_list_length(struct scatterlist *sg) static void calculate_chunk_sz(struct drm_i915_private *i915, bool src_is_lmem, - int *src_sz, int *ccs_sz, u32 bytes_to_cpy, - u32 ccs_bytes_to_cpy) + int *src_sz, u32 bytes_to_cpy, u32 ccs_bytes_to_cpy) { if (ccs_bytes_to_cpy) { - /* - * We can only copy the ccs data corresponding to - * the CHUNK_SZ of lmem which is - * GET_CCS_BYTES(i915, CHUNK_SZ)) - */ - *ccs_sz = min_t(int, ccs_bytes_to_cpy, GET_CCS_BYTES(i915, CHUNK_SZ)); - if (!src_is_lmem) /* * When CHUNK_SZ is passed all the pages upto CHUNK_SZ @@ -713,10 +705,10 @@ intel_context_migrate_copy(struct intel_context *ce, struct drm_i915_private *i915 = ce->engine->i915; u32 ccs_bytes_to_cpy = 0, bytes_to_cpy; enum i915_cache_level ccs_cache_level; - int src_sz, dst_sz, ccs_sz; u32 src_offset, dst_offset; u8 src_access, dst_access; struct i915_request *rq; + int src_sz, dst_sz; bool ccs_is_src; int err; @@ -770,7 +762,7 @@ intel_context_migrate_copy(struct intel_context *ce, } do { - int len; + int len, ccs_sz; rq = i915_request_create(ce); if (IS_ERR(rq)) { @@ -797,7 +789,7 @@ intel_context_migrate_copy(struct intel_context *ce, if (err) goto out_rq; - calculate_chunk_sz(i915, src_is_lmem, &src_sz, &ccs_sz, + calculate_chunk_sz(i915, src_is_lmem, &src_sz, bytes_to_cpy, ccs_bytes_to_cpy); len = emit_pte(rq, &it_src, src_cache_level, src_is_lmem, @@ -835,33 +827,29 @@ intel_context_migrate_copy(struct intel_context *ce, if (err) goto out_rq; + ccs_sz = GET_CCS_BYTES(i915, len); err = emit_pte(rq, &it_ccs, ccs_cache_level, false, ccs_is_src ? src_offset : dst_offset, ccs_sz); + if (err < 0) + goto out_rq; + if (err < ccs_sz) { + err = -EINVAL; + goto out_rq; + } err = rq->engine->emit_flush(rq, EMIT_INVALIDATE); if (err) goto out_rq; - /* - * Using max of src_sz and dst_sz, as we need to - * pass the lmem size corresponding to the ccs - * blocks we need to handle. - */ - ccs_sz = max_t(int, ccs_is_src ? ccs_sz : src_sz, - ccs_is_src ? dst_sz : ccs_sz); - err = emit_copy_ccs(rq, dst_offset, dst_access, - src_offset, src_access, ccs_sz); + src_offset, src_access, len); if (err) goto out_rq; err = rq->engine->emit_flush(rq, EMIT_INVALIDATE); if (err) goto out_rq; - - /* Converting back to ccs bytes */ - ccs_sz = GET_CCS_BYTES(rq->engine->i915, ccs_sz); ccs_bytes_to_cpy -= ccs_sz; } -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* [Intel-gfx] [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C @ 2022-04-21 11:38 ` Ramalingam C -1 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Capture the eviction details for Flat-CCS capable lmem only objects and lmem objects with smem residency. This also captures the impact of eviction on object's memory residency and Flat-CCS compression state. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- drivers/gpu/drm/i915/gt/intel_migrate.c | 36 ++++++++++++++++++------- 1 file changed, 27 insertions(+), 9 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c index 463a6a14b5f9..9d0d18950e76 100644 --- a/drivers/gpu/drm/i915/gt/intel_migrate.c +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c @@ -485,16 +485,34 @@ static bool wa_1209644611_applies(int ver, u32 size) * And CCS data can be copied in and out of CCS region through * XY_CTRL_SURF_COPY_BLT. CPU can't access the CCS data directly. * - * When we exhaust the lmem, if the object's placements support smem, then we can - * directly decompress the compressed lmem object into smem and start using it - * from smem itself. + * when we exhaust the lmem, we need to handle two types of flat-ccs capable + * objects for its eviction. + * 1) lmem only objects + * 2) lmem objects with smem residency option * - * But when we need to swapout the compressed lmem object into a smem region - * though objects' placement doesn't support smem, then we copy the lmem content - * as it is into smem region along with ccs data (using XY_CTRL_SURF_COPY_BLT). - * When the object is referred, lmem content will be swaped in along with - * restoration of the CCS data (using XY_CTRL_SURF_COPY_BLT) at corresponding - * location. + * 1) lmem only objects: + * + * lmem backing memory can be temporarily evicted to smem, along with the + * auxiliary CCS state, where it can be potentially swapped-out at a later point, + * if required. If userspace later touches the evicted pages, then we always move + * the backing memory back to lmem, which includes restoring the saved CCS state, + * and potentially performing any required swap-in. + * + * In this scenario, objects' backing memory class and Flat-CCS state doesn't + * change. + * + * 2) lmem objects with smem residency option + * + * Lmem object with smem region in it's placement list, will be migrated into + * smem by decompressing the content. I915 doesn't handle this kind of + * migration for Flat-CCS compressed objects yet. + * + * In this scenario, objects' backing memory class and Flat-CCS state changed, + * and userspace is not aware of it. + * + * In summary, when a userspace wants to be sure about the objects memory + * residency and flat-ccs compression state, then placement list can't have + * the lmem and smem together. Instead, object has to be lmem resident only. */ static inline u32 *i915_flush_dw(u32 *cmd, u32 flags) -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction @ 2022-04-21 11:38 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Capture the eviction details for Flat-CCS capable lmem only objects and lmem objects with smem residency. This also captures the impact of eviction on object's memory residency and Flat-CCS compression state. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- drivers/gpu/drm/i915/gt/intel_migrate.c | 36 ++++++++++++++++++------- 1 file changed, 27 insertions(+), 9 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c index 463a6a14b5f9..9d0d18950e76 100644 --- a/drivers/gpu/drm/i915/gt/intel_migrate.c +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c @@ -485,16 +485,34 @@ static bool wa_1209644611_applies(int ver, u32 size) * And CCS data can be copied in and out of CCS region through * XY_CTRL_SURF_COPY_BLT. CPU can't access the CCS data directly. * - * When we exhaust the lmem, if the object's placements support smem, then we can - * directly decompress the compressed lmem object into smem and start using it - * from smem itself. + * when we exhaust the lmem, we need to handle two types of flat-ccs capable + * objects for its eviction. + * 1) lmem only objects + * 2) lmem objects with smem residency option * - * But when we need to swapout the compressed lmem object into a smem region - * though objects' placement doesn't support smem, then we copy the lmem content - * as it is into smem region along with ccs data (using XY_CTRL_SURF_COPY_BLT). - * When the object is referred, lmem content will be swaped in along with - * restoration of the CCS data (using XY_CTRL_SURF_COPY_BLT) at corresponding - * location. + * 1) lmem only objects: + * + * lmem backing memory can be temporarily evicted to smem, along with the + * auxiliary CCS state, where it can be potentially swapped-out at a later point, + * if required. If userspace later touches the evicted pages, then we always move + * the backing memory back to lmem, which includes restoring the saved CCS state, + * and potentially performing any required swap-in. + * + * In this scenario, objects' backing memory class and Flat-CCS state doesn't + * change. + * + * 2) lmem objects with smem residency option + * + * Lmem object with smem region in it's placement list, will be migrated into + * smem by decompressing the content. I915 doesn't handle this kind of + * migration for Flat-CCS compressed objects yet. + * + * In this scenario, objects' backing memory class and Flat-CCS state changed, + * and userspace is not aware of it. + * + * In summary, when a userspace wants to be sure about the objects memory + * residency and flat-ccs compression state, then placement list can't have + * the lmem and smem together. Instead, object has to be lmem resident only. */ static inline u32 *i915_flush_dw(u32 *cmd, u32 flags) -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* Re: [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction 2022-04-21 11:38 ` Ramalingam C @ 2022-04-21 13:37 ` Hellstrom, Thomas -1 siblings, 0 replies; 24+ messages in thread From: Hellstrom, Thomas @ 2022-04-21 13:37 UTC (permalink / raw) To: dri-devel, C, Ramalingam, intel-gfx; +Cc: Auld, Matthew On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > Capture the eviction details for Flat-CCS capable lmem only objects > and > lmem objects with smem residency. This also captures the impact of > eviction on object's memory residency and Flat-CCS compression > state. > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > --- > drivers/gpu/drm/i915/gt/intel_migrate.c | 36 ++++++++++++++++++----- > -- > 1 file changed, 27 insertions(+), 9 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > b/drivers/gpu/drm/i915/gt/intel_migrate.c > index 463a6a14b5f9..9d0d18950e76 100644 > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > @@ -485,16 +485,34 @@ static bool wa_1209644611_applies(int ver, u32 > size) > * And CCS data can be copied in and out of CCS region through > * XY_CTRL_SURF_COPY_BLT. CPU can't access the CCS data directly. > * > - * When we exhaust the lmem, if the object's placements support > smem, then we can > - * directly decompress the compressed lmem object into smem and > start using it > - * from smem itself. > + * when we exhaust the lmem, we need to handle two types of flat-ccs > capable > + * objects for its eviction. > + * 1) lmem only objects > + * 2) lmem objects with smem residency option > * > - * But when we need to swapout the compressed lmem object into a > smem region > - * though objects' placement doesn't support smem, then we copy the > lmem content > - * as it is into smem region along with ccs data (using > XY_CTRL_SURF_COPY_BLT). > - * When the object is referred, lmem content will be swaped in along > with > - * restoration of the CCS data (using XY_CTRL_SURF_COPY_BLT) at > corresponding > - * location. > + * 1) lmem only objects: > + * > + * lmem backing memory can be temporarily evicted to smem, along > with the > + * auxiliary CCS state, where it can be potentially swapped-out at a > later point, > + * if required. If userspace later touches the evicted pages, then > we always move > + * the backing memory back to lmem, which includes restoring the > saved CCS state, > + * and potentially performing any required swap-in. > + * > + * In this scenario, objects' backing memory class and Flat-CCS > state doesn't > + * change. > + * > + * 2) lmem objects with smem residency option > + * > + * Lmem object with smem region in it's placement list, will be > migrated into > + * smem by decompressing the content. I915 doesn't handle this kind > of > + * migration for Flat-CCS compressed objects yet. > + * > + * In this scenario, objects' backing memory class and Flat-CCS > state changed, > + * and userspace is not aware of it. > + * > + * In summary, when a userspace wants to be sure about the objects > memory > + * residency and flat-ccs compression state, then placement list > can't have > + * the lmem and smem together. Instead, object has to be lmem > resident only. For 2) I was under the impression that with flat CCS, these objects need to be always uncompressed, since the kernel doesn't have the needed information to decompress / compress. Or has this been changed recently? /Thomas > */ > > static inline u32 *i915_flush_dw(u32 *cmd, u32 flags) ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Intel-gfx] [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction @ 2022-04-21 13:37 ` Hellstrom, Thomas 0 siblings, 0 replies; 24+ messages in thread From: Hellstrom, Thomas @ 2022-04-21 13:37 UTC (permalink / raw) To: dri-devel, C, Ramalingam, intel-gfx; +Cc: Auld, Matthew On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > Capture the eviction details for Flat-CCS capable lmem only objects > and > lmem objects with smem residency. This also captures the impact of > eviction on object's memory residency and Flat-CCS compression > state. > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > --- > drivers/gpu/drm/i915/gt/intel_migrate.c | 36 ++++++++++++++++++----- > -- > 1 file changed, 27 insertions(+), 9 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > b/drivers/gpu/drm/i915/gt/intel_migrate.c > index 463a6a14b5f9..9d0d18950e76 100644 > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > @@ -485,16 +485,34 @@ static bool wa_1209644611_applies(int ver, u32 > size) > * And CCS data can be copied in and out of CCS region through > * XY_CTRL_SURF_COPY_BLT. CPU can't access the CCS data directly. > * > - * When we exhaust the lmem, if the object's placements support > smem, then we can > - * directly decompress the compressed lmem object into smem and > start using it > - * from smem itself. > + * when we exhaust the lmem, we need to handle two types of flat-ccs > capable > + * objects for its eviction. > + * 1) lmem only objects > + * 2) lmem objects with smem residency option > * > - * But when we need to swapout the compressed lmem object into a > smem region > - * though objects' placement doesn't support smem, then we copy the > lmem content > - * as it is into smem region along with ccs data (using > XY_CTRL_SURF_COPY_BLT). > - * When the object is referred, lmem content will be swaped in along > with > - * restoration of the CCS data (using XY_CTRL_SURF_COPY_BLT) at > corresponding > - * location. > + * 1) lmem only objects: > + * > + * lmem backing memory can be temporarily evicted to smem, along > with the > + * auxiliary CCS state, where it can be potentially swapped-out at a > later point, > + * if required. If userspace later touches the evicted pages, then > we always move > + * the backing memory back to lmem, which includes restoring the > saved CCS state, > + * and potentially performing any required swap-in. > + * > + * In this scenario, objects' backing memory class and Flat-CCS > state doesn't > + * change. > + * > + * 2) lmem objects with smem residency option > + * > + * Lmem object with smem region in it's placement list, will be > migrated into > + * smem by decompressing the content. I915 doesn't handle this kind > of > + * migration for Flat-CCS compressed objects yet. > + * > + * In this scenario, objects' backing memory class and Flat-CCS > state changed, > + * and userspace is not aware of it. > + * > + * In summary, when a userspace wants to be sure about the objects > memory > + * residency and flat-ccs compression state, then placement list > can't have > + * the lmem and smem together. Instead, object has to be lmem > resident only. For 2) I was under the impression that with flat CCS, these objects need to be always uncompressed, since the kernel doesn't have the needed information to decompress / compress. Or has this been changed recently? /Thomas > */ > > static inline u32 *i915_flush_dw(u32 *cmd, u32 flags) ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction 2022-04-21 13:37 ` [Intel-gfx] " Hellstrom, Thomas @ 2022-04-22 8:43 ` Ramalingam C -1 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-22 8:43 UTC (permalink / raw) To: Hellstrom, Thomas; +Cc: intel-gfx, Auld, Matthew, dri-devel On 2022-04-21 at 19:07:29 +0530, Hellstrom, Thomas wrote: > On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > > Capture the eviction details for Flat-CCS capable lmem only objects > > and > > lmem objects with smem residency. This also captures the impact of > > eviction on object's memory residency and Flat-CCS compression > > state. > > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > > --- > > drivers/gpu/drm/i915/gt/intel_migrate.c | 36 ++++++++++++++++++----- > > -- > > 1 file changed, 27 insertions(+), 9 deletions(-) > > > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > > b/drivers/gpu/drm/i915/gt/intel_migrate.c > > index 463a6a14b5f9..9d0d18950e76 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > > @@ -485,16 +485,34 @@ static bool wa_1209644611_applies(int ver, u32 > > size) > > * And CCS data can be copied in and out of CCS region through > > * XY_CTRL_SURF_COPY_BLT. CPU can't access the CCS data directly. > > * > > - * When we exhaust the lmem, if the object's placements support > > smem, then we can > > - * directly decompress the compressed lmem object into smem and > > start using it > > - * from smem itself. > > + * when we exhaust the lmem, we need to handle two types of flat-ccs > > capable > > + * objects for its eviction. > > + * 1) lmem only objects > > + * 2) lmem objects with smem residency option > > * > > - * But when we need to swapout the compressed lmem object into a > > smem region > > - * though objects' placement doesn't support smem, then we copy the > > lmem content > > - * as it is into smem region along with ccs data (using > > XY_CTRL_SURF_COPY_BLT). > > - * When the object is referred, lmem content will be swaped in along > > with > > - * restoration of the CCS data (using XY_CTRL_SURF_COPY_BLT) at > > corresponding > > - * location. > > + * 1) lmem only objects: > > + * > > + * lmem backing memory can be temporarily evicted to smem, along > > with the > > + * auxiliary CCS state, where it can be potentially swapped-out at a > > later point, > > + * if required. If userspace later touches the evicted pages, then > > we always move > > + * the backing memory back to lmem, which includes restoring the > > saved CCS state, > > + * and potentially performing any required swap-in. > > + * > > + * In this scenario, objects' backing memory class and Flat-CCS > > state doesn't > > + * change. > > + * > > + * 2) lmem objects with smem residency option > > + * > > + * Lmem object with smem region in it's placement list, will be > > migrated into > > + * smem by decompressing the content. I915 doesn't handle this kind > > of > > + * migration for Flat-CCS compressed objects yet. > > + * > > + * In this scenario, objects' backing memory class and Flat-CCS > > state changed, > > + * and userspace is not aware of it. > > + * > > + * In summary, when a userspace wants to be sure about the objects > > memory > > + * residency and flat-ccs compression state, then placement list > > can't have > > + * the lmem and smem together. Instead, object has to be lmem > > resident only. > > For 2) I was under the impression that with flat CCS, these objects > need to be always uncompressed, since the kernel doesn't have the > needed information to decompress / compress. Or has this been changed > recently? Sorry. I have overlooked the lack of inputs required for decompression at kernel. So yes we can't support the compression on the lmem objects with {lmem, smem} as placement preferences. I will update the documentation accordingly. Ram. > > /Thomas > > > > > > */ > > > > static inline u32 *i915_flush_dw(u32 *cmd, u32 flags) > ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Intel-gfx] [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction @ 2022-04-22 8:43 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-22 8:43 UTC (permalink / raw) To: Hellstrom, Thomas; +Cc: intel-gfx, Auld, Matthew, dri-devel On 2022-04-21 at 19:07:29 +0530, Hellstrom, Thomas wrote: > On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > > Capture the eviction details for Flat-CCS capable lmem only objects > > and > > lmem objects with smem residency. This also captures the impact of > > eviction on object's memory residency and Flat-CCS compression > > state. > > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > > --- > > drivers/gpu/drm/i915/gt/intel_migrate.c | 36 ++++++++++++++++++----- > > -- > > 1 file changed, 27 insertions(+), 9 deletions(-) > > > > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c > > b/drivers/gpu/drm/i915/gt/intel_migrate.c > > index 463a6a14b5f9..9d0d18950e76 100644 > > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c > > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c > > @@ -485,16 +485,34 @@ static bool wa_1209644611_applies(int ver, u32 > > size) > > * And CCS data can be copied in and out of CCS region through > > * XY_CTRL_SURF_COPY_BLT. CPU can't access the CCS data directly. > > * > > - * When we exhaust the lmem, if the object's placements support > > smem, then we can > > - * directly decompress the compressed lmem object into smem and > > start using it > > - * from smem itself. > > + * when we exhaust the lmem, we need to handle two types of flat-ccs > > capable > > + * objects for its eviction. > > + * 1) lmem only objects > > + * 2) lmem objects with smem residency option > > * > > - * But when we need to swapout the compressed lmem object into a > > smem region > > - * though objects' placement doesn't support smem, then we copy the > > lmem content > > - * as it is into smem region along with ccs data (using > > XY_CTRL_SURF_COPY_BLT). > > - * When the object is referred, lmem content will be swaped in along > > with > > - * restoration of the CCS data (using XY_CTRL_SURF_COPY_BLT) at > > corresponding > > - * location. > > + * 1) lmem only objects: > > + * > > + * lmem backing memory can be temporarily evicted to smem, along > > with the > > + * auxiliary CCS state, where it can be potentially swapped-out at a > > later point, > > + * if required. If userspace later touches the evicted pages, then > > we always move > > + * the backing memory back to lmem, which includes restoring the > > saved CCS state, > > + * and potentially performing any required swap-in. > > + * > > + * In this scenario, objects' backing memory class and Flat-CCS > > state doesn't > > + * change. > > + * > > + * 2) lmem objects with smem residency option > > + * > > + * Lmem object with smem region in it's placement list, will be > > migrated into > > + * smem by decompressing the content. I915 doesn't handle this kind > > of > > + * migration for Flat-CCS compressed objects yet. > > + * > > + * In this scenario, objects' backing memory class and Flat-CCS > > state changed, > > + * and userspace is not aware of it. > > + * > > + * In summary, when a userspace wants to be sure about the objects > > memory > > + * residency and flat-ccs compression state, then placement list > > can't have > > + * the lmem and smem together. Instead, object has to be lmem > > resident only. > > For 2) I was under the impression that with flat CCS, these objects > need to be always uncompressed, since the kernel doesn't have the > needed information to decompress / compress. Or has this been changed > recently? Sorry. I have overlooked the lack of inputs required for decompression at kernel. So yes we can't support the compression on the lmem objects with {lmem, smem} as placement preferences. I will update the documentation accordingly. Ram. > > /Thomas > > > > > > */ > > > > static inline u32 *i915_flush_dw(u32 *cmd, u32 flags) > ^ permalink raw reply [flat|nested] 24+ messages in thread
* [PATCH 4/4] uapi/drm/i915: Update the placement list impact on obj residency 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C @ 2022-04-21 11:38 ` Ramalingam C -1 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Object created with list of memory classes as placement preferences, can be backed with any memory class of the list as per kernel's migration policy for the memory contrain situation. Userspace won't be notified of the memory residency change at this scenario. And also Flat-CCS compression is supported only on objects of I915_MEMORY_CLASS_DEVICE. When the Flat-CCS compressed objects migrates out of I915_MEMORY_CLASS_DEVICE, due to memory constrain, content will be decompressed without notifying the userpsace. Record these details in Kernel documentation. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- include/uapi/drm/i915_drm.h | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h index 35ca528803fd..8b25dd6a157a 100644 --- a/include/uapi/drm/i915_drm.h +++ b/include/uapi/drm/i915_drm.h @@ -3393,6 +3393,20 @@ struct drm_i915_gem_create_ext { * At which point we get the object handle in &drm_i915_gem_create_ext.handle, * along with the final object size in &drm_i915_gem_create_ext.size, which * should account for any rounding up, if required. + * + * If an object is created with list of memory classes as their placement + * preference, kernel could use one of the memory class as the backing storage + * based on the memory availability. At memory pressure kernel could migrate the + * objects content from one memory class to another, given in the placement list. + * + * With placement preference list, userpace can't be sure about the object's memory + * residence. + * + * Flat-CCS compression is supported only for objects of I915_MEMORY_CLASS_DEVICE. + * If the object has other placement preferences, and if the content is + * migrated (by kernel due to memory constrain) to a memory class which is other + * than I915_MEMORY_CLASS_DEVICE, object content will be decompressed by kernel. + * Userpace will be ignorant of this Flat-CCS state change. */ struct drm_i915_gem_create_ext_memory_regions { /** @base: Extension link. See struct i915_user_extension. */ -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* [Intel-gfx] [PATCH 4/4] uapi/drm/i915: Update the placement list impact on obj residency @ 2022-04-21 11:38 ` Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:38 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Object created with list of memory classes as placement preferences, can be backed with any memory class of the list as per kernel's migration policy for the memory contrain situation. Userspace won't be notified of the memory residency change at this scenario. And also Flat-CCS compression is supported only on objects of I915_MEMORY_CLASS_DEVICE. When the Flat-CCS compressed objects migrates out of I915_MEMORY_CLASS_DEVICE, due to memory constrain, content will be decompressed without notifying the userpsace. Record these details in Kernel documentation. Signed-off-by: Ramalingam C <ramalingam.c@intel.com> --- include/uapi/drm/i915_drm.h | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h index 35ca528803fd..8b25dd6a157a 100644 --- a/include/uapi/drm/i915_drm.h +++ b/include/uapi/drm/i915_drm.h @@ -3393,6 +3393,20 @@ struct drm_i915_gem_create_ext { * At which point we get the object handle in &drm_i915_gem_create_ext.handle, * along with the final object size in &drm_i915_gem_create_ext.size, which * should account for any rounding up, if required. + * + * If an object is created with list of memory classes as their placement + * preference, kernel could use one of the memory class as the backing storage + * based on the memory availability. At memory pressure kernel could migrate the + * objects content from one memory class to another, given in the placement list. + * + * With placement preference list, userpace can't be sure about the object's memory + * residence. + * + * Flat-CCS compression is supported only for objects of I915_MEMORY_CLASS_DEVICE. + * If the object has other placement preferences, and if the content is + * migrated (by kernel due to memory constrain) to a memory class which is other + * than I915_MEMORY_CLASS_DEVICE, object content will be decompressed by kernel. + * Userpace will be ignorant of this Flat-CCS state change. */ struct drm_i915_gem_create_ext_memory_regions { /** @base: Extension link. See struct i915_user_extension. */ -- 2.20.1 ^ permalink raw reply related [flat|nested] 24+ messages in thread
* Re: [PATCH 4/4] uapi/drm/i915: Update the placement list impact on obj residency 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C @ 2022-04-21 13:40 ` Hellstrom, Thomas -1 siblings, 0 replies; 24+ messages in thread From: Hellstrom, Thomas @ 2022-04-21 13:40 UTC (permalink / raw) To: dri-devel, C, Ramalingam, intel-gfx; +Cc: Auld, Matthew On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > Object created with list of memory classes as placement preferences, > can > be backed with any memory class of the list as per kernel's migration > policy for the memory contrain situation. Userspace won't be notified > of > the memory residency change at this scenario. > > And also Flat-CCS compression is supported only on objects of > I915_MEMORY_CLASS_DEVICE. When the Flat-CCS compressed objects > migrates > out of I915_MEMORY_CLASS_DEVICE, due to memory constrain, content > will > be decompressed without notifying the userpsace. userspace > > Record these details in Kernel documentation. > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > --- > include/uapi/drm/i915_drm.h | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/include/uapi/drm/i915_drm.h > b/include/uapi/drm/i915_drm.h > index 35ca528803fd..8b25dd6a157a 100644 > --- a/include/uapi/drm/i915_drm.h > +++ b/include/uapi/drm/i915_drm.h > @@ -3393,6 +3393,20 @@ struct drm_i915_gem_create_ext { > * At which point we get the object handle in > &drm_i915_gem_create_ext.handle, > * along with the final object size in > &drm_i915_gem_create_ext.size, which > * should account for any rounding up, if required. > + * > + * If an object is created with list of memory classes as their > placement > + * preference, kernel could use one of the memory class as the > backing storage > + * based on the memory availability. At memory pressure kernel could > migrate the > + * objects content from one memory class to another, given in the > placement list. > + * > + * With placement preference list, userpace can't be sure about the > object's memory > + * residence. > + * > + * Flat-CCS compression is supported only for objects of > I915_MEMORY_CLASS_DEVICE. > + * If the object has other placement preferences, and if the content > is > + * migrated (by kernel due to memory constrain) to a memory class > which is other > + * than I915_MEMORY_CLASS_DEVICE, object content will be > decompressed by kernel. > + * Userpace will be ignorant of this Flat-CCS state change. Same question here as for previous commit. > */ > struct drm_i915_gem_create_ext_memory_regions { > /** @base: Extension link. See struct i915_user_extension. */ ^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Intel-gfx] [PATCH 4/4] uapi/drm/i915: Update the placement list impact on obj residency @ 2022-04-21 13:40 ` Hellstrom, Thomas 0 siblings, 0 replies; 24+ messages in thread From: Hellstrom, Thomas @ 2022-04-21 13:40 UTC (permalink / raw) To: dri-devel, C, Ramalingam, intel-gfx; +Cc: Auld, Matthew On Thu, 2022-04-21 at 17:08 +0530, Ramalingam C wrote: > Object created with list of memory classes as placement preferences, > can > be backed with any memory class of the list as per kernel's migration > policy for the memory contrain situation. Userspace won't be notified > of > the memory residency change at this scenario. > > And also Flat-CCS compression is supported only on objects of > I915_MEMORY_CLASS_DEVICE. When the Flat-CCS compressed objects > migrates > out of I915_MEMORY_CLASS_DEVICE, due to memory constrain, content > will > be decompressed without notifying the userpsace. userspace > > Record these details in Kernel documentation. > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > --- > include/uapi/drm/i915_drm.h | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/include/uapi/drm/i915_drm.h > b/include/uapi/drm/i915_drm.h > index 35ca528803fd..8b25dd6a157a 100644 > --- a/include/uapi/drm/i915_drm.h > +++ b/include/uapi/drm/i915_drm.h > @@ -3393,6 +3393,20 @@ struct drm_i915_gem_create_ext { > * At which point we get the object handle in > &drm_i915_gem_create_ext.handle, > * along with the final object size in > &drm_i915_gem_create_ext.size, which > * should account for any rounding up, if required. > + * > + * If an object is created with list of memory classes as their > placement > + * preference, kernel could use one of the memory class as the > backing storage > + * based on the memory availability. At memory pressure kernel could > migrate the > + * objects content from one memory class to another, given in the > placement list. > + * > + * With placement preference list, userpace can't be sure about the > object's memory > + * residence. > + * > + * Flat-CCS compression is supported only for objects of > I915_MEMORY_CLASS_DEVICE. > + * If the object has other placement preferences, and if the content > is > + * migrated (by kernel due to memory constrain) to a memory class > which is other > + * than I915_MEMORY_CLASS_DEVICE, object content will be > decompressed by kernel. > + * Userpace will be ignorant of this Flat-CCS state change. Same question here as for previous commit. > */ > struct drm_i915_gem_create_ext_memory_regions { > /** @base: Extension link. See struct i915_user_extension. */ ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Flat-CCS eviction enhancements (rev2) 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C ` (4 preceding siblings ...) (?) @ 2022-04-21 14:20 ` Patchwork -1 siblings, 0 replies; 24+ messages in thread From: Patchwork @ 2022-04-21 14:20 UTC (permalink / raw) To: Ramalingam C; +Cc: intel-gfx == Series Details == Series: Flat-CCS eviction enhancements (rev2) URL : https://patchwork.freedesktop.org/series/102916/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for Flat-CCS eviction enhancements (rev2) 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C ` (5 preceding siblings ...) (?) @ 2022-04-21 14:48 ` Patchwork -1 siblings, 0 replies; 24+ messages in thread From: Patchwork @ 2022-04-21 14:48 UTC (permalink / raw) To: Ramalingam C; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 9945 bytes --] == Series Details == Series: Flat-CCS eviction enhancements (rev2) URL : https://patchwork.freedesktop.org/series/102916/ State : success == Summary == CI Bug Log - changes from CI_DRM_11535 -> Patchwork_102916v2 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/index.html Participating hosts (45 -> 46) ------------------------------ Additional (3): fi-cml-u2 fi-icl-u2 bat-dg2-8 Missing (2): bat-rpls-2 fi-bsw-cyan Known issues ------------ Here are the changes found in Patchwork_102916v2 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_exec_fence@basic-busy@bcs0: - fi-cml-u2: NOTRUN -> [SKIP][1] ([i915#1208]) +1 similar issue [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@gem_exec_fence@basic-busy@bcs0.html * igt@gem_exec_suspend@basic-s3@smem: - fi-bdw-5557u: [PASS][2] -> [INCOMPLETE][3] ([i915#146]) [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html - fi-rkl-11600: [PASS][4] -> [INCOMPLETE][5] ([i915#5127]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/fi-rkl-11600/igt@gem_exec_suspend@basic-s3@smem.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-rkl-11600/igt@gem_exec_suspend@basic-s3@smem.html * igt@gem_huc_copy@huc-copy: - fi-cml-u2: NOTRUN -> [SKIP][6] ([i915#2190]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@gem_huc_copy@huc-copy.html - fi-icl-u2: NOTRUN -> [SKIP][7] ([i915#2190]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-icl-u2/igt@gem_huc_copy@huc-copy.html * igt@gem_lmem_swapping@parallel-random-engines: - fi-icl-u2: NOTRUN -> [SKIP][8] ([i915#4613]) +3 similar issues [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-icl-u2/igt@gem_lmem_swapping@parallel-random-engines.html - fi-cml-u2: NOTRUN -> [SKIP][9] ([i915#4613]) +3 similar issues [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@gem_lmem_swapping@parallel-random-engines.html * igt@i915_selftest@live@hangcheck: - fi-hsw-4770: [PASS][10] -> [INCOMPLETE][11] ([i915#4785]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html * igt@kms_chamelium@dp-hpd-fast: - fi-cml-u2: NOTRUN -> [SKIP][12] ([fdo#109284] / [fdo#111827]) +8 similar issues [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@kms_chamelium@dp-hpd-fast.html * igt@kms_chamelium@hdmi-hpd-fast: - fi-icl-u2: NOTRUN -> [SKIP][13] ([fdo#111827]) +8 similar issues [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: - fi-cml-u2: NOTRUN -> [SKIP][14] ([fdo#109278]) +1 similar issue [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy: - fi-icl-u2: NOTRUN -> [SKIP][15] ([fdo#109278]) +2 similar issues [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html * igt@kms_force_connector_basic@force-load-detect: - fi-cml-u2: NOTRUN -> [SKIP][16] ([fdo#109285]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@kms_force_connector_basic@force-load-detect.html - fi-icl-u2: NOTRUN -> [SKIP][17] ([fdo#109285]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-icl-u2/igt@kms_force_connector_basic@force-load-detect.html * igt@kms_frontbuffer_tracking@basic: - fi-cml-u2: NOTRUN -> [DMESG-WARN][18] ([i915#4269]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d: - fi-cml-u2: NOTRUN -> [SKIP][19] ([fdo#109278] / [i915#533]) [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html * igt@kms_setmode@basic-clone-single-crtc: - fi-icl-u2: NOTRUN -> [SKIP][20] ([i915#3555]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-icl-u2/igt@kms_setmode@basic-clone-single-crtc.html - fi-cml-u2: NOTRUN -> [SKIP][21] ([i915#3555]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@kms_setmode@basic-clone-single-crtc.html * igt@prime_vgem@basic-userptr: - fi-icl-u2: NOTRUN -> [SKIP][22] ([i915#3301]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-icl-u2/igt@prime_vgem@basic-userptr.html - fi-cml-u2: NOTRUN -> [SKIP][23] ([i915#3301]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/fi-cml-u2/igt@prime_vgem@basic-userptr.html #### Possible fixes #### * igt@i915_selftest@live@workarounds: - {bat-adlp-6}: [DMESG-FAIL][24] -> [PASS][25] [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/bat-adlp-6/igt@i915_selftest@live@workarounds.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/bat-adlp-6/igt@i915_selftest@live@workarounds.html * igt@kms_flip@basic-plain-flip@a-edp1: - bat-adlp-4: [DMESG-WARN][26] ([i915#3576]) -> [PASS][27] +2 similar issues [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/bat-adlp-4/igt@kms_flip@basic-plain-flip@a-edp1.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/bat-adlp-4/igt@kms_flip@basic-plain-flip@a-edp1.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278 [fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284 [fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285 [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827 [i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072 [i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155 [i915#1208]: https://gitlab.freedesktop.org/drm/intel/issues/1208 [i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146 [i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190 [i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582 [i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291 [i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301 [i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555 [i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576 [i915#3595]: https://gitlab.freedesktop.org/drm/intel/issues/3595 [i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708 [i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077 [i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079 [i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083 [i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103 [i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212 [i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213 [i915#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215 [i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269 [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312 [i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613 [i915#4785]: https://gitlab.freedesktop.org/drm/intel/issues/4785 [i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873 [i915#4897]: https://gitlab.freedesktop.org/drm/intel/issues/4897 [i915#5127]: https://gitlab.freedesktop.org/drm/intel/issues/5127 [i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190 [i915#5270]: https://gitlab.freedesktop.org/drm/intel/issues/5270 [i915#5274]: https://gitlab.freedesktop.org/drm/intel/issues/5274 [i915#5275]: https://gitlab.freedesktop.org/drm/intel/issues/5275 [i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533 [i915#5341]: https://gitlab.freedesktop.org/drm/intel/issues/5341 [i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354 [i915#5356]: https://gitlab.freedesktop.org/drm/intel/issues/5356 [i915#5763]: https://gitlab.freedesktop.org/drm/intel/issues/5763 Build changes ------------- * Linux: CI_DRM_11535 -> Patchwork_102916v2 CI-20190529: 20190529 CI_DRM_11535: a80d6006be30036b14f1bcf7346dcd2faaf199d5 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_6444: df584c804e3a44431b0e5ae21c190b6e9acb35ab @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_102916v2: a80d6006be30036b14f1bcf7346dcd2faaf199d5 @ git://anongit.freedesktop.org/gfx-ci/linux ### Linux commits ae84c8c34176 uapi/drm/i915: Update the placement list impact on obj residency ce57ebff0b61 drm/i915/gt: Extend doc on Flat-CCS obj eviction 9858798323d2 drm/i915/gt: optimize the ccs_sz calculation per chunk da74541cc40e drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/index.html [-- Attachment #2: Type: text/html, Size: 10012 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for Flat-CCS eviction enhancements (rev2) 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C ` (6 preceding siblings ...) (?) @ 2022-04-21 18:50 ` Patchwork -1 siblings, 0 replies; 24+ messages in thread From: Patchwork @ 2022-04-21 18:50 UTC (permalink / raw) To: Ramalingam C; +Cc: intel-gfx [-- Attachment #1: Type: text/plain, Size: 50691 bytes --] == Series Details == Series: Flat-CCS eviction enhancements (rev2) URL : https://patchwork.freedesktop.org/series/102916/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11535_full -> Patchwork_102916v2_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_102916v2_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_102916v2_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 -> 13) ------------------------------ No changes in participating hosts Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_102916v2_full: ### IGT changes ### #### Possible regressions #### * igt@gem_busy@close-race: - shard-skl: [PASS][1] -> [TIMEOUT][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl1/igt@gem_busy@close-race.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl4/igt@gem_busy@close-race.html * igt@gem_exec_schedule@wide@vcs1: - shard-kbl: [PASS][3] -> [INCOMPLETE][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-kbl6/igt@gem_exec_schedule@wide@vcs1.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-kbl7/igt@gem_exec_schedule@wide@vcs1.html * igt@i915_selftest@perf@engine_cs: - shard-tglb: [PASS][5] -> [DMESG-WARN][6] +2 similar issues [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-tglb5/igt@i915_selftest@perf@engine_cs.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb3/igt@i915_selftest@perf@engine_cs.html * igt@kms_flip@flip-vs-suspend-interruptible@a-edp1: - shard-skl: [PASS][7] -> [INCOMPLETE][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl1/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl6/igt@kms_flip@flip-vs-suspend-interruptible@a-edp1.html #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * {igt@gem_lmem_swapping@parallel-random-verify-ccs@lmem0}: - {shard-dg1}: NOTRUN -> [SKIP][9] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-dg1-18/igt@gem_lmem_swapping@parallel-random-verify-ccs@lmem0.html Known issues ------------ Here are the changes found in Patchwork_102916v2_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_eio@unwedge-stress: - shard-iclb: [PASS][10] -> [TIMEOUT][11] ([i915#3070]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb4/igt@gem_eio@unwedge-stress.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb3/igt@gem_eio@unwedge-stress.html * igt@gem_exec_fair@basic-deadline: - shard-skl: NOTRUN -> [FAIL][12] ([i915#2846]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl3/igt@gem_exec_fair@basic-deadline.html * igt@gem_exec_fair@basic-pace@vcs0: - shard-kbl: [PASS][13] -> [FAIL][14] ([i915#2842]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-kbl4/igt@gem_exec_fair@basic-pace@vcs0.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-kbl6/igt@gem_exec_fair@basic-pace@vcs0.html * igt@gem_exec_fair@basic-throttle@rcs0: - shard-glk: [PASS][15] -> [FAIL][16] ([i915#2842]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-glk9/igt@gem_exec_fair@basic-throttle@rcs0.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-glk3/igt@gem_exec_fair@basic-throttle@rcs0.html - shard-iclb: [PASS][17] -> [FAIL][18] ([i915#2849]) [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb1/igt@gem_exec_fair@basic-throttle@rcs0.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb2/igt@gem_exec_fair@basic-throttle@rcs0.html * igt@gem_exec_flush@basic-wb-set-default: - shard-snb: [PASS][19] -> [SKIP][20] ([fdo#109271]) +1 similar issue [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-snb7/igt@gem_exec_flush@basic-wb-set-default.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-snb6/igt@gem_exec_flush@basic-wb-set-default.html * igt@gem_exec_params@no-vebox: - shard-iclb: NOTRUN -> [SKIP][21] ([fdo#109283]) +1 similar issue [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb1/igt@gem_exec_params@no-vebox.html - shard-tglb: NOTRUN -> [SKIP][22] ([fdo#109283] / [i915#4877]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@gem_exec_params@no-vebox.html * igt@gem_exec_params@secure-non-root: - shard-iclb: NOTRUN -> [SKIP][23] ([fdo#112283]) [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb5/igt@gem_exec_params@secure-non-root.html * igt@gem_huc_copy@huc-copy: - shard-skl: NOTRUN -> [SKIP][24] ([fdo#109271] / [i915#2190]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl4/igt@gem_huc_copy@huc-copy.html * igt@gem_lmem_swapping@heavy-random: - shard-iclb: NOTRUN -> [SKIP][25] ([i915#4613]) +1 similar issue [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@gem_lmem_swapping@heavy-random.html - shard-apl: NOTRUN -> [SKIP][26] ([fdo#109271] / [i915#4613]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl7/igt@gem_lmem_swapping@heavy-random.html * igt@gem_lmem_swapping@verify: - shard-skl: NOTRUN -> [SKIP][27] ([fdo#109271] / [i915#4613]) [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl3/igt@gem_lmem_swapping@verify.html * igt@gem_pxp@display-protected-crc: - shard-iclb: NOTRUN -> [SKIP][28] ([i915#4270]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@gem_pxp@display-protected-crc.html * igt@gem_render_copy@x-tiled-to-vebox-y-tiled: - shard-iclb: NOTRUN -> [SKIP][29] ([i915#768]) [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb1/igt@gem_render_copy@x-tiled-to-vebox-y-tiled.html * igt@gen9_exec_parse@unaligned-access: - shard-iclb: NOTRUN -> [SKIP][30] ([i915#2856]) +2 similar issues [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@gen9_exec_parse@unaligned-access.html * igt@i915_pm_dc@dc6-dpms: - shard-iclb: [PASS][31] -> [FAIL][32] ([i915#454]) [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb5/igt@i915_pm_dc@dc6-dpms.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html * igt@i915_pm_dc@dc9-dpms: - shard-iclb: [PASS][33] -> [SKIP][34] ([i915#4281]) [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb4/igt@i915_pm_dc@dc9-dpms.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb3/igt@i915_pm_dc@dc9-dpms.html * igt@i915_pm_rpm@gem-execbuf-stress-pc8: - shard-iclb: NOTRUN -> [SKIP][35] ([fdo#109293] / [fdo#109506]) [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html * igt@i915_selftest@live@hangcheck: - shard-snb: [PASS][36] -> [INCOMPLETE][37] ([i915#3921]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-snb2/igt@i915_selftest@live@hangcheck.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-snb2/igt@i915_selftest@live@hangcheck.html * igt@kms_addfb_basic@invalid-smem-bo-on-discrete: - shard-iclb: NOTRUN -> [SKIP][38] ([i915#3826]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb5/igt@kms_addfb_basic@invalid-smem-bo-on-discrete.html * igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-180-hflip: - shard-iclb: NOTRUN -> [SKIP][39] ([i915#5286]) [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-180-hflip.html * igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip: - shard-skl: NOTRUN -> [SKIP][40] ([fdo#109271] / [i915#3777]) +1 similar issue [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl3/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip.html * igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip: - shard-apl: NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#3777]) [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl1/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip.html * igt@kms_busy@extended-modeset-hang-newfb: - shard-skl: NOTRUN -> [SKIP][42] ([fdo#109271]) +151 similar issues [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl4/igt@kms_busy@extended-modeset-hang-newfb.html * igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_mc_ccs: - shard-apl: NOTRUN -> [SKIP][43] ([fdo#109271] / [i915#3886]) +4 similar issues [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl6/igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_mc_ccs.html * igt@kms_ccs@pipe-a-crc-primary-basic-y_tiled_gen12_mc_ccs: - shard-skl: NOTRUN -> [SKIP][44] ([fdo#109271] / [i915#3886]) +1 similar issue [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl3/igt@kms_ccs@pipe-a-crc-primary-basic-y_tiled_gen12_mc_ccs.html * igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc: - shard-iclb: NOTRUN -> [SKIP][45] ([fdo#109278] / [i915#3886]) +2 similar issues [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb1/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html * igt@kms_ccs@pipe-c-bad-pixel-format-yf_tiled_ccs: - shard-tglb: NOTRUN -> [SKIP][46] ([fdo#111615] / [i915#3689]) [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@kms_ccs@pipe-c-bad-pixel-format-yf_tiled_ccs.html * igt@kms_chamelium@hdmi-edid-change-during-suspend: - shard-apl: NOTRUN -> [SKIP][47] ([fdo#109271] / [fdo#111827]) +11 similar issues [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl2/igt@kms_chamelium@hdmi-edid-change-during-suspend.html * igt@kms_chamelium@hdmi-hpd-storm: - shard-tglb: NOTRUN -> [SKIP][48] ([fdo#109284] / [fdo#111827]) [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@kms_chamelium@hdmi-hpd-storm.html * igt@kms_chamelium@vga-hpd-after-suspend: - shard-skl: NOTRUN -> [SKIP][49] ([fdo#109271] / [fdo#111827]) +6 similar issues [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl3/igt@kms_chamelium@vga-hpd-after-suspend.html * igt@kms_color@pipe-d-ctm-0-75: - shard-iclb: NOTRUN -> [SKIP][50] ([fdo#109278] / [i915#1149]) [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_color@pipe-d-ctm-0-75.html * igt@kms_color_chamelium@pipe-a-ctm-red-to-blue: - shard-iclb: NOTRUN -> [SKIP][51] ([fdo#109284] / [fdo#111827]) +3 similar issues [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_color_chamelium@pipe-a-ctm-red-to-blue.html * igt@kms_content_protection@atomic-dpms: - shard-apl: NOTRUN -> [TIMEOUT][52] ([i915#1319]) +1 similar issue [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl6/igt@kms_content_protection@atomic-dpms.html * igt@kms_content_protection@content_type_change: - shard-iclb: NOTRUN -> [SKIP][53] ([fdo#109300] / [fdo#111066]) [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb5/igt@kms_content_protection@content_type_change.html * igt@kms_cursor_crc@pipe-b-cursor-512x170-offscreen: - shard-iclb: NOTRUN -> [SKIP][54] ([fdo#109278] / [fdo#109279]) +2 similar issues [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb5/igt@kms_cursor_crc@pipe-b-cursor-512x170-offscreen.html * igt@kms_cursor_crc@pipe-c-cursor-512x170-rapid-movement: - shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109278]) +13 similar issues [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_cursor_crc@pipe-c-cursor-512x170-rapid-movement.html * igt@kms_cursor_crc@pipe-c-cursor-512x170-sliding: - shard-apl: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#5691]) [56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl6/igt@kms_cursor_crc@pipe-c-cursor-512x170-sliding.html * igt@kms_cursor_crc@pipe-c-cursor-max-size-random: - shard-tglb: NOTRUN -> [SKIP][57] ([i915#3359]) [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@kms_cursor_crc@pipe-c-cursor-max-size-random.html * igt@kms_cursor_legacy@cursorb-vs-flipa-atomic-transitions: - shard-iclb: NOTRUN -> [SKIP][58] ([fdo#109274] / [fdo#109278]) +1 similar issue [58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_cursor_legacy@cursorb-vs-flipa-atomic-transitions.html * igt@kms_cursor_legacy@cursorb-vs-flipa-atomic-transitions-varying-size: - shard-tglb: NOTRUN -> [SKIP][59] ([fdo#109274] / [fdo#111825]) [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@kms_cursor_legacy@cursorb-vs-flipa-atomic-transitions-varying-size.html * igt@kms_dsc@basic-dsc-enable: - shard-iclb: NOTRUN -> [SKIP][60] ([i915#3840]) [60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_dsc@basic-dsc-enable.html * igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible@ac-hdmi-a1-hdmi-a2: - shard-glk: [PASS][61] -> [FAIL][62] ([i915#2122]) [61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-glk6/igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible@ac-hdmi-a1-hdmi-a2.html [62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-glk9/igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible@ac-hdmi-a1-hdmi-a2.html * igt@kms_flip@2x-flip-vs-rmfb: - shard-iclb: NOTRUN -> [SKIP][63] ([fdo#109274]) +3 similar issues [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_flip@2x-flip-vs-rmfb.html * igt@kms_flip@flip-vs-expired-vblank@a-dp1: - shard-apl: [PASS][64] -> [FAIL][65] ([i915#79]) [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl8/igt@kms_flip@flip-vs-expired-vblank@a-dp1.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl8/igt@kms_flip@flip-vs-expired-vblank@a-dp1.html * igt@kms_flip@flip-vs-expired-vblank@c-hdmi-a2: - shard-glk: [PASS][66] -> [FAIL][67] ([i915#79]) [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-glk1/igt@kms_flip@flip-vs-expired-vblank@c-hdmi-a2.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-glk7/igt@kms_flip@flip-vs-expired-vblank@c-hdmi-a2.html * igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1: - shard-skl: [PASS][68] -> [FAIL][69] ([i915#2122]) [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl7/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl6/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html * igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-downscaling: - shard-iclb: [PASS][70] -> [SKIP][71] ([i915#3701]) [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-downscaling.html [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-downscaling.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-upscaling: - shard-skl: NOTRUN -> [INCOMPLETE][72] ([i915#3701]) [72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl4/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-upscaling.html * igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-onoff: - shard-tglb: NOTRUN -> [SKIP][73] ([fdo#109280] / [fdo#111825]) [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-onoff.html * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-mmap-wc: - shard-iclb: NOTRUN -> [SKIP][74] ([fdo#109280]) +7 similar issues [74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-cur-indfb-draw-mmap-wc.html * igt@kms_frontbuffer_tracking@psr-modesetfrombusy: - shard-kbl: NOTRUN -> [SKIP][75] ([fdo#109271]) +3 similar issues [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-kbl3/igt@kms_frontbuffer_tracking@psr-modesetfrombusy.html * igt@kms_hdr@bpc-switch@bpc-switch-edp-1-pipe-a: - shard-skl: [PASS][76] -> [FAIL][77] ([i915#1188]) [76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl3/igt@kms_hdr@bpc-switch@bpc-switch-edp-1-pipe-a.html [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl10/igt@kms_hdr@bpc-switch@bpc-switch-edp-1-pipe-a.html * igt@kms_hdr@static-toggle-dpms: - shard-iclb: NOTRUN -> [SKIP][78] ([i915#3555]) +1 similar issue [78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb5/igt@kms_hdr@static-toggle-dpms.html * igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence: - shard-skl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#533]) +1 similar issue [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl4/igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-d: - shard-apl: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#533]) [80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl6/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-d.html * igt@kms_plane_alpha_blend@pipe-a-alpha-basic: - shard-apl: NOTRUN -> [FAIL][81] ([fdo#108145] / [i915#265]) +1 similar issue [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl1/igt@kms_plane_alpha_blend@pipe-a-alpha-basic.html * igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb: - shard-skl: NOTRUN -> [FAIL][82] ([fdo#108145] / [i915#265]) +1 similar issue [82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl4/igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb.html * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: - shard-skl: [PASS][83] -> [FAIL][84] ([fdo#108145] / [i915#265]) [83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl3/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html [84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl10/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html * igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-b-edp-1-scaler-with-clipping-clamping: - shard-iclb: [PASS][85] -> [SKIP][86] ([i915#5176]) +1 similar issue [85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb5/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-b-edp-1-scaler-with-clipping-clamping.html [86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb3/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-b-edp-1-scaler-with-clipping-clamping.html * igt@kms_psr2_sf@plane-move-sf-dmg-area: - shard-skl: NOTRUN -> [SKIP][87] ([fdo#109271] / [i915#658]) [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl4/igt@kms_psr2_sf@plane-move-sf-dmg-area.html * igt@kms_psr2_su@frontbuffer-xrgb8888: - shard-apl: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#658]) +1 similar issue [88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl6/igt@kms_psr2_su@frontbuffer-xrgb8888.html * igt@kms_psr@psr2_cursor_render: - shard-iclb: NOTRUN -> [SKIP][89] ([fdo#109441]) [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_psr@psr2_cursor_render.html * igt@kms_vblank@pipe-a-ts-continuation-suspend: - shard-kbl: [PASS][90] -> [DMESG-WARN][91] ([i915#180]) [90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html * igt@kms_vblank@pipe-d-wait-forked-hang: - shard-apl: NOTRUN -> [SKIP][92] ([fdo#109271]) +145 similar issues [92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl2/igt@kms_vblank@pipe-d-wait-forked-hang.html * igt@kms_writeback@writeback-invalid-parameters: - shard-apl: NOTRUN -> [SKIP][93] ([fdo#109271] / [i915#2437]) +1 similar issue [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl1/igt@kms_writeback@writeback-invalid-parameters.html * igt@nouveau_crc@pipe-c-source-rg: - shard-iclb: NOTRUN -> [SKIP][94] ([i915#2530]) [94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@nouveau_crc@pipe-c-source-rg.html * igt@nouveau_crc@pipe-d-source-outp-inactive: - shard-tglb: NOTRUN -> [SKIP][95] ([i915#2530]) [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@nouveau_crc@pipe-d-source-outp-inactive.html - shard-iclb: NOTRUN -> [SKIP][96] ([fdo#109278] / [i915#2530]) [96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb1/igt@nouveau_crc@pipe-d-source-outp-inactive.html * igt@perf@polling-parameterized: - shard-apl: [PASS][97] -> [FAIL][98] ([i915#5639]) [97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl3/igt@perf@polling-parameterized.html [98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl8/igt@perf@polling-parameterized.html * igt@prime_nv_api@i915_nv_double_import: - shard-tglb: NOTRUN -> [SKIP][99] ([fdo#109291]) [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb1/igt@prime_nv_api@i915_nv_double_import.html * igt@prime_nv_pcopy@test1_micro: - shard-iclb: NOTRUN -> [SKIP][100] ([fdo#109291]) +1 similar issue [100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@prime_nv_pcopy@test1_micro.html * igt@prime_vgem@fence-read-hang: - shard-iclb: NOTRUN -> [SKIP][101] ([fdo#109295]) [101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@prime_vgem@fence-read-hang.html * igt@syncobj_timeline@invalid-transfer-non-existent-point: - shard-kbl: NOTRUN -> [DMESG-WARN][102] ([i915#5098]) [102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-kbl7/igt@syncobj_timeline@invalid-transfer-non-existent-point.html * igt@syncobj_wait@wait-all-for-submit-snapshot: - shard-skl: [PASS][103] -> [FAIL][104] ([i915#3515]) [103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl9/igt@syncobj_wait@wait-all-for-submit-snapshot.html [104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl8/igt@syncobj_wait@wait-all-for-submit-snapshot.html * igt@sysfs_clients@busy: - shard-skl: NOTRUN -> [SKIP][105] ([fdo#109271] / [i915#2994]) +1 similar issue [105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl3/igt@sysfs_clients@busy.html * igt@sysfs_clients@create: - shard-apl: NOTRUN -> [SKIP][106] ([fdo#109271] / [i915#2994]) [106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl6/igt@sysfs_clients@create.html * igt@sysfs_clients@split-10: - shard-iclb: NOTRUN -> [SKIP][107] ([i915#2994]) [107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb5/igt@sysfs_clients@split-10.html #### Possible fixes #### * igt@fbdev@read: - {shard-rkl}: [SKIP][108] ([i915#2582]) -> [PASS][109] [108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-1/igt@fbdev@read.html [109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@fbdev@read.html * igt@gem_ctx_persistence@many-contexts: - {shard-rkl}: [FAIL][110] ([i915#2410]) -> [PASS][111] [110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-4/igt@gem_ctx_persistence@many-contexts.html [111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-1/igt@gem_ctx_persistence@many-contexts.html * igt@gem_exec_fair@basic-none-share@rcs0: - shard-tglb: [FAIL][112] ([i915#2842]) -> [PASS][113] [112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-tglb8/igt@gem_exec_fair@basic-none-share@rcs0.html [113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb2/igt@gem_exec_fair@basic-none-share@rcs0.html * igt@gem_exec_fair@basic-none@vecs0: - shard-apl: [FAIL][114] ([i915#2842]) -> [PASS][115] [114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl3/igt@gem_exec_fair@basic-none@vecs0.html [115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl8/igt@gem_exec_fair@basic-none@vecs0.html * igt@gem_exec_fair@basic-pace-solo@rcs0: - shard-glk: [FAIL][116] ([i915#2842]) -> [PASS][117] [116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-glk6/igt@gem_exec_fair@basic-pace-solo@rcs0.html [117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-glk9/igt@gem_exec_fair@basic-pace-solo@rcs0.html * igt@gem_exec_fair@basic-throttle@rcs0: - {shard-rkl}: [FAIL][118] ([i915#2842]) -> [PASS][119] [118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-5/igt@gem_exec_fair@basic-throttle@rcs0.html [119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-4/igt@gem_exec_fair@basic-throttle@rcs0.html * igt@gem_exec_flush@basic-batch-kernel-default-uc: - shard-snb: [SKIP][120] ([fdo#109271]) -> [PASS][121] +1 similar issue [120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-snb6/igt@gem_exec_flush@basic-batch-kernel-default-uc.html [121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-snb4/igt@gem_exec_flush@basic-batch-kernel-default-uc.html * igt@gem_mmap_gtt@flink-race: - {shard-rkl}: [INCOMPLETE][122] ([i915#5080]) -> [PASS][123] [122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-5/igt@gem_mmap_gtt@flink-race.html [123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-4/igt@gem_mmap_gtt@flink-race.html * igt@i915_pm_dc@dc6-psr: - shard-iclb: [FAIL][124] ([i915#454]) -> [PASS][125] [124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb3/igt@i915_pm_dc@dc6-psr.html [125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@i915_pm_dc@dc6-psr.html * igt@i915_pm_rpm@i2c: - {shard-rkl}: [SKIP][126] ([fdo#109308]) -> [PASS][127] [126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-5/igt@i915_pm_rpm@i2c.html [127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@i915_pm_rpm@i2c.html * igt@kms_atomic@test-only: - {shard-rkl}: [SKIP][128] ([i915#1845] / [i915#4098]) -> [PASS][129] +12 similar issues [128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-1/igt@kms_atomic@test-only.html [129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@kms_atomic@test-only.html * igt@kms_color@pipe-b-gamma: - {shard-rkl}: [SKIP][130] ([i915#1149] / [i915#1849] / [i915#4070] / [i915#4098]) -> [PASS][131] [130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-2/igt@kms_color@pipe-b-gamma.html [131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@kms_color@pipe-b-gamma.html * igt@kms_cursor_crc@pipe-a-cursor-128x128-rapid-movement: - {shard-rkl}: [SKIP][132] ([fdo#112022] / [i915#4070]) -> [PASS][133] [132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-1/igt@kms_cursor_crc@pipe-a-cursor-128x128-rapid-movement.html [133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@kms_cursor_crc@pipe-a-cursor-128x128-rapid-movement.html * igt@kms_cursor_edge_walk@pipe-b-64x64-bottom-edge: - {shard-rkl}: [SKIP][134] ([i915#1849] / [i915#4070] / [i915#4098]) -> [PASS][135] [134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-2/igt@kms_cursor_edge_walk@pipe-b-64x64-bottom-edge.html [135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@kms_cursor_edge_walk@pipe-b-64x64-bottom-edge.html * igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions-varying-size: - {shard-rkl}: [SKIP][136] ([fdo#111825] / [i915#4070]) -> [PASS][137] +1 similar issue [136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-5/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions-varying-size.html [137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions-varying-size.html * igt@kms_draw_crc@draw-method-xrgb8888-blt-xtiled: - {shard-rkl}: [SKIP][138] ([fdo#111314] / [i915#4098] / [i915#4369]) -> [PASS][139] [138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-5/igt@kms_draw_crc@draw-method-xrgb8888-blt-xtiled.html [139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@kms_draw_crc@draw-method-xrgb8888-blt-xtiled.html * igt@kms_fbcon_fbt@fbc-suspend: - shard-apl: [INCOMPLETE][140] ([i915#180]) -> [PASS][141] [140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl3/igt@kms_fbcon_fbt@fbc-suspend.html [141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl2/igt@kms_fbcon_fbt@fbc-suspend.html * igt@kms_flip@flip-vs-suspend-interruptible@a-dp1: - shard-apl: [DMESG-WARN][142] ([i915#180]) -> [PASS][143] +3 similar issues [142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl3/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html [143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html * igt@kms_flip@flip-vs-suspend-interruptible@d-edp1: - shard-tglb: [DMESG-WARN][144] ([i915#2411]) -> [PASS][145] [144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-tglb8/igt@kms_flip@flip-vs-suspend-interruptible@d-edp1.html [145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-tglb2/igt@kms_flip@flip-vs-suspend-interruptible@d-edp1.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-wc: - {shard-rkl}: [SKIP][146] ([i915#1849] / [i915#4098]) -> [PASS][147] +11 similar issues [146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-rkl-5/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-wc.html [147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-rkl-6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-wc.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a: - shard-kbl: [DMESG-WARN][148] ([i915#180]) -> [PASS][149] [148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-kbl1/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html [149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-kbl7/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html * igt@kms_plane_multiple@atomic-pipe-c-tiling-x: - {shard-dg1}: [FAIL][150] -> [PASS][151] [150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-dg1-15/igt@kms_plane_multiple@atomic-pipe-c-tiling-x.html [151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-dg1-16/igt@kms_plane_multiple@atomic-pipe-c-tiling-x.html * igt@kms_psr2_su@frontbuffer-xrgb8888: - shard-iclb: [SKIP][152] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [PASS][153] [152]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb1/igt@kms_psr2_su@frontbuffer-xrgb8888.html [153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb2/igt@kms_psr2_su@frontbuffer-xrgb8888.html * igt@sysfs_heartbeat_interval@mixed@vcs0: - shard-skl: [WARN][154] ([i915#4055]) -> [PASS][155] [154]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl3/igt@sysfs_heartbeat_interval@mixed@vcs0.html [155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl10/igt@sysfs_heartbeat_interval@mixed@vcs0.html * igt@sysfs_heartbeat_interval@mixed@vecs0: - shard-skl: [FAIL][156] ([i915#1731]) -> [PASS][157] [156]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl3/igt@sysfs_heartbeat_interval@mixed@vecs0.html [157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl10/igt@sysfs_heartbeat_interval@mixed@vecs0.html #### Warnings #### * igt@gem_exec_balancer@parallel-contexts: - shard-iclb: [SKIP][158] ([i915#4525]) -> [DMESG-WARN][159] ([i915#5614]) [158]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb5/igt@gem_exec_balancer@parallel-contexts.html [159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb4/igt@gem_exec_balancer@parallel-contexts.html * igt@gem_exec_balancer@parallel-ordering: - shard-iclb: [SKIP][160] ([i915#4525]) -> [DMESG-FAIL][161] ([i915#5614]) [160]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb8/igt@gem_exec_balancer@parallel-ordering.html [161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb1/igt@gem_exec_balancer@parallel-ordering.html * igt@gem_exec_balancer@parallel-out-fence: - shard-iclb: [DMESG-WARN][162] ([i915#5614]) -> [SKIP][163] ([i915#4525]) +1 similar issue [162]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb4/igt@gem_exec_balancer@parallel-out-fence.html [163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@gem_exec_balancer@parallel-out-fence.html * igt@kms_flip@2x-flip-vs-suspend: - shard-skl: [SKIP][164] ([fdo#109271] / [i915#1888]) -> [SKIP][165] ([fdo#109271]) [164]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-skl7/igt@kms_flip@2x-flip-vs-suspend.html [165]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-skl6/igt@kms_flip@2x-flip-vs-suspend.html * igt@kms_psr2_sf@cursor-plane-update-sf: - shard-iclb: [SKIP][166] ([i915#2920]) -> [SKIP][167] ([fdo#111068] / [i915#658]) [166]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb2/igt@kms_psr2_sf@cursor-plane-update-sf.html [167]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb5/igt@kms_psr2_sf@cursor-plane-update-sf.html * igt@kms_psr2_sf@primary-plane-update-sf-dmg-area: - shard-iclb: [SKIP][168] ([fdo#111068] / [i915#658]) -> [SKIP][169] ([i915#2920]) [168]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb8/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area.html [169]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area.html * igt@kms_psr2_su@page_flip-xrgb8888: - shard-iclb: [FAIL][170] ([i915#4148]) -> [SKIP][171] ([fdo#109642] / [fdo#111068] / [i915#658]) [170]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-iclb2/igt@kms_psr2_su@page_flip-xrgb8888.html [171]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-iclb7/igt@kms_psr2_su@page_flip-xrgb8888.html * igt@runner@aborted: - shard-apl: ([FAIL][172], [FAIL][173], [FAIL][174], [FAIL][175], [FAIL][176], [FAIL][177], [FAIL][178], [FAIL][179], [FAIL][180]) ([i915#180] / [i915#3002] / [i915#4312] / [i915#5257]) -> ([FAIL][181], [FAIL][182], [FAIL][183], [FAIL][184]) ([i915#3002] / [i915#4312] / [i915#5257]) [172]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl3/igt@runner@aborted.html [173]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl4/igt@runner@aborted.html [174]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl3/igt@runner@aborted.html [175]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl3/igt@runner@aborted.html [176]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl6/igt@runner@aborted.html [177]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl4/igt@runner@aborted.html [178]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl8/igt@runner@aborted.html [179]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl1/igt@runner@aborted.html [180]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11535/shard-apl8/igt@runner@aborted.html [181]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl8/igt@runner@aborted.html [182]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl8/igt@runner@aborted.html [183]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl4/igt@runner@aborted.html [184]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_102916v2/shard-apl6/igt@runner@aborted.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375 [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274 [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278 [fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279 [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#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291 [fdo#109293]: https://bugs.freedesktop.org/show_bug.cgi?id=109293 [fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295 [fdo#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300 [fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308 [fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309 [fdo#109314]: https://bugs.freedesktop.org/show_bug.cgi?id=109314 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506 [fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642 [fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189 [fdo#110542]: https://bugs.freedesktop.org/show_bug.cgi?id=110542 [fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723 [fdo#111066]: https://bugs.freedesktop.org/show_bug.cgi?id=111066 [fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068 [fdo#111314]: https://bugs.freedesktop.org/show_bug.cgi?id=111314 [fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614 [fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615 [fdo#111656]: https://bugs.freedesktop.org/show_bug.cgi?id=111656 [fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825 [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827 [fdo#112022]: https://bugs.freedesktop.org/show_bug.cgi?id=112022 [fdo#112054]: https://bugs.freedesktop.org/show_bug.cgi?id=112054 [fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283 [i915#1063]: https://gitlab.freedesktop.org/drm/intel/issues/1063 [i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072 [i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149 [i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155 [i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188 [i915#1257]: https://gitlab.freedesktop.org/drm/intel/issues/1257 [i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319 [i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132 [i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397 [i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722 [i915#1731]: https://gitlab.freedesktop.org/drm/intel/issues/1731 [i915#1755]: https://gitlab.freedesktop.org/drm/intel/issues/1755 [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 [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#1850]: https://gitlab.freedesktop.org/drm/intel/issues/1850 [i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888 [i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122 [i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190 [i915#2232]: https://gitlab.freedesktop.org/drm/intel/issues/2232 [i915#2410]: https://gitlab.freedesktop.org/drm/intel/issues/2410 [i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411 [i915#2436]: https://gitlab.freedesktop.org/drm/intel/issues/2436 [i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437 [i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527 [i915#2530]: https://gitlab.freedesktop.org/drm/intel/issues/2530 [i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582 [i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587 [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265 [i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681 [i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280 [i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842 [i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846 [i915#2849]: https://gitlab.freedesktop.org/drm/intel/issues/2849 [i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856 [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#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012 [i915#3070]: https://gitlab.freedesktop.org/drm/intel/issues/3070 [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#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291 [i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297 [i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299 [i915#3319]: https://gitlab.freedesktop.org/drm/intel/issues/3319 [i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359 [i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458 [i915#3464]: https://gitlab.freedesktop.org/drm/intel/issues/3464 [i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469 [i915#3515]: https://gitlab.freedesktop.org/drm/intel/issues/3515 [i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539 [i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555 [i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558 [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#3701]: https://gitlab.freedesktop.org/drm/intel/issues/3701 [i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708 [i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734 [i915#3736]: https://gitlab.freedesktop.org/drm/intel/issues/3736 [i915#3742]: https://gitlab.freedesktop.org/drm/intel/issues/3742 [i915#3777]: https://gitlab.freedesktop.org/drm/intel/issues/3777 [i915#3810]: https://gitlab.freedesktop.org/drm/intel/issues/3810 [i915#3826]: https://gitlab.freedesktop.org/drm/intel/issues/3826 [i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840 [i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886 [i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921 [i915#3936]: https://gitlab.freedesktop.org/drm/intel/issues/3936 [i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955 [i915#4032]: https://gitlab.freedesktop.org/drm/intel/issues/4032 [i915#4055]: https://gitlab.freedesktop.org/drm/intel/issues/4055 [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#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103 [i915#4148]: https://gitlab.freedesktop.org/drm/intel/issues/4148 [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#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270 [i915#4278]: https://gitlab.freedesktop.org/drm/intel/issues/4278 [i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281 [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312 [i915#4369]: https://gitlab.freedesktop.org/drm/intel/issues/4369 [i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525 [i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538 [i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454 [i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613 [i915#4771]: https://gitlab.freedesktop.org/drm/intel/issues/4771 [i915#4812]: https://gitlab.freedesktop.org/drm/intel/issues/4812 [i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833 [i915#4842]: https://gitlab.freedesktop.org/drm/intel/issues/4842 [i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852 [i915#4853]: https://gitlab.freedesktop.org/drm/intel/issues/4853 [i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860 [i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873 [i915#4877]: https://gitlab.freedesktop.org/drm/intel/issues/4877 [i915#4886]: https://gitlab.freedesktop.org/drm/intel/issues/4886 [i915#4893]: https://gitlab.freedesktop.org/drm/intel/issues/4893 [i915#5080]: https://gitlab.freedesktop.org/drm/intel/issues/5080 [i915#5098]: https://gitlab.freedesktop.org/drm/intel/issues/5098 [i915#5115]: https://gitlab.freedesktop.org/drm/intel/issues/5115 [i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176 [i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235 [i915#5257]: https://gitlab.freedesktop.org/drm/intel/issues/5257 [i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286 [i915#5287]: https://gitlab.freedesktop.org/drm/intel/issues/5287 [i915#5288]: https://gitlab.freedesktop.org/drm/intel/issues/5288 [i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289 [i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325 [i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533 [i915#5341]: https://gitlab.freedesktop.org/drm/intel/issues/5341 [i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439 [i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563 [i915#5614]: https://gitlab.freedesktop.org/drm/intel/issues/5614 [i915#5639]: https://gitlab.freedesktop.org/drm/intel/issues/5639 [i915#5691]: https://gitlab.freedesktop.org/drm/intel/issues/5691 [i915#5723]: https://gitlab.freedesktop.org/drm/intel/issues/5723 [i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658 [i915#768]: https://gitlab.freedesktop.org/drm/intel/issues/768 [i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79 Build changes ------------- * Linux: CI_DRM_11535 -> Patchwork_102916v2 CI-20190529: 20190529 CI_DRM_11535: a80d6006be30036b14f1bcf7346dcd2faaf199d5 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_6444: df584c804e3a44431b0e5ae21c190b6e9acb35ab @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_102916v2: a80d6006be30036b14f1bcf7346dcd2faaf199d5 @ 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_102916v2/index.html [-- Attachment #2: Type: text/html, Size: 55506 bytes --] ^ permalink raw reply [flat|nested] 24+ messages in thread
* [PATCH 0/4] Flat-CCS eviction enhancements @ 2022-04-21 11:37 Ramalingam C 0 siblings, 0 replies; 24+ messages in thread From: Ramalingam C @ 2022-04-21 11:37 UTC (permalink / raw) To: intel-gfx, dri-devel; +Cc: Hellstrom Thomas, Matthew Auld Flat-CCS eviction enhancements. Ramalingam C (4): drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking drm/i915/gt: optimize the ccs_sz calculation per chunk drm/i915/gt: Extend doc on Flat-CCS obj eviction uapi/drm/i915: Update the placement list impact on obj residency drivers/gpu/drm/i915/gt/intel_migrate.c | 78 ++++++++++++++----------- include/uapi/drm/i915_drm.h | 14 +++++ 2 files changed, 59 insertions(+), 33 deletions(-) -- 2.20.1 ^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2022-04-22 8:42 UTC | newest] Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-04-21 11:38 [PATCH 0/4] Flat-CCS eviction enhancements Ramalingam C 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C 2022-04-21 11:38 ` [PATCH 1/4] drm/i915/gt: GEM_BUG_ON unexpected NULL at scatterlist walking Ramalingam C 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C 2022-04-21 13:27 ` Hellstrom, Thomas 2022-04-21 13:27 ` [Intel-gfx] " Hellstrom, Thomas 2022-04-21 14:04 ` Ramalingam C 2022-04-21 14:04 ` [Intel-gfx] " Ramalingam C 2022-04-21 11:38 ` [Intel-gfx] [PATCH 2/4] drm/i915/gt: optimize the ccs_sz calculation per chunk Ramalingam C 2022-04-21 11:38 ` Ramalingam C 2022-04-21 11:38 ` [Intel-gfx] [PATCH 3/4] drm/i915/gt: Extend doc on Flat-CCS obj eviction Ramalingam C 2022-04-21 11:38 ` Ramalingam C 2022-04-21 13:37 ` Hellstrom, Thomas 2022-04-21 13:37 ` [Intel-gfx] " Hellstrom, Thomas 2022-04-22 8:43 ` Ramalingam C 2022-04-22 8:43 ` [Intel-gfx] " Ramalingam C 2022-04-21 11:38 ` [PATCH 4/4] uapi/drm/i915: Update the placement list impact on obj residency Ramalingam C 2022-04-21 11:38 ` [Intel-gfx] " Ramalingam C 2022-04-21 13:40 ` Hellstrom, Thomas 2022-04-21 13:40 ` [Intel-gfx] " Hellstrom, Thomas 2022-04-21 14:20 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Flat-CCS eviction enhancements (rev2) Patchwork 2022-04-21 14:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2022-04-21 18:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork -- strict thread matches above, loose matches on Subject: below -- 2022-04-21 11:37 [PATCH 0/4] Flat-CCS eviction enhancements Ramalingam C
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.