From: Joe Perches <joe@perches.com>
To: Like Xu <like.xu@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Avi Kivity <avi@scylladb.com>
Cc: kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>,
like.xu@linux.inetl.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86/vPMU: refine kvm_pmu err msg when event creation failed
Date: Wed, 17 Jul 2019 22:18:46 -0700 [thread overview]
Message-ID: <9eda0e29f524275a217411ea81352271b782baa4.camel@perches.com> (raw)
In-Reply-To: <20190718044914.35631-1-like.xu@linux.intel.com>
On Thu, 2019-07-18 at 12:49 +0800, Like Xu wrote:
> If a perf_event creation fails due to any reason of the host perf
> subsystem, it has no chance to log the corresponding event for guest
> which may cause abnormal sampling data in guest result. In debug mode,
> this message helps to understand the state of vPMC and we should not
> limit the number of occurrences.
[]
> diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c
[]
> @@ -131,8 +131,8 @@ static void pmc_reprogram_counter(struct kvm_pmc *pmc, u32 type,
> intr ? kvm_perf_overflow_intr :
> kvm_perf_overflow, pmc);
> if (IS_ERR(event)) {
> - printk_once("kvm_pmu: event creation failed %ld\n",
> - PTR_ERR(event));
> + pr_debug("kvm_pmu: event creation failed %ld\n for pmc->idx = %d",
> + PTR_ERR(event), pmc->idx);
Perhaps this was written as printk_once to avoid
spamming the log with repeated messages.
Maybe this should use pr_debug_ratelimited.
(and it should also have a \n termination like:)
pr_debug_ratelimited("kvm_pmu: event creation failed %ld for pmc->idx = %d\n",
PTR_ERR(event), pmc->idx);
Perhaps Avi Kivity remembers why he wrote it this way.
https://lore.kernel.org/kvm/1305129333-7456-6-git-send-email-avi@redhat.com/
next prev parent reply other threads:[~2019-07-18 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 4:49 Like Xu
2019-07-18 5:18 ` Joe Perches [this message]
2019-07-18 5:45 ` Like Xu
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=9eda0e29f524275a217411ea81352271b782baa4.camel@perches.com \
--to=joe@perches.com \
--cc=avi@scylladb.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu@linux.inetl.com \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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
all inboxes | Powered by JetHome®