From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6] x86/mm: Don't disable PCID when INVLPG has been fixed by microcode
Date: Sun, 9 Mar 2025 22:14:53 -0400 [thread overview]
Message-ID: <20250309170051-9ad32b902100fbb3@stable.kernel.org> (raw)
In-Reply-To: <20250307-clear-pcid-6-6-v1-1-cbf7ff0e817c@linux.intel.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: f24f669d03f884a6ef95cca84317d0f329e93961
WARNING: Author mismatch between patch and upstream commit:
Backport author: Pawan Gupta<pawan.kumar.gupta@linux.intel.com>
Commit author: Xi Ruoyao<xry111@xry111.site>
Note: The patch differs from the upstream commit:
---
1: f24f669d03f88 ! 1: b5ea42106470f x86/mm: Don't disable PCID when INVLPG has been fixed by microcode
@@ Metadata
## Commit message ##
x86/mm: Don't disable PCID when INVLPG has been fixed by microcode
+ commit f24f669d03f884a6ef95cca84317d0f329e93961 upstream.
+
Per the "Processor Specification Update" documentations referred by
the intel-microcode-20240312 release note, this microcode release has
fixed the issue for all affected models.
@@ Commit message
Intel.
[ dhansen: comment and changelog tweaks ]
+ [ pawan: backported to 6.6 ]
Signed-off-by: Xi Ruoyao <xry111@xry111.site>
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Acked-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
+ Signed-off-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Link: https://lore.kernel.org/all/168436059559.404.13934972543631851306.tip-bot2@tip-bot2/
Link: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20240312
Link: https://cdrdv2.intel.com/v1/dl/getContent/740518 # RPL042, rev. 13
@@ arch/x86/mm/init.c: static void __init probe_page_size_mask(void)
+ * these CPUs. New microcode fixes the issue.
*/
static const struct x86_cpu_id invlpg_miss_ids[] = {
-- X86_MATCH_VFM(INTEL_ALDERLAKE, 0),
-- X86_MATCH_VFM(INTEL_ALDERLAKE_L, 0),
-- X86_MATCH_VFM(INTEL_ATOM_GRACEMONT, 0),
-- X86_MATCH_VFM(INTEL_RAPTORLAKE, 0),
-- X86_MATCH_VFM(INTEL_RAPTORLAKE_P, 0),
-- X86_MATCH_VFM(INTEL_RAPTORLAKE_S, 0),
-+ X86_MATCH_VFM(INTEL_ALDERLAKE, 0x2e),
-+ X86_MATCH_VFM(INTEL_ALDERLAKE_L, 0x42c),
-+ X86_MATCH_VFM(INTEL_ATOM_GRACEMONT, 0x11),
-+ X86_MATCH_VFM(INTEL_RAPTORLAKE, 0x118),
-+ X86_MATCH_VFM(INTEL_RAPTORLAKE_P, 0x4117),
-+ X86_MATCH_VFM(INTEL_RAPTORLAKE_S, 0x2e),
+- X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE, 0),
+- X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L, 0),
+- X86_MATCH_INTEL_FAM6_MODEL(ATOM_GRACEMONT, 0),
+- X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE, 0),
+- X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P, 0),
+- X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S, 0),
++ X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE, 0x2e),
++ X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L, 0x42c),
++ X86_MATCH_INTEL_FAM6_MODEL(ATOM_GRACEMONT, 0x11),
++ X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE, 0x118),
++ X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P, 0x4117),
++ X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S, 0x2e),
{}
};
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-03-10 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 23:05 [PATCH 6.6] x86/mm: Don't disable PCID when INVLPG has been fixed by microcode Pawan Gupta
2025-03-10 2:14 ` Sasha Levin [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=20250309170051-9ad32b902100fbb3@stable.kernel.org \
--to=sashal@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=stable@vger.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