From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Martin Schiller <ms@dev.tdt.de>,
tony.luck@intel.com, peterz@infradead.org, mingo@redhat.com,
acme@kernel.org, namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, tglx@linutronix.de, bp@alien8.de,
dave.hansen@linux.intel.com
Cc: x86@kernel.org, hpa@zytor.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, fe@dev.tdt.de
Subject: Re: [PATCH 0/3] perf/x86: Add Airmont NP
Date: Tue, 25 Nov 2025 15:44:25 +0800 [thread overview]
Message-ID: <e224b118-6595-4f03-8aad-862e47fde5fa@linux.intel.com> (raw)
In-Reply-To: <20251124074846.9653-1-ms@dev.tdt.de>
On 11/24/2025 3:48 PM, Martin Schiller wrote:
> From the perspective of Intel cstate, PMU and MSR the Airmont NP
> (aka Lightning Mountain) is identical to Airmont.
>
> This changes are taken from patched kernel sources of the MaxLinear SDK
> which can be found at https://github.com/maxlinear/linux
>
> Martin Schiller (3):
> perf/x86/msr: Add Airmont NP
> perf/x86/intel: Add Airmont NP
> perf/x86/cstate: Add Airmont NP
>
> arch/x86/events/intel/core.c | 1 +
> arch/x86/events/intel/cstate.c | 1 +
> arch/x86/events/msr.c | 1 +
> 3 files changed, 3 insertions(+)
The whole patch-set looks good to me.
Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
next prev parent reply other threads:[~2025-11-25 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 7:48 [PATCH 0/3] perf/x86: Add Airmont NP Martin Schiller
2025-11-24 7:48 ` [PATCH 1/3] perf/x86/msr: " Martin Schiller
2025-11-24 7:48 ` [PATCH 2/3] perf/x86/intel: " Martin Schiller
2025-11-24 7:48 ` [PATCH 3/3] perf/x86/cstate: " Martin Schiller
2025-11-25 7:44 ` Mi, Dapeng [this message]
2025-12-17 7:33 ` [PATCH 0/3] perf/x86: " Martin Schiller
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=e224b118-6595-4f03-8aad-862e47fde5fa@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fe@dev.tdt.de \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=ms@dev.tdt.de \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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).