* [PATCH] drm/selftests/mm: reduce per-function stack usage
@ 2020-05-29 20:15 ` Arnd Bergmann
0 siblings, 0 replies; 10+ messages in thread
From: Arnd Bergmann @ 2020-05-29 20:15 UTC (permalink / raw)
To: David Airlie, Daniel Vetter, Christian König, Nirmoy Das,
Chris Wilson
Cc: linux-kernel, dri-devel, kbuild test robot, Arnd Bergmann,
Tvrtko Ursulin
The check_reserve_boundaries() function has a large array on the stack,
over 500 bytes. It gets inlined into __igt_reserve, which has multiple
other large structures as well but stayed just under the stack size
warning limit of 1024 bytes until one more member got added to struct
drm_mm_node, causing a warning:
drivers/gpu/drm/selftests/test-drm_mm.c:371:12: error:
stack frame size of 1032 bytes in function '__igt_reserve' [-Werror,-Wframe-larger-than=]
As far as I can tell, this is not nice but will not be called from
a context that is already low for the kernel stack, so just annotate
the inner function as noinline_for_stack to ensure that each function
by itself stays under the warning limit.
Fixes: 0cdea4455acd ("drm/mm: optimize rb_hole_addr rbtree search")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
drivers/gpu/drm/selftests/test-drm_mm.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c
index 9aabe82dcd3a..30108c330db8 100644
--- a/drivers/gpu/drm/selftests/test-drm_mm.c
+++ b/drivers/gpu/drm/selftests/test-drm_mm.c
@@ -323,9 +323,8 @@ static bool expect_reserve_fail(struct drm_mm *mm, struct drm_mm_node *node)
return false;
}
-static bool check_reserve_boundaries(struct drm_mm *mm,
- unsigned int count,
- u64 size)
+static noinline_for_stack bool
+check_reserve_boundaries(struct drm_mm *mm, unsigned int count, u64 size)
{
const struct boundary {
u64 start, size;
--
2.26.2
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply related [flat|nested] 10+ messages in thread* [PATCH] drm/selftests/mm: reduce per-function stack usage @ 2020-05-29 20:15 ` Arnd Bergmann 0 siblings, 0 replies; 10+ messages in thread From: Arnd Bergmann @ 2020-05-29 20:15 UTC (permalink / raw) To: David Airlie, Daniel Vetter, Christian König, Nirmoy Das, Chris Wilson Cc: Arnd Bergmann, kbuild test robot, Tvrtko Ursulin, dri-devel, linux-kernel The check_reserve_boundaries() function has a large array on the stack, over 500 bytes. It gets inlined into __igt_reserve, which has multiple other large structures as well but stayed just under the stack size warning limit of 1024 bytes until one more member got added to struct drm_mm_node, causing a warning: drivers/gpu/drm/selftests/test-drm_mm.c:371:12: error: stack frame size of 1032 bytes in function '__igt_reserve' [-Werror,-Wframe-larger-than=] As far as I can tell, this is not nice but will not be called from a context that is already low for the kernel stack, so just annotate the inner function as noinline_for_stack to ensure that each function by itself stays under the warning limit. Fixes: 0cdea4455acd ("drm/mm: optimize rb_hole_addr rbtree search") Signed-off-by: Arnd Bergmann <arnd@arndb.de> --- drivers/gpu/drm/selftests/test-drm_mm.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c index 9aabe82dcd3a..30108c330db8 100644 --- a/drivers/gpu/drm/selftests/test-drm_mm.c +++ b/drivers/gpu/drm/selftests/test-drm_mm.c @@ -323,9 +323,8 @@ static bool expect_reserve_fail(struct drm_mm *mm, struct drm_mm_node *node) return false; } -static bool check_reserve_boundaries(struct drm_mm *mm, - unsigned int count, - u64 size) +static noinline_for_stack bool +check_reserve_boundaries(struct drm_mm *mm, unsigned int count, u64 size) { const struct boundary { u64 start, size; -- 2.26.2 ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH] drm/selftests/mm: reduce per-function stack usage 2020-05-29 20:15 ` Arnd Bergmann (?) @ 2020-05-29 20:26 ` Chris Wilson 2020-05-29 20:43 ` Arnd Bergmann -1 siblings, 1 reply; 10+ messages in thread From: Chris Wilson @ 2020-05-29 20:26 UTC (permalink / raw) To: Christian König, Arnd Bergmann, Daniel Vetter, David Airlie, Nirmoy Das Cc: linux-kernel, dri-devel, kbuild test robot, Arnd Bergmann, Tvrtko Ursulin Quoting Arnd Bergmann (2020-05-29 21:15:26) > The check_reserve_boundaries() function has a large array on the stack, > over 500 bytes. It gets inlined into __igt_reserve, which has multiple > other large structures as well but stayed just under the stack size > warning limit of 1024 bytes until one more member got added to struct > drm_mm_node, causing a warning: > > drivers/gpu/drm/selftests/test-drm_mm.c:371:12: error: > stack frame size of 1032 bytes in function '__igt_reserve' [-Werror,-Wframe-larger-than=] > > As far as I can tell, this is not nice but will not be called from > a context that is already low for the kernel stack, so just annotate > the inner function as noinline_for_stack to ensure that each function > by itself stays under the warning limit. > > Fixes: 0cdea4455acd ("drm/mm: optimize rb_hole_addr rbtree search") > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > --- > drivers/gpu/drm/selftests/test-drm_mm.c | 5 ++--- > 1 file changed, 2 insertions(+), 3 deletions(-) > > diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c > index 9aabe82dcd3a..30108c330db8 100644 > --- a/drivers/gpu/drm/selftests/test-drm_mm.c > +++ b/drivers/gpu/drm/selftests/test-drm_mm.c > @@ -323,9 +323,8 @@ static bool expect_reserve_fail(struct drm_mm *mm, struct drm_mm_node *node) > return false; > } > > -static bool check_reserve_boundaries(struct drm_mm *mm, > - unsigned int count, > - u64 size) > +static noinline_for_stack bool > +check_reserve_boundaries(struct drm_mm *mm, unsigned int count, u64 size) > { > const struct boundary { It's this const [] right? Hmm, if we felt adventurous that could be a small set of multiplication factors (0, -1, 1, count, count+1, ...) and made static. -Chris _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] drm/selftests/mm: reduce per-function stack usage 2020-05-29 20:26 ` Chris Wilson @ 2020-05-29 20:43 ` Arnd Bergmann 0 siblings, 0 replies; 10+ messages in thread From: Arnd Bergmann @ 2020-05-29 20:43 UTC (permalink / raw) To: Chris Wilson Cc: kbuild test robot, Tvrtko Ursulin, David Airlie, linux-kernel@vger.kernel.org, dri-devel, Nirmoy Das, Christian König On Fri, May 29, 2020 at 10:26 PM Chris Wilson <chris@chris-wilson.co.uk> wrote: > Quoting Arnd Bergmann (2020-05-29 21:15:26) > > > > diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c > > index 9aabe82dcd3a..30108c330db8 100644 > > --- a/drivers/gpu/drm/selftests/test-drm_mm.c > > +++ b/drivers/gpu/drm/selftests/test-drm_mm.c > > @@ -323,9 +323,8 @@ static bool expect_reserve_fail(struct drm_mm *mm, struct drm_mm_node *node) > > return false; > > } > > > > -static bool check_reserve_boundaries(struct drm_mm *mm, > > - unsigned int count, > > - u64 size) > > +static noinline_for_stack bool > > +check_reserve_boundaries(struct drm_mm *mm, unsigned int count, u64 size) > > { > > const struct boundary { > > It's this const [] right? Hmm, if we felt adventurous that could be a > small set of multiplication factors (0, -1, 1, count, count+1, ...) and > made static. That was my first thought, but I couldn't figure out whether 'count' could be replaced by any compile-time constant. Arnd _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] drm/selftests/mm: reduce per-function stack usage @ 2020-05-29 20:43 ` Arnd Bergmann 0 siblings, 0 replies; 10+ messages in thread From: Arnd Bergmann @ 2020-05-29 20:43 UTC (permalink / raw) To: Chris Wilson Cc: Christian König, Daniel Vetter, David Airlie, Nirmoy Das, kbuild test robot, Tvrtko Ursulin, dri-devel, linux-kernel@vger.kernel.org On Fri, May 29, 2020 at 10:26 PM Chris Wilson <chris@chris-wilson.co.uk> wrote: > Quoting Arnd Bergmann (2020-05-29 21:15:26) > > > > diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c > > index 9aabe82dcd3a..30108c330db8 100644 > > --- a/drivers/gpu/drm/selftests/test-drm_mm.c > > +++ b/drivers/gpu/drm/selftests/test-drm_mm.c > > @@ -323,9 +323,8 @@ static bool expect_reserve_fail(struct drm_mm *mm, struct drm_mm_node *node) > > return false; > > } > > > > -static bool check_reserve_boundaries(struct drm_mm *mm, > > - unsigned int count, > > - u64 size) > > +static noinline_for_stack bool > > +check_reserve_boundaries(struct drm_mm *mm, unsigned int count, u64 size) > > { > > const struct boundary { > > It's this const [] right? Hmm, if we felt adventurous that could be a > small set of multiplication factors (0, -1, 1, count, count+1, ...) and > made static. That was my first thought, but I couldn't figure out whether 'count' could be replaced by any compile-time constant. Arnd ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] drm/selftests/mm: reduce per-function stack usage 2020-05-29 20:43 ` Arnd Bergmann (?) @ 2020-05-29 21:36 ` Chris Wilson -1 siblings, 0 replies; 10+ messages in thread From: Chris Wilson @ 2020-05-29 21:36 UTC (permalink / raw) To: Arnd Bergmann Cc: kbuild test robot, Tvrtko Ursulin, David Airlie, linux-kernel@vger.kernel.org, dri-devel, Nirmoy Das, Christian König Quoting Arnd Bergmann (2020-05-29 21:43:47) > On Fri, May 29, 2020 at 10:26 PM Chris Wilson <chris@chris-wilson.co.uk> wrote: > > Quoting Arnd Bergmann (2020-05-29 21:15:26) > > > > > > > diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c > > > index 9aabe82dcd3a..30108c330db8 100644 > > > --- a/drivers/gpu/drm/selftests/test-drm_mm.c > > > +++ b/drivers/gpu/drm/selftests/test-drm_mm.c > > > @@ -323,9 +323,8 @@ static bool expect_reserve_fail(struct drm_mm *mm, struct drm_mm_node *node) > > > return false; > > > } > > > > > > -static bool check_reserve_boundaries(struct drm_mm *mm, > > > - unsigned int count, > > > - u64 size) > > > +static noinline_for_stack bool > > > +check_reserve_boundaries(struct drm_mm *mm, unsigned int count, u64 size) > > > { > > > const struct boundary { > > > > It's this const [] right? Hmm, if we felt adventurous that could be a > > small set of multiplication factors (0, -1, 1, count, count+1, ...) and > > made static. > > That was my first thought, but I couldn't figure out whether 'count' > could be replaced by any compile-time constant. I just realised I sent a sketch of a patch to the wrong place. If we replace struct boundary with { int start; int size; const char *name; } that should reduce it from 408 to 272. (Where start, size are the multiples.) Probably not worth the hassle, the saving is too small overall leaving it uncomfortably close to a future warning. Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> -Chris _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Intel-gfx] [PATCH] compact-test-array 2020-05-29 20:15 ` Arnd Bergmann (?) (?) @ 2020-05-29 20:34 ` Chris Wilson -1 siblings, 0 replies; 10+ messages in thread From: Chris Wilson @ 2020-05-29 20:34 UTC (permalink / raw) To: intel-gfx; +Cc: Chris Wilson Ok, so count was variable, how about something like this. By my back of the paper calcs this should reduce it from 408 bytes to 272 bytes. --- drivers/gpu/drm/selftests/test-drm_mm.c | 42 ++++++++++++------------- 1 file changed, 20 insertions(+), 22 deletions(-) diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c index 9aabe82dcd3a..fa643cc54b0b 100644 --- a/drivers/gpu/drm/selftests/test-drm_mm.c +++ b/drivers/gpu/drm/selftests/test-drm_mm.c @@ -323,32 +323,30 @@ static bool expect_reserve_fail(struct drm_mm *mm, struct drm_mm_node *node) return false; } -static bool check_reserve_boundaries(struct drm_mm *mm, - unsigned int count, - u64 size) +static bool check_reserve_boundaries(struct drm_mm *mm, int count, u64 size) { const struct boundary { - u64 start, size; + int start, size; const char *name; } boundaries[] = { #define B(st, sz) { (st), (sz), "{ " #st ", " #sz "}" } B(0, 0), - B(-size, 0), - B(size, 0), - B(size * count, 0), - B(-size, size), - B(-size, -size), - B(-size, 2*size), - B(0, -size), - B(size, -size), - B(count*size, size), - B(count*size, -size), - B(count*size, count*size), - B(count*size, -count*size), - B(count*size, -(count+1)*size), - B((count+1)*size, size), - B((count+1)*size, -size), - B((count+1)*size, -2*size), + B(-1, 0), + B(1, 0), + B(count, 0), + B(-1, 1), + B(-1, -1), + B(-1, 2), + B(0, -1), + B(1, -1), + B(count, 1), + B(count, -1), + B(count, count), + B(count, -count), + B(count, -(count + 1)), + B(count + 1, 1), + B(count + 1, -1), + B(count + 1, -2), #undef B }; struct drm_mm_node tmp = {}; @@ -357,8 +355,8 @@ static bool check_reserve_boundaries(struct drm_mm *mm, for (n = 0; n < ARRAY_SIZE(boundaries); n++) { if (!expect_reserve_fail(mm, set_node(&tmp, - boundaries[n].start, - boundaries[n].size))) { + boundaries[n].start * size, + boundaries[n].size * size))) { pr_err("boundary[%d:%s] failed, count=%u, size=%lld\n", n, boundaries[n].name, count, size); return false; -- 2.27.0.rc2 _______________________________________________ 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
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for compact-test-array 2020-05-29 20:15 ` Arnd Bergmann ` (2 preceding siblings ...) (?) @ 2020-05-29 22:20 ` Patchwork -1 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2020-05-29 22:20 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: compact-test-array URL : https://patchwork.freedesktop.org/series/77802/ State : warning == Summary == $ dim checkpatch origin/drm-tip 546e4806fc80 compact-test-array -:74: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s) total: 1 errors, 0 warnings, 0 checks, 60 lines checked _______________________________________________ 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 compact-test-array 2020-05-29 20:15 ` Arnd Bergmann ` (3 preceding siblings ...) (?) @ 2020-05-29 22:41 ` Patchwork -1 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2020-05-29 22:41 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: compact-test-array URL : https://patchwork.freedesktop.org/series/77802/ State : success == Summary == CI Bug Log - changes from CI_DRM_8556 -> Patchwork_17822 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/index.html Known issues ------------ Here are the changes found in Patchwork_17822 that come from known issues: ### IGT changes ### #### Possible fixes #### * igt@i915_selftest@live@active: - fi-bsw-n3050: [DMESG-FAIL][1] ([i915#541]) -> [PASS][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/fi-bsw-n3050/igt@i915_selftest@live@active.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/fi-bsw-n3050/igt@i915_selftest@live@active.html [i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541 Participating hosts (50 -> 44) ------------------------------ Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus Build changes ------------- * Linux: CI_DRM_8556 -> Patchwork_17822 CI-20190529: 20190529 CI_DRM_8556: a12abc504361cc53eeb53c2948aebbd88709a901 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5684: bd399f5eb8263bb4a84ae6a5bb1a13d329e0515d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_17822: 546e4806fc80f3557d3395a9a101d9c21e985323 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 546e4806fc80 compact-test-array == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/index.html _______________________________________________ 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 compact-test-array 2020-05-29 20:15 ` Arnd Bergmann ` (4 preceding siblings ...) (?) @ 2020-05-30 2:35 ` Patchwork -1 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2020-05-30 2:35 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: compact-test-array URL : https://patchwork.freedesktop.org/series/77802/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8556_full -> Patchwork_17822_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_17822_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_17822_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_17822_full: ### IGT changes ### #### Possible regressions #### * igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque: - shard-hsw: NOTRUN -> [DMESG-WARN][1] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-hsw6/igt@kms_cursor_crc@pipe-b-cursor-alpha-opaque.html Known issues ------------ Here are the changes found in Patchwork_17822_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@kms_big_fb@x-tiled-64bpp-rotate-0: - shard-glk: [PASS][2] -> [FAIL][3] ([i915#1119] / [i915#118] / [i915#95]) +1 similar issue [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-glk4/igt@kms_big_fb@x-tiled-64bpp-rotate-0.html [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-glk8/igt@kms_big_fb@x-tiled-64bpp-rotate-0.html * igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding: - shard-kbl: [PASS][4] -> [FAIL][5] ([i915#54]) [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-kbl2/igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-kbl1/igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding.html - shard-skl: [PASS][6] -> [FAIL][7] ([i915#54]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-skl2/igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-skl7/igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding.html - shard-apl: [PASS][8] -> [FAIL][9] ([i915#54]) [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl7/igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl8/igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding.html * igt@kms_cursor_crc@pipe-c-cursor-suspend: - shard-kbl: [PASS][10] -> [DMESG-WARN][11] ([i915#180]) +1 similar issue [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-kbl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-kbl2/igt@kms_cursor_crc@pipe-c-cursor-suspend.html * igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic: - shard-glk: [PASS][12] -> [FAIL][13] ([i915#72]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-glk9/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-glk4/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html * igt@kms_frontbuffer_tracking@fbc-suspend: - shard-kbl: [PASS][14] -> [DMESG-WARN][15] ([i915#180] / [i915#93] / [i915#95]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-suspend.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b: - shard-apl: [PASS][16] -> [DMESG-WARN][17] ([i915#180]) +1 similar issue [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl4/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: - shard-skl: [PASS][18] -> [FAIL][19] ([fdo#108145] / [i915#265]) [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-skl5/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-skl3/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html * igt@kms_psr@psr2_primary_page_flip: - shard-iclb: [PASS][20] -> [SKIP][21] ([fdo#109441]) +3 similar issues [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-iclb7/igt@kms_psr@psr2_primary_page_flip.html #### Possible fixes #### * {igt@gem_exec_reloc@basic-concurrent0}: - shard-glk: [FAIL][22] ([i915#1930]) -> [PASS][23] [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-glk6/igt@gem_exec_reloc@basic-concurrent0.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-glk9/igt@gem_exec_reloc@basic-concurrent0.html * igt@i915_pm_rpm@system-suspend-execbuf: - shard-tglb: [INCOMPLETE][24] ([i915#456]) -> [PASS][25] [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-tglb6/igt@i915_pm_rpm@system-suspend-execbuf.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-tglb1/igt@i915_pm_rpm@system-suspend-execbuf.html * igt@i915_suspend@fence-restore-untiled: - shard-kbl: [DMESG-WARN][26] ([i915#180] / [i915#93] / [i915#95]) -> [PASS][27] [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-kbl2/igt@i915_suspend@fence-restore-untiled.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-kbl7/igt@i915_suspend@fence-restore-untiled.html * igt@kms_big_fb@y-tiled-64bpp-rotate-0: - shard-glk: [FAIL][28] ([i915#1119] / [i915#118] / [i915#95]) -> [PASS][29] [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-glk8/igt@kms_big_fb@y-tiled-64bpp-rotate-0.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-glk7/igt@kms_big_fb@y-tiled-64bpp-rotate-0.html * igt@kms_color@pipe-a-ctm-blue-to-red: - shard-skl: [FAIL][30] ([i915#129]) -> [PASS][31] [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-skl8/igt@kms_color@pipe-a-ctm-blue-to-red.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-skl5/igt@kms_color@pipe-a-ctm-blue-to-red.html * igt@kms_cursor_crc@pipe-a-cursor-256x85-random: - shard-skl: [FAIL][32] ([i915#54]) -> [PASS][33] [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-skl1/igt@kms_cursor_crc@pipe-a-cursor-256x85-random.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-skl8/igt@kms_cursor_crc@pipe-a-cursor-256x85-random.html * igt@kms_cursor_crc@pipe-a-cursor-suspend: - shard-kbl: [DMESG-WARN][34] ([i915#180]) -> [PASS][35] +3 similar issues [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-suspend.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-suspend.html * igt@kms_cursor_legacy@2x-cursor-vs-flip-legacy: - shard-hsw: [INCOMPLETE][36] ([i915#1926] / [i915#61]) -> [PASS][37] [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-hsw7/igt@kms_cursor_legacy@2x-cursor-vs-flip-legacy.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-hsw6/igt@kms_cursor_legacy@2x-cursor-vs-flip-legacy.html * {igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2}: - shard-glk: [FAIL][38] ([i915#79]) -> [PASS][39] [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-glk1/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-glk8/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html * {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}: - shard-apl: [DMESG-WARN][40] ([i915#180]) -> [PASS][41] +3 similar issues [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html * igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-blt: - shard-iclb: [FAIL][42] ([i915#49]) -> [PASS][43] [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-blt.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-blt.html * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: - shard-skl: [FAIL][44] ([fdo#108145] / [i915#265]) -> [PASS][45] +1 similar issue [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-skl4/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-skl10/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html * igt@kms_plane_multiple@atomic-pipe-b-tiling-yf: - shard-glk: [INCOMPLETE][46] ([i915#1927] / [i915#58] / [k.org#198133]) -> [PASS][47] [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-glk2/igt@kms_plane_multiple@atomic-pipe-b-tiling-yf.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-glk4/igt@kms_plane_multiple@atomic-pipe-b-tiling-yf.html * igt@kms_psr@psr2_sprite_plane_move: - shard-iclb: [SKIP][48] ([fdo#109441]) -> [PASS][49] +5 similar issues [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-iclb7/igt@kms_psr@psr2_sprite_plane_move.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html #### Warnings #### * igt@kms_content_protection@legacy: - shard-apl: [DMESG-FAIL][50] ([fdo#110321]) -> [TIMEOUT][51] ([i915#1319] / [i915#1635]) [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl2/igt@kms_content_protection@legacy.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl2/igt@kms_content_protection@legacy.html * igt@kms_content_protection@lic: - shard-apl: [TIMEOUT][52] ([i915#1319] / [i915#1635]) -> [FAIL][53] ([fdo#110321]) [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl1/igt@kms_content_protection@lic.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl4/igt@kms_content_protection@lic.html * igt@kms_content_protection@srm: - shard-apl: [TIMEOUT][54] ([i915#1319]) -> [TIMEOUT][55] ([i915#1319] / [i915#1635]) [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl7/igt@kms_content_protection@srm.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl8/igt@kms_content_protection@srm.html * igt@kms_content_protection@uevent: - shard-kbl: [FAIL][56] ([i915#357]) -> [FAIL][57] ([i915#357] / [i915#93] / [i915#95]) [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-kbl3/igt@kms_content_protection@uevent.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-kbl6/igt@kms_content_protection@uevent.html - shard-apl: [FAIL][58] ([i915#357]) -> [FAIL][59] ([i915#357] / [i915#95]) [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl1/igt@kms_content_protection@uevent.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl6/igt@kms_content_protection@uevent.html * igt@kms_plane_alpha_blend@pipe-c-alpha-basic: - shard-apl: [FAIL][60] ([fdo#108145] / [i915#265] / [i915#95]) -> [FAIL][61] ([fdo#108145] / [i915#265]) [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8556/shard-apl7/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17822/shard-apl8/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321 [i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119 [i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118 [i915#129]: https://gitlab.freedesktop.org/drm/intel/issues/129 [i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319 [i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542 [i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635 [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 [i915#1926]: https://gitlab.freedesktop.org/drm/intel/issues/1926 [i915#1927]: https://gitlab.freedesktop.org/drm/intel/issues/1927 [i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928 [i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930 [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265 [i915#357]: https://gitlab.freedesktop.org/drm/intel/issues/357 [i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456 [i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49 [i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54 [i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58 [i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61 [i915#72]: https://gitlab.freedesktop.org/drm/intel/issues/72 [i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79 [i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93 [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95 [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133 Participating hosts (11 -> 11) ------------------------------ No changes in participating hosts Build changes ------------- * Linux: CI_DRM_8556 -> Patchwork_17822 CI-20190529: 20190529 CI_DRM_8556: a12abc504361cc53eeb53c2948aebbd88709a901 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5684: bd399f5eb8263bb4a84ae6a5bb1a13d329e0515d @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_17822: 546e4806fc80f3557d3395a9a101d9c21e985323 @ 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_17822/index.html _______________________________________________ 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:[~2020-05-30 2:35 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2020-05-29 20:15 [PATCH] drm/selftests/mm: reduce per-function stack usage Arnd Bergmann 2020-05-29 20:15 ` Arnd Bergmann 2020-05-29 20:26 ` Chris Wilson 2020-05-29 20:43 ` Arnd Bergmann 2020-05-29 20:43 ` Arnd Bergmann 2020-05-29 21:36 ` Chris Wilson 2020-05-29 20:34 ` [Intel-gfx] [PATCH] compact-test-array Chris Wilson 2020-05-29 22:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for compact-test-array Patchwork 2020-05-29 22:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2020-05-30 2:35 ` [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.