From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] perf/core for v5.17
Date: Tue, 11 Jan 2022 21:21:16 +0000 [thread overview]
Message-ID: <Yd30zIQsKTJCyGgO@google.com> (raw)
In-Reply-To: <Yd2+Wqrl0ax2JQjg@zn.tnic>
On Tue, Jan 11, 2022, Borislav Petkov wrote:
> KVM: Move x86's perf guest info callbacks to generic KVM
This commit, e1bfc24577cc, introduces a new warning on arm64 with CONFIG_GUEST_PERF_EVENTS=n.
>> arch/arm64/kvm/arm.c:499:15: warning: no previous prototype for function 'kvm_arch_vcpu_get_ip' [-Wmissing-prototypes]
unsigned long kvm_arch_vcpu_get_ip(struct kvm_vcpu *vcpu)
I floated a potential fix[*], but we all lost track of it. I assume the easiest
solution at this point is to post a proper patch to go on top?
---
arch/arm64/kvm/arm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
index 8129ee1ed3a4..e3b46951a92d 100644
--- a/arch/arm64/kvm/arm.c
+++ b/arch/arm64/kvm/arm.c
@@ -496,10 +496,12 @@ bool kvm_arch_vcpu_in_kernel(struct kvm_vcpu *vcpu)
return vcpu_mode_priv(vcpu);
}
+#ifdef CONFIG_GUEST_PERF_EVENTS
unsigned long kvm_arch_vcpu_get_ip(struct kvm_vcpu *vcpu)
{
return *vcpu_pc(vcpu);
}
+#endif
/* Just ensure a guest exit from a particular CPU */
static void exit_vm_noop(void *info)
--
[*] https://lore.kernel.org/all/YZvysKFSLTxDzaBs@google.com/
next prev parent reply other threads:[~2022-01-11 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 17:28 Borislav Petkov
2022-01-11 21:21 ` Sean Christopherson [this message]
2022-01-11 21:28 ` Borislav Petkov
2022-01-13 0:45 ` pr-tracker-bot
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=Yd30zIQsKTJCyGgO@google.com \
--to=seanjc@google.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®