From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Kan Liang <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Sasha Levin <sashal@kernel.org>,
mingo@redhat.com, acme@kernel.org, tglx@linutronix.de,
bp@alien8.de, x86@kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH AUTOSEL 5.10 12/14] perf/x86/msr: Add Sapphire Rapids CPU support
Date: Wed, 20 Oct 2021 20:21:53 -0400 [thread overview]
Message-ID: <20211021002155.1129292-12-sashal@kernel.org> (raw)
In-Reply-To: <20211021002155.1129292-1-sashal@kernel.org>
From: Kan Liang <kan.liang@linux.intel.com>
[ Upstream commit 71920ea97d6d1d800ee8b51951dc3fda3f5dc698 ]
SMI_COUNT MSR is supported on Sapphire Rapids CPU.
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/1633551137-192083-1-git-send-email-kan.liang@linux.intel.com
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
arch/x86/events/msr.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/events/msr.c b/arch/x86/events/msr.c
index 4be8f9cabd07..ca8ce64df2ce 100644
--- a/arch/x86/events/msr.c
+++ b/arch/x86/events/msr.c
@@ -68,6 +68,7 @@ static bool test_intel(int idx, void *data)
case INTEL_FAM6_BROADWELL_D:
case INTEL_FAM6_BROADWELL_G:
case INTEL_FAM6_BROADWELL_X:
+ case INTEL_FAM6_SAPPHIRERAPIDS_X:
case INTEL_FAM6_ATOM_SILVERMONT:
case INTEL_FAM6_ATOM_SILVERMONT_D:
--
2.33.0
next prev parent reply other threads:[~2021-10-21 0:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 0:21 [PATCH AUTOSEL 5.10 01/14] gcc-plugins/structleak: add makefile var for disabling structleak Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 02/14] ALSA: hda: intel: Allow repeatedly probing on codec configuration errors Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 03/14] btrfs: deal with errors when checking if a dir entry exists during log replay Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 04/14] net: stmmac: add support for dwmac 3.40a Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 05/14] ARM: dts: spear3xx: Fix gmac node Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 06/14] nfc: nci: fix the UAF of rf_conn_info object Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 07/14] isdn: cpai: check ctr->cnr to avoid array index out of bound Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 08/14] isdn: mISDN: Fix sleeping function called from invalid context Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 09/14] platform/x86: intel_scu_ipc: Update timeout value in comment Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 10/14] ALSA: hda: avoid write to STATESTS if controller is in reset Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 11/14] libperf tests: Fix test_stat_cpu Sasha Levin
2021-10-21 0:21 ` Sasha Levin [this message]
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 13/14] Input: snvs_pwrkey - add clk handling Sasha Levin
2021-10-21 0:21 ` [PATCH AUTOSEL 5.10 14/14] Input: xpad - add support for another USB ID of Nacon GC-100 Sasha Levin
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=20211021002155.1129292-12-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=kan.liang@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=stable@vger.kernel.org \
--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