linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Zhang Rui <rui.zhang@intel.com>, peterz@infradead.org
Cc: mingo@redhat.com, tglx@linutronix.de, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	ak@linux.intel.com
Subject: Re: [PATCH 1/2] perf/x86/rapl: Add support for Intel Arrow Lake
Date: Wed, 10 Apr 2024 09:20:08 -0400	[thread overview]
Message-ID: <55528313-d858-41d2-b438-77bbc0e514f0@linux.intel.com> (raw)
In-Reply-To: <20240410124554.448987-1-rui.zhang@intel.com>



On 2024-04-10 8:45 a.m., Zhang Rui wrote:
> Arrow Lake RAPL support is the same as previous Sky Lake.
> Add Arrow Lake model for RAPL.
> 
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>

The series looks good to me.

Reviewed-by: Kan Liang <kan.liang@linux.intel.com>

Thanks,
Kan
> ---
>  arch/x86/events/rapl.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/x86/events/rapl.c b/arch/x86/events/rapl.c
> index fb2b1961e5a3..6bfb78d5b37e 100644
> --- a/arch/x86/events/rapl.c
> +++ b/arch/x86/events/rapl.c
> @@ -808,6 +808,8 @@ static const struct x86_cpu_id rapl_model_match[] __initconst = {
>  	X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S,	&model_skl),
>  	X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE,		&model_skl),
>  	X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE_L,	&model_skl),
> +	X86_MATCH_INTEL_FAM6_MODEL(ARROWLAKE_H,		&model_skl),
> +	X86_MATCH_INTEL_FAM6_MODEL(ARROWLAKE,		&model_skl),
>  	{},
>  };
>  MODULE_DEVICE_TABLE(x86cpu, rapl_model_match);

      parent reply	other threads:[~2024-04-10 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 12:45 [PATCH 1/2] perf/x86/rapl: Add support for Intel Arrow Lake Zhang Rui
2024-04-10 12:45 ` [PATCH 2/2] perf/x86/rapl: Add support for Intel Lunar Lake Zhang Rui
2024-04-10 13:20 ` Liang, Kan [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=55528313-d858-41d2-b438-77bbc0e514f0@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=ak@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rui.zhang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).