Op 12-09-17 om 15:56 schreef Emil Velikov: > On 12 September 2017 at 14:37, Maarten Lankhorst > <maarten.lankhorst@xxxxxxxxxxxxxxx> wrote: >> When we want to make drm_atomic_commit interruptible, there are a lot of >> places that call the lock function, which we don't have control over. >> >> Rather than trying to convert every single one, it's easier to toggle >> interruptible waiting per acquire_ctx. If drm_modeset_acquire_init is >> called with DRM_MODESET_ACQUIRE_INTERRUPTIBLE, then we will perform >> interruptible waits in drm_modeset_lock and drm_modeset_backoff. >> >> Changes since v1: >> - Fix locking example in drm_modeset_lock.c to be compatible >> with interruptible waiting (xexaxo) and make it default. >> Uninterruptible waiting shouldn't happen except in corner cases, >> but the example will still apply if the flag is removed. >> - Add drm_modeset_lock_single_interruptible() to documentation. >> - Fix dead link to removed drm_modeset_lock_interruptible() in >> drm_modeset_lock(). >> >> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxxxx> >> Reviewed-by: Daniel Vetter <daniel.vetter@xxxxxxxx> #v1 >> Cc: Emil Velikov <emil.l.velikov@xxxxxxxxx> > Thanks for the documentation updates/fixes Maarten. FWIW the series is > Reviewed-by: Emil Velikov <emil.l.velikov@xxxxxxxxx> > > -Emil Thanks, applied. :) _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
