From: "tip-bot2 for Kan Liang" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Kan Liang <kan.liang@linux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/core] perf/x86: Add new Alder Lake and Raptor Lake support
Date: Wed, 11 May 2022 19:47:05 -0000 [thread overview]
Message-ID: <165229842585.4207.14170896439135247906.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220504194413.1003071-1-kan.liang@linux.intel.com>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: c2a960f7c5741cc4f03b4e587afeb89ad53c32c5
Gitweb: https://git.kernel.org/tip/c2a960f7c5741cc4f03b4e587afeb89ad53c32c5
Author: Kan Liang <kan.liang@linux.intel.com>
AuthorDate: Wed, 04 May 2022 12:44:09 -07:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Wed, 11 May 2022 16:27:08 +02:00
perf/x86: Add new Alder Lake and Raptor Lake support
>From PMU's perspective, there is no difference for the new Alder Lake N
and Raptor Lake P.
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20220504194413.1003071-1-kan.liang@linux.intel.com
---
arch/x86/events/intel/core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
index fc7f458..955ae91 100644
--- a/arch/x86/events/intel/core.c
+++ b/arch/x86/events/intel/core.c
@@ -6216,7 +6216,9 @@ __init int intel_pmu_init(void)
case INTEL_FAM6_ALDERLAKE:
case INTEL_FAM6_ALDERLAKE_L:
+ case INTEL_FAM6_ALDERLAKE_N:
case INTEL_FAM6_RAPTORLAKE:
+ case INTEL_FAM6_RAPTORLAKE_P:
/*
* Alder Lake has 2 types of CPU, core and atom.
*
prev parent reply other threads:[~2022-05-11 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 19:44 [PATCH 1/5] perf/x86: Add new Alder Lake and Raptor Lake support kan.liang
2022-05-04 19:44 ` [PATCH 2/5] perf/x86/msr: " kan.liang
2022-05-11 19:47 ` [tip: perf/core] " tip-bot2 for Kan Liang
2022-05-04 19:44 ` [PATCH 3/5] perf/x86/cstate: " kan.liang
2022-05-11 19:47 ` [tip: perf/core] " tip-bot2 for Kan Liang
2022-05-04 19:44 ` [PATCH 4/5] perf/x86/uncore: Clean up uncore_pci_ids[] kan.liang
2022-05-11 19:47 ` [tip: perf/core] " tip-bot2 for Kan Liang
2022-05-04 19:44 ` [PATCH 5/5] perf/x86/uncore: Add new Alder Lake and Raptor Lake support kan.liang
2022-05-11 19:47 ` [tip: perf/core] " tip-bot2 for Kan Liang
2022-05-11 19:47 ` tip-bot2 for Kan Liang [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=165229842585.4207.14170896439135247906.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.