diff options
| author | Daniel Vetter <[email protected]> | 2022-04-05 21:03:35 +0000 |
|---|---|---|
| committer | Daniel Vetter <[email protected]> | 2022-04-07 14:52:14 +0000 |
| commit | efc3acbc105af79bce2ccf97a6159255b7cf6b38 (patch) | |
| tree | 2fb68ffea5bce5f6f7fa19987ea4322414c2ce23 /drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | |
| parent | fbcon: untangle fbcon_exit (diff) | |
| download | kernel-efc3acbc105af79bce2ccf97a6159255b7cf6b38.tar.gz kernel-efc3acbc105af79bce2ccf97a6159255b7cf6b38.zip | |
fbcon: Maintain a private array of fb_info
Accessing the one in fbmem.c without taking the right locks is a bad
idea. Instead maintain our own private copy, which is fully protected
by console_lock() (like everything else in fbcon.c). That copy is
serialized through fbcon_fb_registered/unregistered() calls.
Also this means we do not need to hold a full fb_info reference, which
is nice because doing so would mean a refcount loop between the
console and the fb_info. But it's also not nice since it means
console_lock() must be held absolutely everywhere. Well strictly
speaking we could still try to do some refcounting games again by
calling get_fb_info before we drop the console_lock. But things will
get tricky.
Acked-by: Sam Ravnborg <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Cc: Daniel Vetter <[email protected]>
Cc: Tetsuo Handa <[email protected]>
Cc: Claudio Suarez <[email protected]>
Cc: Du Cheng <[email protected]>
Cc: Greg Kroah-Hartman <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c')
0 files changed, 0 insertions, 0 deletions
