summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>2015-02-25 18:27:19 +0200
committerLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>2015-03-03 16:16:30 +0200
commit5ee5a81df57ea3a19a5e306fdf8244ab696c8916 (patch)
tree3ad94723cd456fccf232536326ba303aad9a3595 /Makefile
parent48596d502e93a62fd1adab42b0a923709cd1c115 (diff)
downloadlinux-stable-5ee5a81df57ea3a19a5e306fdf8244ab696c8916.tar.gz
linux-stable-5ee5a81df57ea3a19a5e306fdf8244ab696c8916.tar.bz2
linux-stable-5ee5a81df57ea3a19a5e306fdf8244ab696c8916.zip
drm: rcar-du: Fix race condition in hardware plane allocator
The plane allocator has been inherently racy since the beginning of the transition to atomic updates, as the allocator lock is released between free plane check (at .atomic_check() time) and the reservation (at .atomic_update() time). To fix it, create a new allocator solely based on the atomic plane states without keeping any external state and perform allocation in the .atomic_check() handler. The core idea is to replace the free planes bitmask with a collective knowledge based on the allocated hardware plane(s) for each KMS plane. The allocator then loops over all plane states to compute the free planes bitmask, allocates hardware planes based on that bitmask, and stores the result back in the plane states. For this to work we need to access the current state of planes not touched by the atomic update. To ensure that it won't be modified, we need to lock all planes using drm_atomic_get_plane_state(). This effectively serializes atomic updates from .atomic_check() up to completion, either when swapping the states if the check step has succeeded, or when freeing the states if the check step has failed. Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions