Linux Power Management development
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 1/2] powercap: intel_rapl: Add support for MeteorLake platforms
Date: Sun, 11 Sep 2022 12:08:18 +0800	[thread overview]
Message-ID: <abe9bd8ca3620dae94b8788b62af53862f97c0f6.camel@intel.com> (raw)
In-Reply-To: <CAJZ5v0hPh21mgTLT6jZf4=bZqNbsLqFnu41j9G3K5TTo3=YKHQ@mail.gmail.com>

On Sat, 2022-09-10 at 18:44 +0200, Rafael J. Wysocki wrote:
> On Sat, Sep 10, 2022 at 3:12 PM Zhang Rui <rui.zhang@intel.com>
> wrote:
> > Add intel_rapl support for the MeteorLake platforms, which behave
> > the
> > same as RaptorLake platforms.
> > 
> > Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> > ---
> > 
> > Note:
> > This patch depends on commit 5515d21c6817
> > ("x86/cpu: Add CPU model numbers for Meteor Lake") in the
> > x86/urgent
> > branch of tip tree.
> 
> So I think I will have to rebase the powercap branch on top of a
> future -rc in order to apply this one.

Yeah, or we can wait for the next release cycle as this is not that
urgent.

thanks,
rui
> 
> > Note:
> > This patch is made on top of commit 0d7a23b5f8e1
> > ("powercap: intel_rapl: Add support for RAPTORLAKE_S") in the
> > linux-next branch of pm tree to avoid conflict.
> > 
> > ---
> >  drivers/powercap/intel_rapl_common.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/drivers/powercap/intel_rapl_common.c
> > b/drivers/powercap/intel_rapl_common.c
> > index 6812c1ca3100..949eb90f5733 100644
> > --- a/drivers/powercap/intel_rapl_common.c
> > +++ b/drivers/powercap/intel_rapl_common.c
> > @@ -1111,6 +1111,8 @@ static const struct x86_cpu_id rapl_ids[]
> > __initconst = {
> >         X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE,          &rapl_defau
> > lts_core),
> >         X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P,        &rapl_defau
> > lts_core),
> >         X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S,        &rapl_defau
> > lts_core),
> > +       X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE,          &rapl_defau
> > lts_core),
> > +       X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE_L,        &rapl_defau
> > lts_core),
> >         X86_MATCH_INTEL_FAM6_MODEL(SAPPHIRERAPIDS_X,    &rapl_defau
> > lts_spr_server),
> >         X86_MATCH_INTEL_FAM6_MODEL(LAKEFIELD,           &rapl_defau
> > lts_core),
> > 
> > --


      reply	other threads:[~2022-09-11  4:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10 13:15 [PATCH 1/2] powercap: intel_rapl: Add support for MeteorLake platforms Zhang Rui
2022-09-10 13:15 ` [PATCH 2/2] tools/power turbostat: " Zhang Rui
2022-09-10 16:44 ` [PATCH 1/2] powercap: intel_rapl: " Rafael J. Wysocki
2022-09-11  4:08   ` Zhang Rui [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=abe9bd8ca3620dae94b8788b62af53862f97c0f6.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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