From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH 3.2] KVM: Make KVM_INTEL depend on CPU_SUP_INTEL
Date: Fri, 16 Dec 2011 14:22:48 -0200 [thread overview]
Message-ID: <20111216162248.GA32059@amt.cnet> (raw)
In-Reply-To: <1323858467-23537-1-git-send-email-avi@redhat.com>
On Wed, Dec 14, 2011 at 12:27:47PM +0200, 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>
Applied, thanks.
next prev parent reply other threads:[~2011-12-17 15:58 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 [this message]
2011-12-16 18:26 ` Randy Dunlap
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=20111216162248.GA32059@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
/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;
as well as URLs for NNTP newsgroup(s).