On 20/01/2026 7:50 am, Jan Beulich wrote:
> On 19.01.2026 20:39, Andrew Cooper wrote:
>> Despite removing references from the documentation, the Intel parts of CPUID
>> Masking were accidentally left behind and still active.
>>
>> Intel CPUID Masking is even more niche than AMD masking, as the MSRs only
>> exist between Nehalem and SandyBridge,
Turns out it was Core2, not Nehalem.
>> being fully replaced with CPUID
>> Faulting from IvyBridge onwards.
>>
>> Fixes: 317051c2f032 ("x86/amd: Drop the cpuid_mask_* command line options")
>> Signed-off-by: Andrew Cooper <[email protected]>
> Acked-by: Jan Beulich <[email protected]>
Thanks.
>
> Yet I think you also want to edit the CHANGELOG.md entry the other commit put
> in place, to not have that remain AMD-only?
Good point. I can fold in this minor adjustment:
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 7de34f64d1e6..53d92a259731 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,9 +12,9 @@ The format is based on [Keep a
Changelog](https://keepachangelog.com/en/1.0.0/)
### Removed
- On x86:
- - The cpuid_mask_* command line options for legacy AMD CPUs. These were
+ - The cpuid_mask_* command line options for legacy CPUs. These were
deprecated in Xen 4.7 and noted not to work correctly with AMD CPUs from
- 2011 onwards.
+ 2011 onwards, nor work at all with Intel CPUs from 2012.
- Xenoprofile support. Oprofile themselves removed support for Xen in 2014
prior to the version 1.0 release, and there has been no development since
before then in Xen.
which covers things suitably.
~Andrew
