Re: [PATCH v3 1/4] x86: Reject CPU policies with vendors other than the host's

[Alejandro Vallejo <alejandro.garciavallejo@amd.com>]

On Wed Mar 11, 2026 at 9:26 AM CET, Jan Beulich wrote:
> On 13.02.2026 12:42, Alejandro Vallejo wrote:
>> --- a/CHANGELOG.md
>> +++ b/CHANGELOG.md
>> @@ -22,6 +22,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>     - 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.
>> +   - Domains can no longer run on a CPU vendor if they were initially launched
>> +     on a different CPU vendor. This affects live migrations and save/restore
>> +     workflows accross mixed-vendor hosts. Cross-vendor emulation has always
>> +     been unreliable, but since 2017 with the advent of speculation security it
>> +     became unsustainably so.
>
> While the code adjustment looks okay to me, the wording is a little odd. What is
> "run on a CPU vendor"? How about "Domains can no longer run on a system with CPUs
> of a vendor different from the one they were initially launched on"?
>
> Also, nit: "across".

Sure

Cheers,
Alejandro