summaryrefslogtreecommitdiffstats
path: root/drivers/xen/privcmd.c
diff options
context:
space:
mode:
authorVaughan Cao <vaughan.cao@oracle.com>2013-08-16 16:10:56 +0800
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2013-08-20 15:37:03 -0400
commit669b0ae961e87c824233475e987b2d39996d4849 (patch)
treefafef462ed8610212fe86533daa075281ee5879a /drivers/xen/privcmd.c
parentee0726407feaf504dff304fb603652fb2d778b42 (diff)
downloadlinux-669b0ae961e87c824233475e987b2d39996d4849.tar.bz2
xen/pvhvm: Initialize xen panic handler for PVHVM guests
kernel use callback linked in panic_notifier_list to notice others when panic happens. NORET_TYPE void panic(const char * fmt, ...){ ... atomic_notifier_call_chain(&panic_notifier_list, 0, buf); } When Xen becomes aware of this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but we only call it in xen_arch_setup which only be called by PV, this patch is necessary for PVHVM. Without this patch, setting 'on_crash=coredump-restart' in PVHVM guest config file won't lead a vmcore to be generate when the guest panics. It can be reproduced with 'echo c > /proc/sysrq-trigger'. Signed-off-by: Vaughan Cao <vaughan.cao@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Acked-by: Joe Jin <joe.jin@oracle.com>
Diffstat (limited to 'drivers/xen/privcmd.c')
0 files changed, 0 insertions, 0 deletions