* [PATCH] drm/vgem: Use 256B aligned pitch @ 2021-06-30 12:02 ` Tejas Upadhyay 0 siblings, 0 replies; 10+ messages in thread From: Tejas Upadhyay @ 2021-06-30 12:02 UTC (permalink / raw) To: dri-devel; +Cc: intel-gfx, chris Having different alignment requirement by different drivers, 256B aligned should work for all drm drivers. Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com> --- drivers/gpu/drm/vgem/vgem_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c index bf38a7e319d1..1da6df5e256a 100644 --- a/drivers/gpu/drm/vgem/vgem_drv.c +++ b/drivers/gpu/drm/vgem/vgem_drv.c @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file *file, struct drm_device *dev, struct drm_gem_object *gem_object; u64 pitch, size; - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); size = args->height * pitch; if (size == 0) return -EINVAL; -- 2.31.1 ^ permalink raw reply related [flat|nested] 10+ messages in thread
* [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch @ 2021-06-30 12:02 ` Tejas Upadhyay 0 siblings, 0 replies; 10+ messages in thread From: Tejas Upadhyay @ 2021-06-30 12:02 UTC (permalink / raw) To: dri-devel; +Cc: intel-gfx, chris Having different alignment requirement by different drivers, 256B aligned should work for all drm drivers. Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com> --- drivers/gpu/drm/vgem/vgem_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c index bf38a7e319d1..1da6df5e256a 100644 --- a/drivers/gpu/drm/vgem/vgem_drv.c +++ b/drivers/gpu/drm/vgem/vgem_drv.c @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file *file, struct drm_device *dev, struct drm_gem_object *gem_object; u64 pitch, size; - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); size = args->height * pitch; if (size == 0) return -EINVAL; -- 2.31.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch 2021-06-30 12:02 ` [Intel-gfx] " Tejas Upadhyay @ 2021-06-30 12:21 ` Daniel Vetter -1 siblings, 0 replies; 10+ messages in thread From: Daniel Vetter @ 2021-06-30 12:21 UTC (permalink / raw) To: Tejas Upadhyay; +Cc: intel-gfx, dri-devel, chris On Wed, Jun 30, 2021 at 05:32:15PM +0530, Tejas Upadhyay wrote: > Having different alignment requirement by different drivers, > 256B aligned should work for all drm drivers. What. Like yes vgem abuses dumb_create, but it's not a kms driver. Pitch is meaningless, and that's why we align it minimally to 1 byte (bpp = bits per pixel here). Maybe start with explaining what you're trying to do here. -Daniel > > Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com> > --- > drivers/gpu/drm/vgem/vgem_drv.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c > index bf38a7e319d1..1da6df5e256a 100644 > --- a/drivers/gpu/drm/vgem/vgem_drv.c > +++ b/drivers/gpu/drm/vgem/vgem_drv.c > @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file *file, struct drm_device *dev, > struct drm_gem_object *gem_object; > u64 pitch, size; > > - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); > + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); > size = args->height * pitch; > if (size == 0) > return -EINVAL; > -- > 2.31.1 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch @ 2021-06-30 12:21 ` Daniel Vetter 0 siblings, 0 replies; 10+ messages in thread From: Daniel Vetter @ 2021-06-30 12:21 UTC (permalink / raw) To: Tejas Upadhyay; +Cc: intel-gfx, dri-devel, chris On Wed, Jun 30, 2021 at 05:32:15PM +0530, Tejas Upadhyay wrote: > Having different alignment requirement by different drivers, > 256B aligned should work for all drm drivers. What. Like yes vgem abuses dumb_create, but it's not a kms driver. Pitch is meaningless, and that's why we align it minimally to 1 byte (bpp = bits per pixel here). Maybe start with explaining what you're trying to do here. -Daniel > > Signed-off-by: Tejas Upadhyay <tejaskumarx.surendrakumar.upadhyay@intel.com> > --- > drivers/gpu/drm/vgem/vgem_drv.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c > index bf38a7e319d1..1da6df5e256a 100644 > --- a/drivers/gpu/drm/vgem/vgem_drv.c > +++ b/drivers/gpu/drm/vgem/vgem_drv.c > @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file *file, struct drm_device *dev, > struct drm_gem_object *gem_object; > u64 pitch, size; > > - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); > + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); > size = args->height * pitch; > if (size == 0) > return -EINVAL; > -- > 2.31.1 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch 2021-06-30 12:21 ` Daniel Vetter @ 2021-06-30 12:46 ` Surendrakumar Upadhyay, TejaskumarX -1 siblings, 0 replies; 10+ messages in thread From: Surendrakumar Upadhyay, TejaskumarX @ 2021-06-30 12:46 UTC (permalink / raw) To: Daniel Vetter; +Cc: intel-gfx, dri-devel, chris > -----Original Message----- > From: Daniel Vetter <daniel@ffwll.ch> > Sent: 30 June 2021 17:52 > To: Surendrakumar Upadhyay, TejaskumarX > <tejaskumarx.surendrakumar.upadhyay@intel.com> > Cc: dri-devel@lists.freedesktop.org; intel-gfx@lists.freedesktop.org; > chris@chris-wilson.co.uk > Subject: Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch > > On Wed, Jun 30, 2021 at 05:32:15PM +0530, Tejas Upadhyay wrote: > > Having different alignment requirement by different drivers, 256B > > aligned should work for all drm drivers. > > What. > > Like yes vgem abuses dumb_create, but it's not a kms driver. Pitch is > meaningless, and that's why we align it minimally to 1 byte (bpp = bits per > pixel here). > > Maybe start with explaining what you're trying to do here. > -Daniel > > Igt tool tests which are trying to exercise tests through VGEM are getting failure (if not 64B aligned) on Intel platforms in creating framebuffer as they need them to be 64B aligned. Then 64B alignment is not A requirement for all drm drivers. Thanks, Tejas > > Signed-off-by: Tejas Upadhyay > > <tejaskumarx.surendrakumar.upadhyay@intel.com> > > --- > > drivers/gpu/drm/vgem/vgem_drv.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c > > b/drivers/gpu/drm/vgem/vgem_drv.c index bf38a7e319d1..1da6df5e256a > > 100644 > > --- a/drivers/gpu/drm/vgem/vgem_drv.c > > +++ b/drivers/gpu/drm/vgem/vgem_drv.c > > @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file > *file, struct drm_device *dev, > > struct drm_gem_object *gem_object; > > u64 pitch, size; > > > > - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); > > + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); > > size = args->height * pitch; > > if (size == 0) > > return -EINVAL; > > -- > > 2.31.1 > > > > _______________________________________________ > > Intel-gfx mailing list > > Intel-gfx@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch @ 2021-06-30 12:46 ` Surendrakumar Upadhyay, TejaskumarX 0 siblings, 0 replies; 10+ messages in thread From: Surendrakumar Upadhyay, TejaskumarX @ 2021-06-30 12:46 UTC (permalink / raw) To: Daniel Vetter; +Cc: intel-gfx, dri-devel, chris > -----Original Message----- > From: Daniel Vetter <daniel@ffwll.ch> > Sent: 30 June 2021 17:52 > To: Surendrakumar Upadhyay, TejaskumarX > <tejaskumarx.surendrakumar.upadhyay@intel.com> > Cc: dri-devel@lists.freedesktop.org; intel-gfx@lists.freedesktop.org; > chris@chris-wilson.co.uk > Subject: Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch > > On Wed, Jun 30, 2021 at 05:32:15PM +0530, Tejas Upadhyay wrote: > > Having different alignment requirement by different drivers, 256B > > aligned should work for all drm drivers. > > What. > > Like yes vgem abuses dumb_create, but it's not a kms driver. Pitch is > meaningless, and that's why we align it minimally to 1 byte (bpp = bits per > pixel here). > > Maybe start with explaining what you're trying to do here. > -Daniel > > Igt tool tests which are trying to exercise tests through VGEM are getting failure (if not 64B aligned) on Intel platforms in creating framebuffer as they need them to be 64B aligned. Then 64B alignment is not A requirement for all drm drivers. Thanks, Tejas > > Signed-off-by: Tejas Upadhyay > > <tejaskumarx.surendrakumar.upadhyay@intel.com> > > --- > > drivers/gpu/drm/vgem/vgem_drv.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c > > b/drivers/gpu/drm/vgem/vgem_drv.c index bf38a7e319d1..1da6df5e256a > > 100644 > > --- a/drivers/gpu/drm/vgem/vgem_drv.c > > +++ b/drivers/gpu/drm/vgem/vgem_drv.c > > @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file > *file, struct drm_device *dev, > > struct drm_gem_object *gem_object; > > u64 pitch, size; > > > > - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); > > + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); > > size = args->height * pitch; > > if (size == 0) > > return -EINVAL; > > -- > > 2.31.1 > > > > _______________________________________________ > > Intel-gfx mailing list > > Intel-gfx@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch 2021-06-30 12:46 ` Surendrakumar Upadhyay, TejaskumarX @ 2021-06-30 14:03 ` Daniel Vetter -1 siblings, 0 replies; 10+ messages in thread From: Daniel Vetter @ 2021-06-30 14:03 UTC (permalink / raw) To: Surendrakumar Upadhyay, TejaskumarX; +Cc: intel-gfx, dri-devel, chris On Wed, Jun 30, 2021 at 12:46:27PM +0000, Surendrakumar Upadhyay, TejaskumarX wrote: > > > > -----Original Message----- > > From: Daniel Vetter <daniel@ffwll.ch> > > Sent: 30 June 2021 17:52 > > To: Surendrakumar Upadhyay, TejaskumarX > > <tejaskumarx.surendrakumar.upadhyay@intel.com> > > Cc: dri-devel@lists.freedesktop.org; intel-gfx@lists.freedesktop.org; > > chris@chris-wilson.co.uk > > Subject: Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch > > > > On Wed, Jun 30, 2021 at 05:32:15PM +0530, Tejas Upadhyay wrote: > > > Having different alignment requirement by different drivers, 256B > > > aligned should work for all drm drivers. > > > > What. > > > > Like yes vgem abuses dumb_create, but it's not a kms driver. Pitch is > > meaningless, and that's why we align it minimally to 1 byte (bpp = bits per > > pixel here). > > > > Maybe start with explaining what you're trying to do here. > > -Daniel > > > > > Igt tool tests which are trying to exercise tests through VGEM are getting failure (if not 64B aligned) on Intel platforms in creating framebuffer as they need them to be 64B aligned. Then 64B alignment is not > A requirement for all drm drivers. Fix the tests. We're not going to encode alignment constraints for all kms drivers in vgem, that's not what vgem is for. Really what we should have done is just give vgem an ioctl to allocate a buffer, with the size specified in bytes. Not this "abuse dumb_create" business we're doing. But that's a past mistake, can't really fix that. -Daniel > > Thanks, > Tejas > > > > Signed-off-by: Tejas Upadhyay > > > <tejaskumarx.surendrakumar.upadhyay@intel.com> > > > --- > > > drivers/gpu/drm/vgem/vgem_drv.c | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c > > > b/drivers/gpu/drm/vgem/vgem_drv.c index bf38a7e319d1..1da6df5e256a > > > 100644 > > > --- a/drivers/gpu/drm/vgem/vgem_drv.c > > > +++ b/drivers/gpu/drm/vgem/vgem_drv.c > > > @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file > > *file, struct drm_device *dev, > > > struct drm_gem_object *gem_object; > > > u64 pitch, size; > > > > > > - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); > > > + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); > > > size = args->height * pitch; > > > if (size == 0) > > > return -EINVAL; > > > -- > > > 2.31.1 > > > > > > _______________________________________________ > > > Intel-gfx mailing list > > > Intel-gfx@lists.freedesktop.org > > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > > > > -- > > Daniel Vetter > > Software Engineer, Intel Corporation > > http://blog.ffwll.ch -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch @ 2021-06-30 14:03 ` Daniel Vetter 0 siblings, 0 replies; 10+ messages in thread From: Daniel Vetter @ 2021-06-30 14:03 UTC (permalink / raw) To: Surendrakumar Upadhyay, TejaskumarX; +Cc: intel-gfx, dri-devel, chris On Wed, Jun 30, 2021 at 12:46:27PM +0000, Surendrakumar Upadhyay, TejaskumarX wrote: > > > > -----Original Message----- > > From: Daniel Vetter <daniel@ffwll.ch> > > Sent: 30 June 2021 17:52 > > To: Surendrakumar Upadhyay, TejaskumarX > > <tejaskumarx.surendrakumar.upadhyay@intel.com> > > Cc: dri-devel@lists.freedesktop.org; intel-gfx@lists.freedesktop.org; > > chris@chris-wilson.co.uk > > Subject: Re: [Intel-gfx] [PATCH] drm/vgem: Use 256B aligned pitch > > > > On Wed, Jun 30, 2021 at 05:32:15PM +0530, Tejas Upadhyay wrote: > > > Having different alignment requirement by different drivers, 256B > > > aligned should work for all drm drivers. > > > > What. > > > > Like yes vgem abuses dumb_create, but it's not a kms driver. Pitch is > > meaningless, and that's why we align it minimally to 1 byte (bpp = bits per > > pixel here). > > > > Maybe start with explaining what you're trying to do here. > > -Daniel > > > > > Igt tool tests which are trying to exercise tests through VGEM are getting failure (if not 64B aligned) on Intel platforms in creating framebuffer as they need them to be 64B aligned. Then 64B alignment is not > A requirement for all drm drivers. Fix the tests. We're not going to encode alignment constraints for all kms drivers in vgem, that's not what vgem is for. Really what we should have done is just give vgem an ioctl to allocate a buffer, with the size specified in bytes. Not this "abuse dumb_create" business we're doing. But that's a past mistake, can't really fix that. -Daniel > > Thanks, > Tejas > > > > Signed-off-by: Tejas Upadhyay > > > <tejaskumarx.surendrakumar.upadhyay@intel.com> > > > --- > > > drivers/gpu/drm/vgem/vgem_drv.c | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c > > > b/drivers/gpu/drm/vgem/vgem_drv.c index bf38a7e319d1..1da6df5e256a > > > 100644 > > > --- a/drivers/gpu/drm/vgem/vgem_drv.c > > > +++ b/drivers/gpu/drm/vgem/vgem_drv.c > > > @@ -215,7 +215,7 @@ static int vgem_gem_dumb_create(struct drm_file > > *file, struct drm_device *dev, > > > struct drm_gem_object *gem_object; > > > u64 pitch, size; > > > > > > - pitch = args->width * DIV_ROUND_UP(args->bpp, 8); > > > + pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 256); > > > size = args->height * pitch; > > > if (size == 0) > > > return -EINVAL; > > > -- > > > 2.31.1 > > > > > > _______________________________________________ > > > Intel-gfx mailing list > > > Intel-gfx@lists.freedesktop.org > > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx > > > > -- > > Daniel Vetter > > Software Engineer, Intel Corporation > > http://blog.ffwll.ch -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/vgem: Use 256B aligned pitch 2021-06-30 12:02 ` [Intel-gfx] " Tejas Upadhyay (?) (?) @ 2021-06-30 17:41 ` Patchwork -1 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2021-06-30 17:41 UTC (permalink / raw) To: Surendrakumar Upadhyay, TejaskumarX; +Cc: intel-gfx [-- Attachment #1.1: Type: text/plain, Size: 1955 bytes --] == Series Details == Series: drm/vgem: Use 256B aligned pitch URL : https://patchwork.freedesktop.org/series/92067/ State : success == Summary == CI Bug Log - changes from CI_DRM_10295 -> Patchwork_20492 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/index.html Known issues ------------ Here are the changes found in Patchwork_20492 that come from known issues: ### IGT changes ### #### Possible fixes #### * igt@prime_vgem@basic-fence-flip: - fi-bsw-kefka: [SKIP][1] ([fdo#109271]) -> [PASS][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/fi-bsw-kefka/igt@prime_vgem@basic-fence-flip.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/fi-bsw-kefka/igt@prime_vgem@basic-fence-flip.html - fi-snb-2520m: [SKIP][3] ([fdo#109271]) -> [PASS][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/fi-snb-2520m/igt@prime_vgem@basic-fence-flip.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/fi-snb-2520m/igt@prime_vgem@basic-fence-flip.html [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 Participating hosts (39 -> 36) ------------------------------ Missing (3): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus Build changes ------------- * Linux: CI_DRM_10295 -> Patchwork_20492 CI-20190529: 20190529 CI_DRM_10295: 683b7f160eb6993ccfc19e67e3c7111f12946bea @ git://anongit.freedesktop.org/gfx-ci/linux IGT_6124: 357d5477c93f2bdd3354afe91b89ccfd4ee4fd56 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git Patchwork_20492: fe15f53952c2cec06e3088b55450f758aa56a7e6 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == fe15f53952c2 drm/vgem: Use 256B aligned pitch == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/index.html [-- Attachment #1.2: Type: text/html, Size: 2645 bytes --] [-- Attachment #2: Type: text/plain, Size: 160 bytes --] _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/vgem: Use 256B aligned pitch 2021-06-30 12:02 ` [Intel-gfx] " Tejas Upadhyay ` (2 preceding siblings ...) (?) @ 2021-07-01 0:56 ` Patchwork -1 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2021-07-01 0:56 UTC (permalink / raw) To: Surendrakumar Upadhyay, TejaskumarX; +Cc: intel-gfx [-- Attachment #1.1: Type: text/plain, Size: 30255 bytes --] == Series Details == Series: drm/vgem: Use 256B aligned pitch URL : https://patchwork.freedesktop.org/series/92067/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10295_full -> Patchwork_20492_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_20492_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_20492_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_20492_full: ### IGT changes ### #### Possible regressions #### * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip: - shard-skl: NOTRUN -> [FAIL][1] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl5/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * igt@i915_pm_dc@dc6-psr: - {shard-rkl}: [FAIL][2] ([i915#2951]) -> [SKIP][3] [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@i915_pm_dc@dc6-psr.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@i915_pm_dc@dc6-psr.html * igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip: - {shard-rkl}: [PASS][4] -> [SKIP][5] +56 similar issues [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip-async-flip.html * igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_ccs: - {shard-rkl}: NOTRUN -> [FAIL][6] +7 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-5/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_ccs.html * igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_ccs: - {shard-rkl}: [FAIL][7] -> [SKIP][8] +11 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-1/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_ccs.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-6/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_ccs.html * igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc: - {shard-rkl}: [PASS][9] -> [FAIL][10] +8 similar issues [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_ccs@pipe-b-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html * igt@kms_ccs@pipe-c-bad-rotation-90-yf_tiled_ccs: - {shard-rkl}: [SKIP][11] -> [FAIL][12] +12 similar issues [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_ccs@pipe-c-bad-rotation-90-yf_tiled_ccs.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_ccs@pipe-c-bad-rotation-90-yf_tiled_ccs.html * igt@kms_ccs@pipe-d-crc-primary-basic-y_tiled_gen12_rc_ccs: - {shard-rkl}: [SKIP][13] ([i915#533]) -> [FAIL][14] +5 similar issues [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_ccs@pipe-d-crc-primary-basic-y_tiled_gen12_rc_ccs.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_ccs@pipe-d-crc-primary-basic-y_tiled_gen12_rc_ccs.html * igt@kms_content_protection@atomic: - {shard-rkl}: [SKIP][15] ([fdo#109300]) -> [SKIP][16] +1 similar issue [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_content_protection@atomic.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_content_protection@atomic.html * igt@kms_content_protection@dp-mst-type-0: - {shard-rkl}: [SKIP][17] ([i915#3116]) -> [SKIP][18] [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_content_protection@dp-mst-type-0.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_content_protection@dp-mst-type-0.html * igt@kms_cursor_crc@pipe-a-cursor-32x10-onscreen: - {shard-rkl}: [SKIP][19] ([i915#3359]) -> [SKIP][20] +6 similar issues [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_cursor_crc@pipe-a-cursor-32x10-onscreen.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_cursor_crc@pipe-a-cursor-32x10-onscreen.html * igt@kms_cursor_crc@pipe-a-cursor-64x64-rapid-movement: - {shard-rkl}: [SKIP][21] ([fdo#112022]) -> [SKIP][22] +9 similar issues [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-5/igt@kms_cursor_crc@pipe-a-cursor-64x64-rapid-movement.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_cursor_crc@pipe-a-cursor-64x64-rapid-movement.html * igt@kms_cursor_crc@pipe-b-cursor-512x512-offscreen: - {shard-rkl}: [SKIP][23] ([fdo#109279] / [i915#3359]) -> [SKIP][24] +1 similar issue [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_cursor_crc@pipe-b-cursor-512x512-offscreen.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_cursor_crc@pipe-b-cursor-512x512-offscreen.html * igt@kms_cursor_crc@pipe-c-cursor-32x32-offscreen: - {shard-rkl}: [SKIP][25] ([i915#3319]) -> [SKIP][26] +1 similar issue [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_cursor_crc@pipe-c-cursor-32x32-offscreen.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_cursor_crc@pipe-c-cursor-32x32-offscreen.html * igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled: - {shard-rkl}: [SKIP][27] ([fdo#111314]) -> [SKIP][28] [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-5/igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled.html * igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset: - {shard-rkl}: NOTRUN -> [SKIP][29] +19 similar issues [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset.html * igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile: - {shard-rkl}: [SKIP][30] -> [INCOMPLETE][31] [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile.html * igt@kms_frontbuffer_tracking@fbc-2p-indfb-fliptrack-mmap-gtt: - {shard-rkl}: [SKIP][32] ([fdo#111825]) -> [SKIP][33] [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-2p-indfb-fliptrack-mmap-gtt.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_frontbuffer_tracking@fbc-2p-indfb-fliptrack-mmap-gtt.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-fullscreen: - {shard-rkl}: [SKIP][34] ([i915#1849]) -> [SKIP][35] +38 similar issues [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-fullscreen.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-fullscreen.html * igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-blt: - {shard-rkl}: [SKIP][36] ([fdo#111825] / [i915#1825]) -> [SKIP][37] +7 similar issues [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-blt.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-blt.html * igt@kms_multipipe_modeset@basic-max-pipe-crc-check: - {shard-rkl}: [SKIP][38] ([i915#1839]) -> [SKIP][39] [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-6/igt@kms_multipipe_modeset@basic-max-pipe-crc-check.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-2/igt@kms_multipipe_modeset@basic-max-pipe-crc-check.html * igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4: - {shard-rkl}: [SKIP][40] ([i915#658]) -> [SKIP][41] +1 similar issue [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-6/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4.html * igt@kms_psr@psr2_sprite_plane_move: - {shard-rkl}: [SKIP][42] ([i915#1072]) -> [SKIP][43] +4 similar issues [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-5/igt@kms_psr@psr2_sprite_plane_move.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-1/igt@kms_psr@psr2_sprite_plane_move.html Known issues ------------ Here are the changes found in Patchwork_20492_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_create@create-massive: - shard-apl: NOTRUN -> [DMESG-WARN][44] ([i915#3002]) [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl6/igt@gem_create@create-massive.html * igt@gem_ctx_persistence@legacy-engines-hostile-preempt: - shard-snb: NOTRUN -> [SKIP][45] ([fdo#109271] / [i915#1099]) +3 similar issues [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-snb6/igt@gem_ctx_persistence@legacy-engines-hostile-preempt.html * igt@gem_ctx_sseu@engines: - shard-tglb: NOTRUN -> [SKIP][46] ([i915#280]) [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@gem_ctx_sseu@engines.html * igt@gem_eio@unwedge-stress: - shard-tglb: [PASS][47] -> [TIMEOUT][48] ([i915#2369] / [i915#3063] / [i915#3648]) [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-tglb7/igt@gem_eio@unwedge-stress.html [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb1/igt@gem_eio@unwedge-stress.html - shard-skl: [PASS][49] -> [TIMEOUT][50] ([i915#2369] / [i915#3063]) [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-skl5/igt@gem_eio@unwedge-stress.html [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl4/igt@gem_eio@unwedge-stress.html * igt@gem_exec_fair@basic-pace-share@rcs0: - shard-tglb: [PASS][51] -> [FAIL][52] ([i915#2842]) [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-tglb3/igt@gem_exec_fair@basic-pace-share@rcs0.html [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@gem_exec_fair@basic-pace-share@rcs0.html * igt@gem_exec_fair@basic-throttle@rcs0: - shard-iclb: [PASS][53] -> [FAIL][54] ([i915#2849]) [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-iclb8/igt@gem_exec_fair@basic-throttle@rcs0.html [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-iclb8/igt@gem_exec_fair@basic-throttle@rcs0.html * igt@gem_huc_copy@huc-copy: - shard-apl: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#2190]) [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl6/igt@gem_huc_copy@huc-copy.html * igt@gem_mmap_gtt@big-copy-xy: - shard-glk: [PASS][56] -> [FAIL][57] ([i915#307]) [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-glk6/igt@gem_mmap_gtt@big-copy-xy.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk7/igt@gem_mmap_gtt@big-copy-xy.html * igt@gem_pread@exhaustion: - shard-apl: NOTRUN -> [WARN][58] ([i915#2658]) +1 similar issue [58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl3/igt@gem_pread@exhaustion.html * igt@gem_pwrite@basic-exhaustion: - shard-snb: NOTRUN -> [WARN][59] ([i915#2658]) [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-snb7/igt@gem_pwrite@basic-exhaustion.html * igt@gem_userptr_blits@coherency-sync: - shard-tglb: NOTRUN -> [SKIP][60] ([fdo#110542]) [60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@gem_userptr_blits@coherency-sync.html * igt@gem_userptr_blits@vma-merge: - shard-apl: NOTRUN -> [FAIL][61] ([i915#3318]) [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl1/igt@gem_userptr_blits@vma-merge.html - shard-glk: NOTRUN -> [FAIL][62] ([i915#3318]) [62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk6/igt@gem_userptr_blits@vma-merge.html * igt@gem_vm_create@destroy-race: - shard-tglb: [PASS][63] -> [TIMEOUT][64] ([i915#2795]) [63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-tglb1/igt@gem_vm_create@destroy-race.html [64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb3/igt@gem_vm_create@destroy-race.html * igt@gen7_exec_parse@oacontrol-tracking: - shard-glk: NOTRUN -> [SKIP][65] ([fdo#109271]) +40 similar issues [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk6/igt@gen7_exec_parse@oacontrol-tracking.html * igt@gen9_exec_parse@allowed-single: - shard-tglb: NOTRUN -> [SKIP][66] ([fdo#112306]) [66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@gen9_exec_parse@allowed-single.html * igt@i915_pm_dc@dc5-psr: - shard-iclb: [PASS][67] -> [DMESG-WARN][68] ([i915#3698]) [67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-iclb2/igt@i915_pm_dc@dc5-psr.html [68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-iclb2/igt@i915_pm_dc@dc5-psr.html * igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp: - shard-apl: NOTRUN -> [SKIP][69] ([fdo#109271] / [i915#1937]) [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl3/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html * igt@i915_selftest@live@hangcheck: - shard-snb: NOTRUN -> [INCOMPLETE][70] ([i915#2782]) [70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-snb6/igt@i915_selftest@live@hangcheck.html * igt@kms_big_fb@yf-tiled-64bpp-rotate-270: - shard-tglb: NOTRUN -> [SKIP][71] ([fdo#111615]) +1 similar issue [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@kms_big_fb@yf-tiled-64bpp-rotate-270.html * igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0: - shard-apl: NOTRUN -> [SKIP][72] ([fdo#109271]) +328 similar issues [72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl8/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0.html * igt@kms_ccs@pipe-c-bad-rotation-90-yf_tiled_ccs: - shard-tglb: NOTRUN -> [SKIP][73] ([i915#3689]) +3 similar issues [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@kms_ccs@pipe-c-bad-rotation-90-yf_tiled_ccs.html * igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs: - shard-snb: NOTRUN -> [SKIP][74] ([fdo#109271]) +345 similar issues [74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-snb6/igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs.html * igt@kms_chamelium@hdmi-mode-timings: - shard-kbl: NOTRUN -> [SKIP][75] ([fdo#109271] / [fdo#111827]) +17 similar issues [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl1/igt@kms_chamelium@hdmi-mode-timings.html * igt@kms_chamelium@vga-hpd-for-each-pipe: - shard-glk: NOTRUN -> [SKIP][76] ([fdo#109271] / [fdo#111827]) +3 similar issues [76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk6/igt@kms_chamelium@vga-hpd-for-each-pipe.html * igt@kms_color_chamelium@pipe-a-ctm-blue-to-red: - shard-snb: NOTRUN -> [SKIP][77] ([fdo#109271] / [fdo#111827]) +15 similar issues [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-snb6/igt@kms_color_chamelium@pipe-a-ctm-blue-to-red.html * igt@kms_color_chamelium@pipe-b-degamma: - shard-tglb: NOTRUN -> [SKIP][78] ([fdo#109284] / [fdo#111827]) +1 similar issue [78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@kms_color_chamelium@pipe-b-degamma.html * igt@kms_color_chamelium@pipe-c-ctm-0-25: - shard-apl: NOTRUN -> [SKIP][79] ([fdo#109271] / [fdo#111827]) +30 similar issues [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl6/igt@kms_color_chamelium@pipe-c-ctm-0-25.html * igt@kms_color_chamelium@pipe-c-degamma: - shard-skl: NOTRUN -> [SKIP][80] ([fdo#109271] / [fdo#111827]) +4 similar issues [80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl3/igt@kms_color_chamelium@pipe-c-degamma.html * igt@kms_content_protection@atomic: - shard-kbl: NOTRUN -> [TIMEOUT][81] ([i915#1319]) +2 similar issues [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl6/igt@kms_content_protection@atomic.html * igt@kms_cursor_crc@pipe-a-cursor-suspend: - shard-kbl: [PASS][82] -> [INCOMPLETE][83] ([i915#155] / [i915#2828]) [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-kbl2/igt@kms_cursor_crc@pipe-a-cursor-suspend.html [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl3/igt@kms_cursor_crc@pipe-a-cursor-suspend.html * igt@kms_cursor_crc@pipe-b-cursor-32x32-rapid-movement: - shard-tglb: NOTRUN -> [SKIP][84] ([i915#3319]) [84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@kms_cursor_crc@pipe-b-cursor-32x32-rapid-movement.html * igt@kms_cursor_crc@pipe-d-cursor-suspend: - shard-kbl: NOTRUN -> [SKIP][85] ([fdo#109271]) +208 similar issues [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl3/igt@kms_cursor_crc@pipe-d-cursor-suspend.html * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size: - shard-skl: [PASS][86] -> [FAIL][87] ([i915#2346] / [i915#533]) [86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-skl9/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl6/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html * igt@kms_cursor_legacy@pipe-d-torture-bo: - shard-kbl: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#533]) +2 similar issues [88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl1/igt@kms_cursor_legacy@pipe-d-torture-bo.html * igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1: - shard-skl: [PASS][89] -> [FAIL][90] ([i915#79]) +1 similar issue [89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html [90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl2/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html * igt@kms_flip@flip-vs-suspend-interruptible@a-dp1: - shard-kbl: [PASS][91] -> [DMESG-WARN][92] ([i915#180]) +5 similar issues [91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-kbl6/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html [92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl4/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html - shard-apl: [PASS][93] -> [DMESG-WARN][94] ([i915#180]) [93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-apl8/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html [94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-render: - shard-glk: [PASS][95] -> [FAIL][96] ([i915#2546] / [i915#49]) [95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-glk5/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-render.html [96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk3/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-render.html * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-mmap-cpu: - shard-tglb: NOTRUN -> [SKIP][97] ([fdo#111825]) +3 similar issues [97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-mmap-cpu.html * igt@kms_hdr@bpc-switch-dpms: - shard-skl: [PASS][98] -> [FAIL][99] ([i915#1188]) [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-skl9/igt@kms_hdr@bpc-switch-dpms.html [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl6/igt@kms_hdr@bpc-switch-dpms.html * igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence: - shard-apl: NOTRUN -> [SKIP][100] ([fdo#109271] / [i915#533]) +3 similar issues [100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl2/igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-d: - shard-skl: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#533]) [101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-d.html * igt@kms_plane_alpha_blend@pipe-a-alpha-7efc: - shard-apl: NOTRUN -> [FAIL][102] ([fdo#108145] / [i915#265]) +3 similar issues [102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl1/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: - shard-skl: [PASS][103] -> [FAIL][104] ([fdo#108145] / [i915#265]) [103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html [104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl4/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html * igt@kms_plane_alpha_blend@pipe-c-alpha-basic: - shard-kbl: NOTRUN -> [FAIL][105] ([fdo#108145] / [i915#265]) +1 similar issue [105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl1/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html * igt@kms_plane_lowres@pipe-d-tiling-y: - shard-tglb: NOTRUN -> [SKIP][106] ([i915#3536]) [106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@kms_plane_lowres@pipe-d-tiling-y.html * igt@kms_plane_lowres@pipe-d-tiling-yf: - shard-skl: NOTRUN -> [SKIP][107] ([fdo#109271]) +49 similar issues [107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl3/igt@kms_plane_lowres@pipe-d-tiling-yf.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2: - shard-apl: NOTRUN -> [SKIP][108] ([fdo#109271] / [i915#658]) +6 similar issues [108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl8/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2.html * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3: - shard-kbl: NOTRUN -> [SKIP][109] ([fdo#109271] / [i915#658]) +3 similar issues [109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl7/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3.html * igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5: - shard-glk: NOTRUN -> [SKIP][110] ([fdo#109271] / [i915#658]) [110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk6/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5.html * igt@kms_psr@psr2_cursor_plane_move: - shard-iclb: [PASS][111] -> [SKIP][112] ([fdo#109441]) +2 similar issues [111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html [112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-iclb4/igt@kms_psr@psr2_cursor_plane_move.html * igt@kms_psr@psr2_primary_blt: - shard-tglb: NOTRUN -> [FAIL][113] ([i915#132] / [i915#3467]) [113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@kms_psr@psr2_primary_blt.html * igt@kms_writeback@writeback-check-output: - shard-apl: NOTRUN -> [SKIP][114] ([fdo#109271] / [i915#2437]) +2 similar issues [114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl6/igt@kms_writeback@writeback-check-output.html * igt@kms_writeback@writeback-invalid-parameters: - shard-skl: NOTRUN -> [SKIP][115] ([fdo#109271] / [i915#2437]) [115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl3/igt@kms_writeback@writeback-invalid-parameters.html - shard-kbl: NOTRUN -> [SKIP][116] ([fdo#109271] / [i915#2437]) [116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl6/igt@kms_writeback@writeback-invalid-parameters.html * igt@kms_writeback@writeback-pixel-formats: - shard-glk: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#2437]) [117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk6/igt@kms_writeback@writeback-pixel-formats.html * igt@nouveau_crc@pipe-d-source-rg: - shard-tglb: NOTRUN -> [SKIP][118] ([i915#2530]) [118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@nouveau_crc@pipe-d-source-rg.html * igt@prime_nv_api@i915_nv_import_vs_close: - shard-tglb: NOTRUN -> [SKIP][119] ([fdo#109291]) [119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb7/igt@prime_nv_api@i915_nv_import_vs_close.html * igt@syncobj_wait@wait-for-submit-snapshot: - shard-skl: [PASS][120] -> [FAIL][121] ([i915#3515]) [120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-skl4/igt@syncobj_wait@wait-for-submit-snapshot.html [121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl10/igt@syncobj_wait@wait-for-submit-snapshot.html * igt@sysfs_clients@fair-0: - shard-apl: NOTRUN -> [SKIP][122] ([fdo#109271] / [i915#2994]) +4 similar issues [122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-apl2/igt@sysfs_clients@fair-0.html * igt@sysfs_clients@fair-3: - shard-kbl: NOTRUN -> [SKIP][123] ([fdo#109271] / [i915#2994]) +3 similar issues [123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl6/igt@sysfs_clients@fair-3.html - shard-skl: NOTRUN -> [SKIP][124] ([fdo#109271] / [i915#2994]) [124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-skl3/igt@sysfs_clients@fair-3.html #### Possible fixes #### * igt@gem_ctx_isolation@preservation-s3@vecs0: - shard-kbl: [DMESG-WARN][125] ([i915#180]) -> [PASS][126] +8 similar issues [125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-kbl2/igt@gem_ctx_isolation@preservation-s3@vecs0.html [126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl3/igt@gem_ctx_isolation@preservation-s3@vecs0.html * igt@gem_ctx_persistence@many-contexts: - shard-tglb: [FAIL][127] ([i915#2410]) -> [PASS][128] [127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-tglb1/igt@gem_ctx_persistence@many-contexts.html [128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb3/igt@gem_ctx_persistence@many-contexts.html * igt@gem_exec_fair@basic-flow@rcs0: - shard-tglb: [FAIL][129] ([i915#2842]) -> [PASS][130] +1 similar issue [129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-tglb7/igt@gem_exec_fair@basic-flow@rcs0.html [130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-tglb5/igt@gem_exec_fair@basic-flow@rcs0.html * igt@gem_exec_fair@basic-none-rrul@rcs0: - shard-glk: [FAIL][131] ([i915#2842]) -> [PASS][132] [131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-glk6/igt@gem_exec_fair@basic-none-rrul@rcs0.html [132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-glk7/igt@gem_exec_fair@basic-none-rrul@rcs0.html * igt@gem_exec_fair@basic-pace-solo@rcs0: - shard-kbl: [FAIL][133] ([i915#2842]) -> [PASS][134] [133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-kbl3/igt@gem_exec_fair@basic-pace-solo@rcs0.html [134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl7/igt@gem_exec_fair@basic-pace-solo@rcs0.html * igt@gem_exec_fair@basic-pace@vcs1: - shard-kbl: [SKIP][135] ([fdo#109271]) -> [PASS][136] [135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-kbl1/igt@gem_exec_fair@basic-pace@vcs1.html [136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-kbl7/igt@gem_exec_fair@basic-pace@vcs1.html * igt@gem_mmap_gtt@cpuset-medium-copy: - {shard-rkl}: [FAIL][137] ([i915#2428]) -> [PASS][138] [137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10295/shard-rkl-1/igt@gem_mmap_gtt@cpuset-medium-copy.html [138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/shard-rkl-6/igt@gem_mmap_gtt@cpuset-medium-copy.html * igt@i915_pm_back == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20492/index.html [-- Attachment #1.2: Type: text/html, Size: 33432 bytes --] [-- Attachment #2: Type: text/plain, Size: 160 bytes --] _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2021-07-01 0:56 UTC | newest] Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-06-30 12:02 [PATCH] drm/vgem: Use 256B aligned pitch Tejas Upadhyay 2021-06-30 12:02 ` [Intel-gfx] " Tejas Upadhyay 2021-06-30 12:21 ` Daniel Vetter 2021-06-30 12:21 ` Daniel Vetter 2021-06-30 12:46 ` Surendrakumar Upadhyay, TejaskumarX 2021-06-30 12:46 ` Surendrakumar Upadhyay, TejaskumarX 2021-06-30 14:03 ` Daniel Vetter 2021-06-30 14:03 ` Daniel Vetter 2021-06-30 17:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork 2021-07-01 0:56 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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.