<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@kms_cursor_legacy@2x-(long-)?cursor-vs-flip-(legacy|atomic) - fail - Failed assertion: shared[child] > vrefresh[child]*target[child] / 2" href="https://bugs.freedesktop.org/show_bug.cgi?id=109079#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][DRMTIP] igt@kms_cursor_legacy@2x-(long-)?cursor-vs-flip-(legacy|atomic) - fail - Failed assertion: shared[child] > vrefresh[child]*target[child] / 2" href="https://bugs.freedesktop.org/show_bug.cgi?id=109079">bug 109079</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>(In reply to Neel from <a href="show_bug.cgi?id=109079#c3">comment #3</a>) > Due to the DDB allocation changes, we have to add all the planes in the > drm_atomic_state post gen 9. When the watermarks are computed by the kernel, > the cursor plane is added to the state. This introduces a dependency between > the code that processes DRM_IOCTL_MODE_ATOMIC and DRM_IOCTL_MODE_CURSOR. > This is a corner case and there is no race-free way to handle this. The > important thing is that we do not crash. These tests made sense < gen 9 but > now, we have to block all crtc updates during modeset. So, I will be > relaxing the test to skip the 2x-(long)cursor-vs-flip(atomic | legacy) > subtests for gen 9+ > > Patch underway... We use a fixed ddb allocation for the cursor. Hence its allocation should not change when other planes' allocations change.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>