From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Sworo, George D" <george.d.sworo@intel.com>,
"Zhang, Rui" <rui.zhang@intel.com>,
"rafael@kernel.org" <rafael@kernel.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] powercap: intel_rapl: Add support for RAPTORLAKE_P
Date: Thu, 09 Jun 2022 15:10:57 -0700 [thread overview]
Message-ID: <448c7f1d3adbdc9c8eb71bba0ff7b547535d0e76.camel@linux.intel.com> (raw)
In-Reply-To: <abfe8223dd06766d4297cbef0728c84f1e7d3aed.camel@intel.com>
On Thu, 2022-06-09 at 21:47 +0000, Sworo, George D wrote:
> On Thu, 2022-06-09 at 14:02 -0700, srinivas pandruvada wrote:
> > On Thu, 2022-06-09 at 20:55 +0200, Rafael J. Wysocki wrote:
> > > Rui, Srinivas, should I take this one?
> > >
> > Yes.
> >
> > Not sure if the RAPL-MMIO driver is loaded on this system.
> >
> > George,
> >
> > What is the output of
> > lspci -vv -s :0:4.0
> >
> > If the device id is 0xA71D, then we have this change in the
> > upstream kernel. If not then we need to submit patch for that.
> >
> > Thanks,
> > Srinivas
> >
> Thanks for the quick review.
>
> the device id is 0xA71D
We have upstream patch for this ID. So we are good.
Thanks,
Srinivas
> is not avaible without this patch. But when
> add it i can see the ID. Below are the outputs
>
> Output from a kernel without this patch:
> -------------------------------------
> localhost ~ # lspci -vv -s :0:4.0
> 00:04.0 Signal processing controller: Intel Corporation Alder Lake
> Innovation Platform Framework Processor Participant (rev 03)
> Subsystem: Intel Corporation Device 7270
> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
>
> Output with this patch added:
> ----------------------------------------
> localhost ~ # lspci -vv -s :0:4.0
> 00:04.0 Signal processing controller: Intel Corporation Device a71d
>
> > > On Wed, Jun 1, 2022 at 9:22 PM <george.d.sworo@intel.com> wrote:
> > > > From: George D Sworo <george.d.sworo@intel.com>
> > > >
> > > > Add RAPTORLAKE_P to the list of supported processor model in
> > > > the
> > > > Intel
> > > >
> > > > RAPL power capping driver.
> > > >
> > > > Signed-off-by: George D Sworo <george.d.sworo@intel.com>
> > > > ---
> > > > drivers/powercap/intel_rapl_common.c | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/drivers/powercap/intel_rapl_common.c
> > > > b/drivers/powercap/intel_rapl_common.c
> > > > index a9c99d9e8b42..21d624f9f5fb 100644
> > > > --- a/drivers/powercap/intel_rapl_common.c
> > > > +++ b/drivers/powercap/intel_rapl_common.c
> > > > @@ -1109,6 +1109,7 @@ static const struct x86_cpu_id rapl_ids[]
> > > > __initconst = {
> > > > X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L,
> > > > &rapl_defaults_core),
> > > > X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_N,
> > > > &rapl_defaults_core),
> > > > X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE,
> > > > &rapl_defaults_core),
> > > > + X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P,
> > > > &rapl_defaults_core),
> > > > X86_MATCH_INTEL_FAM6_MODEL(SAPPHIRERAPIDS_X,
> > > > &rapl_defaults_spr_server),
> > > > X86_MATCH_INTEL_FAM6_MODEL(LAKEFIELD,
> > > > &rapl_defaults_core),
> > > >
> > > > --
> > > > 2.17.1
> > > >
next prev parent reply other threads:[~2022-06-09 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 19:22 [PATCH] powercap: intel_rapl: Add support for RAPTORLAKE_P george.d.sworo
2022-06-09 18:55 ` Rafael J. Wysocki
2022-06-09 21:02 ` srinivas pandruvada
2022-06-09 21:47 ` Sworo, George D
2022-06-09 22:10 ` srinivas pandruvada [this message]
2022-06-10 2:26 ` Zhang Rui
2022-06-10 2:32 ` Zhang Rui
2022-06-10 3:31 ` Sworo, George D
2022-06-21 14:49 ` Pawnikar, Sumeet R
2022-06-21 19:22 ` Sworo, George D
2022-07-05 19:01 ` 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=448c7f1d3adbdc9c8eb71bba0ff7b547535d0e76.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=george.d.sworo@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).