diff options
author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2015-08-25 16:45:14 +0300 |
---|---|---|
committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2015-12-15 16:41:24 +0300 |
commit | c3c296b069dd84264cbaf7a0c4c13783e7508d50 (patch) | |
tree | a6e66ebae1cf330d046aa2bc57a9aa6e380cf88d /include/linux/fb.h | |
parent | 1c639baeafa5fe40e6b6e6ee99e9ddd29986fba1 (diff) | |
download | linux-c3c296b069dd84264cbaf7a0c4c13783e7508d50.tar.xz |
fbdev: Debug knob to register without holding console_lock
When the usual fbcon legacy options are enabled we have
->register_framebuffer
->fb notifier chain calls into fbcon
->fbcon sets up console on new fbi
->fbi->set_par
->drm_fb_helper_set_par exercises full kms api
And because of locking inversion hilarity all of register_framebuffer
is done with the console lock held. Which means that the first time on
driver load we exercise _all_ the kms code (all probe paths and
modeset paths for everything connected) is under the console lock.
That means if anything goes belly-up in that big pile of code nothing
ever reaches logfiles (and the machine is dead).
Usual tactic to debug that is to temporarily remove those console_lock
calls to be able to capture backtraces. I'm fed up writing this patch
and recompiling kernels. Hence this patch here to add an unsafe,
kernel-taining option to do this at runtime.
Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-fbdev@vger.kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'include/linux/fb.h')
0 files changed, 0 insertions, 0 deletions