[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091009161552.fdbaf350.akpm@linux-foundation.org>
Date: Fri, 9 Oct 2009 16:15:52 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: Jiri Slaby <jirislaby@...il.com>, linux-kernel@...r.kernel.org,
Avi Kivity <avi@...hat.com>,
Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org,
Dave Jones <davej@...emonkey.org.uk>
Subject: Re: [was: mmotm 2009-10-09-01-07 uploaded]
On Fri, 9 Oct 2009 08:30:28 -0700
Randy Dunlap <rdunlap@...otime.net> wrote:
> From: Randy Dunlap <randy.dunlap@...cle.com>
>
> When CONFIG_CPU_FREQ is disabled, cpufreq_get() needs a stub.
> Used by kvm (although it looks like a bit of the kvm code could
> be omitted when CONFIG_CPU_FREQ is disabled).
>
> arch/x86/built-in.o: In function `kvm_arch_init':
> (.text+0x10de7): undefined reference to `cpufreq_get'
>
> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
> Tested-by: Eric Paris <eparis@...hat.com>
> ---
> include/linux/cpufreq.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> --- linux-next-20091006.orig/include/linux/cpufreq.h
> +++ linux-next-20091006/include/linux/cpufreq.h
> @@ -291,8 +291,15 @@ struct global_attr {
> int cpufreq_get_policy(struct cpufreq_policy *policy, unsigned int cpu);
> int cpufreq_update_policy(unsigned int cpu);
>
> +#ifdef CONFIG_CPU_FREQ
> /* query the current CPU frequency (in kHz). If zero, cpufreq couldn't detect it */
> unsigned int cpufreq_get(unsigned int cpu);
> +#else
> +static inline unsigned int cpufreq_get(unsigned int cpu)
> +{
> + return 0;
> +}
> +#endif
Thanks. I'll merge this into mainline in the next batch I think. It's
only needed by the KVM development tree but it's the correct thing to
do anyway and having it in minaline will simplify life for everyone.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists