From: Avi Kivity <avi@redhat.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: linux-kernel@vger.kernel.org, zamsden@redhat.com,
Marcelo Tosatti <mtosatti@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] Fix preempt imbalance in kvm_timer_init()
Date: Sun, 12 Dec 2010 11:28:10 +0200 [thread overview]
Message-ID: <4D0495AA.4050600@redhat.com> (raw)
In-Reply-To: <1291920155.8141.4.camel@localhost.localdomain>
On 12/09/2010 08:42 PM, Thomas Meyer wrote:
> Signed-off-by: Thomas Meyer<thomas@m3y3r.de>
> ---
> arch/x86/kvm/x86.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index cdac9e5..2609c3d 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -4561,7 +4561,7 @@ static struct notifier_block kvmclock_cpu_notifier_block = {
>
> static void kvm_timer_init(void)
> {
> - int cpu;
> + int cpu = get_cpu();
>
> max_tsc_khz = tsc_khz;
> register_hotcpu_notifier(&kvmclock_cpu_notifier_block);
This eventually takes a mutex (in cpu_maps_update_begin()), so it can't
be called with preemption disabled.
> @@ -4569,13 +4569,14 @@ static void kvm_timer_init(void)
> #ifdef CONFIG_CPU_FREQ
> struct cpufreq_policy policy;
> memset(&policy, 0, sizeof(policy));
> - cpufreq_get_policy(&policy, get_cpu());
> + cpufreq_get_policy(&policy, cpu);
> if (policy.cpuinfo.max_freq)
> max_tsc_khz = policy.cpuinfo.max_freq;
> #endif
> cpufreq_register_notifier(&kvmclock_cpufreq_notifier_block,
> CPUFREQ_TRANSITION_NOTIFIER);
> }
> + put_cpu();
> pr_debug("kvm: max_tsc_khz = %ld\n", max_tsc_khz);
> for_each_online_cpu(cpu)
> smp_call_function_single(cpu, tsc_khz_changed, NULL, 1);
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-12-12 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 18:42 [PATCH] Fix preempt imbalance in kvm_timer_init() Thomas Meyer
2010-12-12 9:28 ` Avi Kivity [this message]
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=4D0495AA.4050600@redhat.com \
--to=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=x86@kernel.org \
--cc=zamsden@redhat.com \
/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