[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update (rev2)

== Series Details == Series: drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update (rev2) URL : https://patchwork.freedesktop.org/series/46104/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4451_full -> Patchwork_9584_full = == Summary - WARNING == Minor

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update (rev2)

== Series Details == Series: drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update (rev2) URL : https://patchwork.freedesktop.org/series/46104/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4451 -> Patchwork_9584 = == Summary - SUCCESS == No regressions f

[Intel-gfx] [PATCH v2] drm/i915: Use crtc_state->has_psr instead of CAN_PSR for pipe update

In commit "drm/i915: Wait for PSR exit before checking for vblank evasion", the idea was to limit the PSR IDLE checks when PSR is actually supported. While CAN_PSR does do that check, it doesn't applies on a per-crtc basis. crtc_state->has_psr is a more granular check that avoids everything but pip

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Prevent background reaping of active objects

/0day-ci/linux/commits/Chris-Wilson/drm-i915-selftests-Prevent-background-reaping-of-active-objects/20180708-204032 base: git://anongit.freedesktop.org/drm-intel for-linux-next config: i386-randconfig-a1-201827 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: # save

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/selftests: Prevent background reaping of active objects

== Series Details == Series: drm/i915/selftests: Prevent background reaping of active objects URL : https://patchwork.freedesktop.org/series/46124/ State : failure == Summary == CALLscripts/checksyscalls.sh DESCEND objtool CHK include/generated/compile.h CC [M] drivers/gpu/drm/

[Intel-gfx] [PATCH] drm/i915/selftests: Prevent background reaping of active objects

igt_mmap_offset_exhaustion() wants to test what happens when the mmap space is filled with zombie objects, objects discarded by userspace but still active on the GPU. As they are only protected by the active reference, we have to be certain that active reference is kept while we peek into our dangl