From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Thomas Renninger <trenn@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
rjw@rjwysocki.net, linux-pm@vger.kernel.org,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH resend] intel_rapl: downgrade message if no RAPL domains found in a VM
Date: Tue, 19 Jul 2016 13:49:57 +0200 [thread overview]
Message-ID: <1468928997-20431-1-git-send-email-pbonzini@redhat.com> (raw)
People complain about the driver saying there's no valid RAPL domains
in a VM, and doing so at KERN_ERR severity. Downgrade this to KERN_INFO
if running on a hypervisor, since it is basically stating the obvious.
Suggested-by: Peter Zijlstra <peterz@infradead.org>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
First sent out about a year ago. :)
drivers/powercap/intel_rapl.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c
index b2766b867b0e..0a0b09910116 100644
--- a/drivers/powercap/intel_rapl.c
+++ b/drivers/powercap/intel_rapl.c
@@ -1392,7 +1392,9 @@ static int rapl_detect_domains(struct rapl_package *rp, int cpu)
}
rp->nr_domains = bitmap_weight(&rp->domain_map, RAPL_DOMAIN_MAX);
if (!rp->nr_domains) {
- pr_err("no valid rapl domains found in package %d\n", rp->id);
+ printk("%sNo valid RAPL domains found in package %d\n",
+ boot_cpu_has(X86_FEATURE_HYPERVISOR) ? KERN_INFO : KERN_ERR,
+ rp->id);
ret = -ENODEV;
goto done;
}
--
2.7.4
next reply other threads:[~2016-07-19 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 11:49 Paolo Bonzini [this message]
2016-07-19 12:27 ` [PATCH resend] intel_rapl: downgrade message if no RAPL domains found in a VM Jacob Pan
2016-07-21 13:19 ` Rafael J. Wysocki
2016-07-21 14:58 ` Paolo Bonzini
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=1468928997-20431-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=trenn@suse.de \
/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).