From: Randy Dunlap <rdunlap@xenotime.net>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 3.2] KVM: Make KVM_INTEL depend on CPU_SUP_INTEL
Date: Fri, 16 Dec 2011 10:26:49 -0800 [thread overview]
Message-ID: <4EEB8D69.3040003@xenotime.net> (raw)
In-Reply-To: <1323858467-23537-1-git-send-email-avi@redhat.com>
On 12/14/2011 02:27 AM, Avi Kivity wrote:
> PMU virtualization needs to talk to Intel-specific bits of perf; these are
> only available when CPU_SUP_INTEL=y.
>
> Fixes
>
> arch/x86/built-in.o: In function `atomic_switch_perf_msrs':
> vmx.c:(.text+0x6b1d4): undefined reference to `perf_guest_get_msrs'
>
> Reported-by: Ingo Molnar <mingo@elte.hu>
> Reported-by: Randy Dunlap <rdunlap@xenotime.net>
> Signed-off-by: Avi Kivity <avi@redhat.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
> ---
> arch/x86/kvm/Kconfig | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig
> index ff5790d..ca4d49e 100644
> --- a/arch/x86/kvm/Kconfig
> +++ b/arch/x86/kvm/Kconfig
> @@ -52,6 +52,8 @@ config KVM
> config KVM_INTEL
> tristate "KVM for Intel processors support"
> depends on KVM
> + # for perf_guest_get_msrs():
> + depends on CPU_SUP_INTEL
> ---help---
> Provides support for KVM on Intel processors equipped with the VT
> extensions.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-12-16 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 10:27 [PATCH 3.2] KVM: Make KVM_INTEL depend on CPU_SUP_INTEL Avi Kivity
2011-12-14 13:11 ` Avi Kivity
2011-12-16 16:22 ` Marcelo Tosatti
2011-12-16 18:26 ` Randy Dunlap [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=4EEB8D69.3040003@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.