xen/x86: Do not call xen_init_time_ops() until shared_info is initialized
authorBoris Ostrovsky <boris.ostrovsky@oracle.com>
Wed, 3 May 2017 20:20:51 +0000 (16:20 -0400)
committerJuergen Gross <jgross@suse.com>
Fri, 5 May 2017 08:43:15 +0000 (10:43 +0200)
Routines that are set by xen_init_time_ops() use shared_info's
pvclock_vcpu_time_info area. This area is not properly available until
shared_info is mapped in xen_setup_shared_info().

This became especially problematic due to commit dd759d93f4dd ("x86/timers:
Add simple udelay calibration") where we end up reading tsc_to_system_mul
from xen_dummy_shared_info (i.e. getting zero value) and then trying
to divide by it in pvclock_tsc_khz().

Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
arch/x86/xen/enlighten_pv.c
arch/x86/xen/time.c

index a1af4f68278f09ff0fe667214a782e32ef22380b..b5c54ab0e195733f837882de09e61aea0fe3649d 100644 (file)
@@ -974,6 +974,13 @@ void xen_setup_shared_info(void)
 #endif
 
        xen_setup_mfn_list_list();
+
+       /*
+        * Now that shared info is set up we can start using routines that
+        * point to pvclock area.
+        */
+       if (system_state == SYSTEM_BOOTING)
+               xen_init_time_ops();
 }
 
 /* This is called once we have the cpu_possible_mask */
@@ -1272,8 +1279,6 @@ asmlinkage __visible void __init xen_start_kernel(void)
        x86_init.oem.arch_setup = xen_arch_setup;
        x86_init.oem.banner = xen_banner;
 
-       xen_init_time_ops();
-
        /*
         * Set up some pagetable state before starting to set any ptes.
         */
index 090c7eb4dca9c43d5a52ff14e426a192349f7088..a1895a8e85c15753d4781c3ac72185b4c96a7d9d 100644 (file)
@@ -406,7 +406,7 @@ static void __init xen_time_init(void)
                pvclock_gtod_register_notifier(&xen_pvclock_gtod_notifier);
 }
 
-void __init xen_init_time_ops(void)
+void __ref xen_init_time_ops(void)
 {
        pv_time_ops = xen_time_ops;