summaryrefslogtreecommitdiffstats
path: root/arch/x86/xen
diff options
context:
space:
mode:
authorLiu, Jinsong <jinsong.liu@intel.com>2012-06-07 19:58:50 +0800
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2012-07-19 15:51:37 -0400
commita8fccdb0617386695a13ec742a61b5c935b63795 (patch)
tree9eaa0d5a3507ae03965457db9158cce801cdb5ca /arch/x86/xen
parentcef12ee52b054282461a6d5fe7742755fa6e3bd3 (diff)
downloadop-kernel-dev-a8fccdb0617386695a13ec742a61b5c935b63795.zip
op-kernel-dev-a8fccdb0617386695a13ec742a61b5c935b63795.tar.gz
x86, MCE, AMD: Adjust initcall sequence for xen
there are 3 funcs which need to be _initcalled in a logic sequence: 1. xen_late_init_mcelog 2. mcheck_init_device 3. threshold_init_device xen_late_init_mcelog must register xen_mce_chrdev_device before native mce_chrdev_device registration if running under xen platform; mcheck_init_device should be inited before threshold_init_device to initialize mce_device, otherwise a a NULL ptr dereference will cause panic. so we use following _initcalls 1. device_initcall(xen_late_init_mcelog); 2. device_initcall_sync(mcheck_init_device); 3. late_initcall(threshold_init_device); when running under xen, the initcall order is 1,2,3; on baremetal, we skip 1 and we do only 2 and 3. Acked-and-tested-by: Borislav Petkov <bp@amd64.org> Suggested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'arch/x86/xen')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud