From: "Zhang, Rui" <rui.zhang@intel.com>
To: "rafael@kernel.org" <rafael@kernel.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
Subject: Re: [PATCH 03/15] powercap/intel_rapl: Support per Interface rapl_defaults
Date: Sun, 2 Apr 2023 07:40:48 +0000 [thread overview]
Message-ID: <0d85d86ffa9d9aee8f5cc83851dc07ccf16a5baa.camel@intel.com> (raw)
In-Reply-To: <CAJZ5v0iFP1A+yZfjgx-yXfV2c0+o1t9DAYsj-3YzzaqNfP9LVw@mail.gmail.com>
On Thu, 2023-03-30 at 19:54 +0200, Rafael J. Wysocki wrote:
> On Thu, Mar 16, 2023 at 4:41 PM Zhang Rui <rui.zhang@intel.com>
> wrote:
> > rapl_defaults is Interface specific.
> >
> > Although current MSR and MMIO Interface share the same
> > rapl_defaults,
> > new Interface like TPMI need its own rapl_defaults callbacks.
> >
> > Save the rapl_defaults information in the Interface private
> > structure.
> >
> > No functional change.
> >
> > Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> > ---
> > drivers/powercap/intel_rapl_common.c | 46 ++++++++++++++++++++--
> > ------
> > include/linux/intel_rapl.h | 2 ++
> > 2 files changed, 35 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/powercap/intel_rapl_common.c
> > b/drivers/powercap/intel_rapl_common.c
> > index 2d2c15eea8eb..56e8af2a1e6f 100644
> > --- a/drivers/powercap/intel_rapl_common.c
> > +++ b/drivers/powercap/intel_rapl_common.c
> > @@ -115,6 +115,11 @@ struct rapl_defaults {
> > };
> > static struct rapl_defaults *rapl_defaults;
> >
> > +static struct rapl_defaults *get_rpd(struct rapl_package *rp)
>
> I would replace "rpd" with "defaults" here and everywhere below in
> this patch.
sure, will update in next release.
thanks,
rui
next prev parent reply other threads:[~2023-04-02 7:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 15:38 [PATCH 0/15] powercap/intel_rapl: Introduce RAPL TPMI support Zhang Rui
2023-03-16 15:38 ` [PATCH 01/15] powercap/intel_rapl: Remove unused field in struct rapl_if_priv Zhang Rui
2023-03-16 15:38 ` [PATCH 02/15] powercap/intel_rapl: Allow probing without CPUID match Zhang Rui
2023-03-16 15:38 ` [PATCH 03/15] powercap/intel_rapl: Support per Interface rapl_defaults Zhang Rui
2023-03-30 17:54 ` Rafael J. Wysocki
2023-04-02 7:40 ` Zhang, Rui [this message]
2023-03-16 15:38 ` [PATCH 04/15] powercap/intel_rapl: Support per Interface primitive information Zhang Rui
2023-03-30 17:56 ` Rafael J. Wysocki
2023-04-02 7:43 ` Zhang, Rui
2023-04-03 17:51 ` Rafael J. Wysocki
2023-03-16 15:38 ` [PATCH 05/15] powercap/intel_rapl: Support per domain energy/power/time unit Zhang Rui
2023-03-16 15:38 ` [PATCH 06/15] powercap/intel_rapl: Use index to initialize primitive information Zhang Rui
2023-03-16 15:38 ` [PATCH 07/15] powercap/intel_rapl: Change primitive order Zhang Rui
2023-04-07 11:40 ` Rafael J. Wysocki
2023-03-16 15:38 ` [PATCH 08/15] powercap/intel_rapl: Use bitmap for Power Limits Zhang Rui
2023-03-16 15:38 ` [PATCH 09/15] powercap/intel_rapl: Cleanup Power Limits support Zhang Rui
2023-03-16 15:38 ` [PATCH 10/15] powercap/intel_rapl: Introduce per Power Limit lock Zhang Rui
2023-04-07 12:01 ` Rafael J. Wysocki
2023-03-16 15:38 ` [PATCH 11/15] powercap/intel_rapl: Remove redundant cpu parameter Zhang Rui
2023-03-16 15:38 ` [PATCH 12/15] powercap/intel_rapl: Make cpu optional for rapl_package Zhang Rui
2023-03-16 15:38 ` [PATCH 13/15] powercap/intel_rapl: Introduce RAPL I/F type Zhang Rui
2023-03-16 15:38 ` [PATCH 14/15] powercap/intel_rapl: Introduce core support for TPMI interface Zhang Rui
2023-03-16 15:38 ` [PATCH 15/15] powercap/intel_rapl_tpmi: Introduce RAPL TPMI interface driver Zhang Rui
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=0d85d86ffa9d9aee8f5cc83851dc07ccf16a5baa.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@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
all inboxes | Powered by JetHome®