From: Rik van Riel <riel@surriel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, x86@kernel.org, kernel-team@meta.com,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, nadav.amit@gmail.com,
Rik van Riel <riel@fb.com>, Yu-cheng Yu <yu-cheng.yu@intel.com>,
Rik van Riel <riel@surriel.com>
Subject: [RFC v2 4/9] x86/mm: Introduce X86_FEATURE_RAR
Date: Mon, 19 May 2025 21:02:29 -0400 [thread overview]
Message-ID: <20250520010350.1740223-5-riel@surriel.com> (raw)
In-Reply-To: <20250520010350.1740223-1-riel@surriel.com>
From: Rik van Riel <riel@fb.com>
Introduce X86_FEATURE_RAR and enumeration of the feature.
[riel: moved initialization to intel.c and disabling to Kconfig.cpufeatures]
Signed-off-by: Yu-cheng Yu <yu-cheng.yu@intel.com>
Signed-off-by: Rik van Riel <riel@surriel.com>
---
arch/x86/Kconfig.cpufeatures | 4 ++++
arch/x86/include/asm/cpufeatures.h | 2 +-
arch/x86/kernel/cpu/common.c | 13 +++++++++++++
3 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/arch/x86/Kconfig.cpufeatures b/arch/x86/Kconfig.cpufeatures
index 250c10627ab3..7d459b5f47f7 100644
--- a/arch/x86/Kconfig.cpufeatures
+++ b/arch/x86/Kconfig.cpufeatures
@@ -195,3 +195,7 @@ config X86_DISABLED_FEATURE_SEV_SNP
config X86_DISABLED_FEATURE_INVLPGB
def_bool y
depends on !BROADCAST_TLB_FLUSH
+
+config X86_DISABLED_FEATURE_RAR
+ def_bool y
+ depends on !BROADCAST_TLB_FLUSH
diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h
index 5b50e0e35129..0729c2d54109 100644
--- a/arch/x86/include/asm/cpufeatures.h
+++ b/arch/x86/include/asm/cpufeatures.h
@@ -76,7 +76,7 @@
#define X86_FEATURE_K8 ( 3*32+ 4) /* Opteron, Athlon64 */
#define X86_FEATURE_ZEN5 ( 3*32+ 5) /* CPU based on Zen5 microarchitecture */
#define X86_FEATURE_ZEN6 ( 3*32+ 6) /* CPU based on Zen6 microarchitecture */
-/* Free ( 3*32+ 7) */
+#define X86_FEATURE_RAR ( 3*32+ 7) /* Intel Remote Action Request */
#define X86_FEATURE_CONSTANT_TSC ( 3*32+ 8) /* "constant_tsc" TSC ticks at a constant rate */
#define X86_FEATURE_UP ( 3*32+ 9) /* "up" SMP kernel running on UP */
#define X86_FEATURE_ART ( 3*32+10) /* "art" Always running timer (ART) */
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index 8feb8fd2957a..dd662c42f510 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -1545,6 +1545,18 @@ static void __init cpu_set_bug_bits(struct cpuinfo_x86 *c)
setup_force_cpu_bug(X86_BUG_L1TF);
}
+static void __init detect_rar(struct cpuinfo_x86 *c)
+{
+ u64 msr;
+
+ if (cpu_has(c, X86_FEATURE_CORE_CAPABILITIES)) {
+ rdmsrl(MSR_IA32_CORE_CAPABILITIES, msr);
+
+ if (msr & CORE_CAP_RAR)
+ setup_force_cpu_cap(X86_FEATURE_RAR);
+ }
+}
+
/*
* The NOPL instruction is supposed to exist on all CPUs of family >= 6;
* unfortunately, that's not true in practice because of early VIA
@@ -1771,6 +1783,7 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
setup_clear_cpu_cap(X86_FEATURE_LA57);
detect_nopl();
+ detect_rar(c);
}
void __init init_cpu_devs(void)
--
2.49.0
next prev parent reply other threads:[~2025-05-20 1:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 1:02 [RFC v2 PATCH 0/9] Intel RAR TLB invalidation Rik van Riel
2025-05-20 1:02 ` [RFC v2 1/9] x86/mm: Introduce MSR_IA32_CORE_CAPABILITIES Rik van Riel
2025-05-21 14:57 ` Dave Hansen
2025-05-22 15:10 ` Sean Christopherson
2025-05-20 1:02 ` [RFC v2 2/9] x86/mm: Introduce Remote Action Request MSRs Rik van Riel
2025-05-21 11:49 ` Borislav Petkov
2025-05-20 1:02 ` [RFC v2 3/9] x86/mm: enable BROADCAST_TLB_FLUSH on Intel, too Rik van Riel
2025-05-20 1:02 ` Rik van Riel [this message]
2025-05-21 11:53 ` [RFC v2 4/9] x86/mm: Introduce X86_FEATURE_RAR Borislav Petkov
2025-05-21 13:57 ` Rik van Riel
2025-05-21 14:53 ` Borislav Petkov
2025-05-21 16:06 ` Rik van Riel
2025-05-21 19:39 ` Borislav Petkov
2025-05-20 1:02 ` [RFC v2 5/9] x86/mm: Change cpa_flush() to call flush_kernel_range() directly Rik van Riel
2025-05-21 11:54 ` Borislav Petkov
2025-05-21 15:16 ` Dave Hansen
2025-05-20 1:02 ` [RFC v2 6/9] x86/apic: Introduce Remote Action Request Operations Rik van Riel
2025-05-20 9:16 ` Ingo Molnar
2025-06-04 0:11 ` Rik van Riel
2025-05-21 15:28 ` Dave Hansen
2025-05-21 15:59 ` Rik van Riel
2025-05-20 1:02 ` [RFC v2 7/9] x86/mm: Introduce Remote Action Request Rik van Riel
2025-05-20 9:28 ` Ingo Molnar
2025-05-20 12:57 ` Rik van Riel
2025-05-24 9:22 ` Ingo Molnar
2025-05-20 11:29 ` Nadav Amit
2025-05-20 13:00 ` Rik van Riel
2025-05-20 20:26 ` Nadav Amit
2025-05-20 20:31 ` Rik van Riel
2025-05-21 16:38 ` Dave Hansen
2025-05-21 19:06 ` Thomas Gleixner
2025-06-03 20:08 ` Rik van Riel
2025-05-20 1:02 ` [RFC v2 8/9] x86/mm: use RAR for kernel TLB flushes Rik van Riel
2025-05-20 1:02 ` [RFC v2 9/9] x86/mm: userspace & pageout flushing using Intel RAR Rik van Riel
2025-05-20 2:48 ` [RFC v2.1 " Rik van Riel
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=20250520010350.1740223-5-riel@surriel.com \
--to=riel@surriel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=peterz@infradead.org \
--cc=riel@fb.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/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