summaryrefslogtreecommitdiffstats
path: root/arch/avr32/Kconfig.debug
diff options
context:
space:
mode:
authorDexuan Cui <decui@microsoft.com>2014-08-01 04:27:54 -0700
committerTomi Valkeinen <tomi.valkeinen@ti.com>2014-08-04 09:35:27 +0300
commit3686fe964285a9a0c25265f37ada117d47614f1e (patch)
treed1ac734487e1257c68959963b8c14915e53fa41e /arch/avr32/Kconfig.debug
parent1d5167b72ca05b2096760e1200fcd53b5f9a7562 (diff)
downloadblackbird-obmc-linux-3686fe964285a9a0c25265f37ada117d47614f1e.tar.gz
blackbird-obmc-linux-3686fe964285a9a0c25265f37ada117d47614f1e.zip
video: hyperv: hyperv_fb: refresh the VM screen by force on VM panic
Currently the VSC has no chance to notify the VSP of the dirty rectangle on VM panic because the notification work is done in a workqueue, and in panic() the kernel typically ends up in an infinite loop, and a typical kernel config has CONFIG_PREEMPT_VOLUNTARY=y and CONFIG_PREEMPT is not set, so a context switch can't happen in panic() and the workqueue won't have a chance to run. As a result, the VM Connection window can't refresh until it's closed and we re-connect to the VM. We can register a handler on panic_notifier_list: the handler can notify the VSC and switch the framebuffer driver to a "synchronous mode", meaning the VSC flushes any future framebuffer change to the VSP immediately. v2: removed the MS-TFS line in the commit message v3: remove some 'unlikely' markings v4: avoid global variables as Tomi Valkeinen suggested Cc: Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by: Dexuan Cui <decui@microsoft.com> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'arch/avr32/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud