On 10/24/25 3:15 PM, Zhao Liu wrote:
> 
> 
> On Mon, Sep 22, 2025 at 10:11:33PM -0400, Ewan Hai wrote:
>> Date: Mon, 22 Sep 2025 22:11:33 -0400
>> From: Ewan Hai <[email protected]>
>> Subject: [PATCH 3/3] target/i386: Introduce Zhaoxin Shijidadao-Server CPU
>>  model
>> X-Mailer: git-send-email 2.34.1
>>
>> Shijidadao-Server hardware enables IA32_CORE_CAPABILITIES and relies on
>> the SPLIT_LOCK_DETECT feature. When the kernel has not yet virtualized
>> this MSR, KVM filters the capability and QEMU emits a warning.
>>
>> This patch retains the core-capability bit in the CPU model so it will
>> take effect once KVM support becomes available.
>>
>> In QEMU, vCPU models default to '.version = 1'. Since there is currently
>> no '.features[index]' mapping for the "x-force-cpuid-0x1f" property, this
>> patch adds that property to the v1 version of the model.
> 
> I'm preparing the CPU model for Diamond Rapids, and also meet this
> issue.
> 
> Well, I happen to have a patch for this and I think you could give it
> a try. :)

That's good news. I'll test your patch and update mine accordingly.
When I send out v2, should I note in the cover letter that my patches are based
on your "0x1f option" patch?


Reply via email to