From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Yunfeng Ye <yeyunfeng@huawei.com>,
"Zhang, Rui" <rui.zhang@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hushiyuan@huawei.com, hewenliang4@huawei.com,
caihongda@huawei.com
Subject: Re: [PATCH 1/2] powercap/intel_rapl: Use topology interface in rapl_add_package()
Date: Fri, 05 Feb 2021 09:07:28 -0800 [thread overview]
Message-ID: <0f63aaa63cb4217f772aa702fac5c44a3ac110b6.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0hNryYqKfTZfRjN+KJVgw973G+vi9SrT4mGTPz_TTT2ng@mail.gmail.com>
On Fri, 2021-02-05 at 13:45 +0100, Rafael J. Wysocki wrote:
> On Sat, Jan 23, 2021 at 11:07 AM Yunfeng Ye <yeyunfeng@huawei.com>
> wrote:
> > It's not a good way to access phys_proc_id and cpu_die_id directly.
> > So using topology_physical_package_id(cpu) and topology_die_id(cpu)
> > instead.
> >
> > Signed-off-by: Yunfeng Ye <yeyunfeng@huawei.com>
>
> Srinivas, Rui, any concerns?
Looks good.
Thanks,
Srinivas
>
> > ---
> > drivers/powercap/intel_rapl_common.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/powercap/intel_rapl_common.c
> > b/drivers/powercap/intel_rapl_common.c
> > index c9e57237d778..5f3d39b8212a 100644
> > --- a/drivers/powercap/intel_rapl_common.c
> > +++ b/drivers/powercap/intel_rapl_common.c
> > @@ -1309,7 +1309,6 @@ struct rapl_package *rapl_add_package(int
> > cpu, struct rapl_if_priv *priv)
> > {
> > int id = topology_logical_die_id(cpu);
> > struct rapl_package *rp;
> > - struct cpuinfo_x86 *c = &cpu_data(cpu);
> > int ret;
> >
> > if (!rapl_defaults)
> > @@ -1326,10 +1325,11 @@ struct rapl_package *rapl_add_package(int
> > cpu, struct rapl_if_priv *priv)
> >
> > if (topology_max_die_per_package() > 1)
> > snprintf(rp->name, PACKAGE_DOMAIN_NAME_LENGTH,
> > - "package-%d-die-%d", c->phys_proc_id, c-
> > >cpu_die_id);
> > + "package-%d-die-%d",
> > + topology_physical_package_id(cpu),
> > topology_die_id(cpu));
> > else
> > snprintf(rp->name, PACKAGE_DOMAIN_NAME_LENGTH,
> > "package-%d",
> > - c->phys_proc_id);
> > + topology_physical_package_id(cpu));
> >
> > /* check if the package contains valid domains */
> > if (rapl_detect_domains(rp, cpu) || rapl_defaults-
> > >check_unit(rp, cpu)) {
> > --
> > 2.27.0
> >
next prev parent reply other threads:[~2021-02-05 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 10:06 Yunfeng Ye
2021-01-23 10:06 ` [PATCH 2/2] powercap/intel_rapl: Use topology interface in rapl_init_domains() Yunfeng Ye
2021-02-05 12:46 ` Rafael J. Wysocki
2021-02-05 17:07 ` Srinivas Pandruvada
2021-02-05 12:45 ` [PATCH 1/2] powercap/intel_rapl: Use topology interface in rapl_add_package() Rafael J. Wysocki
2021-02-05 17:07 ` Srinivas Pandruvada [this message]
2021-02-12 15:54 ` Rafael J. Wysocki
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=0f63aaa63cb4217f772aa702fac5c44a3ac110b6.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=caihongda@huawei.com \
--cc=hewenliang4@huawei.com \
--cc=hushiyuan@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=yeyunfeng@huawei.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
Powered by JetHome