qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Xudong Hao <xudong.hao@intel.com>,
	Zhao Liu <zhao1.liu@intel.com>
Subject: [PATCH 00/10] i386/cpu: Add new instructions & CPU model for Intel Diamond Rapids
Date: Thu, 20 Nov 2025 15:10:20 +0800	[thread overview]
Message-ID: <20251120071030.961230-1-zhao1.liu@intel.com> (raw)

Hi,

This series addes new instrucions and CPU model support for Intel
Diamond Rapids.

This series mainly includes:
 * MOVRS CPUID
 * new AMX CPUIDs
 * AVX10.2 & AVX10_VNNI_INT
 * DMR CPU model & topology documentation

This series is based on the previous minor cleanup:

https://lore.kernel.org/qemu-devel/20251118080837.837505-1-zhao1.liu@intel.com/

And you can find the code here:

https://gitlab.com/zhao.liu/qemu/-/tree/i386-all-for-dmr-v1.1-11-17-2025


One Thing More
==============

I'm a bit unsure about the AVX10 model (patch 4). In principle, AVX10.1
should be allowed to run on an AVX10.2 host. For similarly version
drived features, introducing a model might be a preferable way. However,
PMU doesn't serve as a good example here.


Thanks for your review!

Best Regards,
Zhao
---
Zhao Liu (10):
  i386/cpu: Add support for MOVRS in CPUID enumeration
  i386/cpu: Add CPUID.0x1E.0x1 subleaf for AMX instructions
  i386/cpu: Add support for AVX10_VNNI_INT in CPUID enumeration
  i386/cpu: Support AVX10.2 with AVX10 feature models
  i386/cpu: Add a helper to get host avx10 version
  i386/cpu: Allow cache to be shared at thread level
  i386/cpu: Add an option in X86CPUDefinition to control CPUID 0x1f
  i386/cpu: Define dependency for VMX_VM_ENTRY_LOAD_IA32_FRED
  i386/cpu: Add CPU model for Diamond Rapids
  dosc/cpu-models-x86: Add documentation for DiamondRapids

 docs/system/cpu-models-x86.rst.inc |  20 ++
 target/i386/cpu.c                  | 443 +++++++++++++++++++++++++----
 target/i386/cpu.h                  |  27 ++
 3 files changed, 441 insertions(+), 49 deletions(-)

-- 
2.34.1



             reply	other threads:[~2025-11-20  6:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  7:10 Zhao Liu [this message]
2025-11-20  7:10 ` [PATCH 01/10] i386/cpu: Add support for MOVRS in CPUID enumeration Zhao Liu
2025-11-20  7:10 ` [PATCH 02/10] i386/cpu: Add CPUID.0x1E.0x1 subleaf for AMX instructions Zhao Liu
2025-11-20  7:10 ` [PATCH 03/10] i386/cpu: Add support for AVX10_VNNI_INT in CPUID enumeration Zhao Liu
2025-11-20  7:10 ` [PATCH 04/10] i386/cpu: Support AVX10.2 with AVX10 feature models Zhao Liu
2025-11-20  7:10 ` [PATCH 05/10] i386/cpu: Add a helper to get host avx10 version Zhao Liu
2025-11-20  7:10 ` [PATCH 06/10] i386/cpu: Allow cache to be shared at thread level Zhao Liu
2025-11-20  7:10 ` [PATCH 07/10] i386/cpu: Add an option in X86CPUDefinition to control CPUID 0x1f Zhao Liu
2025-11-20  7:10 ` [PATCH 08/10] i386/cpu: Define dependency for VMX_VM_ENTRY_LOAD_IA32_FRED Zhao Liu
2025-11-20  7:10 ` [PATCH 09/10] i386/cpu: Add CPU model for Diamond Rapids Zhao Liu
2025-11-20  7:10 ` [PATCH 10/10] dosc/cpu-models-x86: Add documentation for DiamondRapids Zhao Liu

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=20251120071030.961230-1-zhao1.liu@intel.com \
    --to=zhao1.liu@intel.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xudong.hao@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;
as well as URLs for NNTP newsgroup(s).