From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Rafael Wysocki <rafael.j.wysocki@intel.com>,
Linux PM <linux-pm@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powercap/rapl: lower warning level for domain detection
Date: Tue, 2 Sep 2014 10:57:18 -0700 [thread overview]
Message-ID: <20140902105718.7e9ec107@ultegra> (raw)
In-Reply-To: <2181254.mWuCKKqmQW@vostro.rjw.lan>
On Tue, 02 Sep 2014 01:48:40 +0200
"Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> On Thursday, August 28, 2014 09:56:08 PM Jacob Pan wrote:
> > Many CPUs do not support complete set of RAPL domains, as a
> > result this detection failed message is very misleading and
> > annoying. So loweab Pan <jacob.jun.pan@linux.intel.com>
>
> What about printing a (info-level) message if the RAPL domain *is*
> supported? That surely is more interesting?
>
yes, that is better. just sent out an updated patch with a different
Subject: [PATCH] powercap/rapl: change domain detection message
Thanks,
Jacob
> > ---
> > drivers/powercap/intel_rapl.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/powercap/intel_rapl.c
> > b/drivers/powercap/intel_rapl.c index b1cda6f..0b282e7 100644
> > --- a/drivers/powercap/intel_rapl.c
> > +++ b/drivers/powercap/intel_rapl.c
> > @@ -1169,7 +1169,7 @@ static int rapl_detect_domains(struct
> > rapl_package *rp, int cpu) if (!rapl_check_domain(cpu, i))
> > rp->domain_map |= 1 << i;
> > else
> > - pr_warn("RAPL domain %s detection
> > failed\n",
> > + pr_info("RAPL domain %s not supported\n",
> > rapl_domain_names[i]);
> > }
> > rp->nr_domains = bitmap_weight(&rp->domain_map,
> > RAPL_DOMAIN_MAX);
> >
>
[Jacob Pan]
prev parent reply other threads:[~2014-09-02 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 4:56 [PATCH] powercap/rapl: lower warning level for domain detection Jacob Pan
2014-09-01 23:48 ` Rafael J. Wysocki
2014-09-02 17:57 ` Jacob Pan [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=20140902105718.7e9ec107@ultegra \
--to=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.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