From: Thomas Gleixner <tglx@linutronix.de>
To: Igor Mammedov <imammedo@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
jacob.jun.pan@linux.intel.com, alan@linux.intel.com,
feng.tang@intel.com, konrad.wilk@oracle.com, avi@redhat.com,
glommer@redhat.com, johnstul@us.ibm.com, riel@redhat.com,
tj@kernel.org, kosaki.motohiro@jp.fujitsu.com,
akpm@linux-foundation.org
Subject: Re: [PATCH] Introduce x86_cpuinit.early_percpu_clock_init hook
Date: Tue, 7 Feb 2012 18:43:46 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1202071808340.2794@ionos> (raw)
In-Reply-To: <1328626364-22591-1-git-send-email-imammedo@redhat.com>
On Tue, 7 Feb 2012, Igor Mammedov wrote:
> When kvm guest uses kvmclock, it may hang on vcpu hot-plug.
> This is caused by an overflow in pvclock_get_nsec_offset,
>
> u64 delta = tsc - shadow->tsc_timestamp;
>
> which in turn is caused by an undefined values from percpu
> hv_clock that hasn't been initialized yet.
> Uninitialized clock on being booted cpu is accessed from
> start_secondary
> -> smp_callin
> -> smp_store_cpu_info
> -> identify_secondary_cpu
> -> mtrr_ap_init
> -> mtrr_restore
> -> stop_machine_from_inactive_cpu
> -> queue_stop_cpus_work
> ...
> -> sched_clock
> -> kvm_clock_read
> which is well before x86_cpuinit.setup_percpu_clockev call in
> start_secondary, where percpu clock is initialized.
>
> This patch introduces a hook that allows to setup/initialize
> per_cpu clock early and avoid overflow due to reading
> - undefined values
> - old values if cpu was offlined and then onlined again
>
> Another possible early user of this clock source is ftrace that
> accesses it to get timestamps for ring buffer entries. So if
> mtrr_ap_init is moved from identify_secondary_cpu to past
> x86_cpuinit.setup_percpu_clockev in start_secondary, ftrace
> may cause the same overflow/hang on cpu hot-plug anyway.
>
> More complete description of the problem:
> https://lkml.org/lkml/2012/2/2/101
>
> Credits to Marcelo Tosatti <mtosatti@redhat.com> for hook idea.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> ---
> arch/x86/include/asm/x86_init.h | 2 ++
> arch/x86/kernel/kvmclock.c | 4 +---
> arch/x86/kernel/smpboot.c | 1 +
> arch/x86/kernel/x86_init.c | 1 +
> 4 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/include/asm/x86_init.h b/arch/x86/include/asm/x86_init.h
> index 517d476..5d0afac 100644
> --- a/arch/x86/include/asm/x86_init.h
> +++ b/arch/x86/include/asm/x86_init.h
> @@ -145,9 +145,11 @@ struct x86_init_ops {
> /**
> * struct x86_cpuinit_ops - platform specific cpu hotplug setups
> * @setup_percpu_clockev: set up the per cpu clock event device
> + * @early_percpu_clock_init: early init of the per cpu clock event device
You initialize the per cpu clock, not the per cpu clock event
device. The latter is still initialized via setup_percpu_clockev().
Otherwise
Acked-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2012-02-07 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 14:52 [PATCH] Introduce x86_cpuinit.early_percpu_clock_init hook Igor Mammedov
2012-02-07 17:43 ` Thomas Gleixner [this message]
2012-02-07 19:47 ` Marcelo Tosatti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1202071808340.2794@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=avi@redhat.com \
--cc=feng.tang@intel.com \
--cc=glommer@redhat.com \
--cc=hpa@zytor.com \
--cc=imammedo@redhat.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=johnstul@us.ibm.com \
--cc=konrad.wilk@oracle.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox