Op 31-03-16 om 13:26 schreef Maarten Lankhorst: > It turns out that preserving framebuffers after the rmfb call breaks > vmwgfx userspace. This was originally introduced because it was thought > nobody relied on the behavior, but unfortunately it seems there are > exceptions. > > drm_framebuffer_remove may fail with -EINTR now, so a straight revert > is impossible. There is no way to remove the framebuffer from the lists > and active planes without introducing a race because of the different > locking requirements. Instead call drm_framebuffer_remove from a > workqueue, which is unaffected by signals. > Ping?
- [PATCH] drm/core: Do not preserve framebuffer on rmfb, v... Maarten Lankhorst
- [PATCH] drm/core: Do not preserve framebuffer on rm... Maarten Lankhorst
- [PATCH] drm/core: Do not preserve framebuffer o... Maarten Lankhorst
- [PATCH] drm/core: Do not preserve framebuffer o... Daniel Vetter
- [REBASED PATCH] drm/core: Do not preserve f... Maarten Lankhorst
- [PATCH] drm/core: Do not preserve framebuffer o... Thomas Hellstrom
- [PATCH i-g-t] tests/kms: Add test for testi... Maarten Lankhorst
- [Intel-gfx] [PATCH i-g-t] tests/kms: Ad... Tvrtko Ursulin
- [Intel-gfx] [PATCH i-g-t] tests/km... Daniel Vetter
- [PATCH] drm/core: Do not preserve framebuff... Maarten Lankhorst
- [Intel-gfx] [PATCH] drm/core: Do not pr... Tvrtko Ursulin
- [Intel-gfx] [PATCH] drm/core: Do n... Daniel Vetter