All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@intel.com>
To: "Daniel P. Berrang�" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Xudong Hao <xudong.hao@intel.com>,
	Yu Chen <yu.c.chen@intel.com>, Zhao Liu <zhao1.liu@intel.com>
Subject: Re: [PATCH 10/10] dosc/cpu-models-x86: Add documentation for DiamondRapids
Date: Mon, 26 Jan 2026 22:00:45 +0800	[thread overview]
Message-ID: <aXdzjevRI51J43xy@intel.com> (raw)
In-Reply-To: <aV3WI44CYzWECDHh@intel.com>

Hi Daniel, just a gentle poke.

Thanks,
Zhao

On Wed, Jan 07, 2026 at 11:42:27AM +0800, Zhao Liu wrote:
> Date: Wed, 7 Jan 2026 11:42:27 +0800
> From: Zhao Liu <zhao1.liu@intel.com>
> Subject: Re: [PATCH 10/10] dosc/cpu-models-x86: Add documentation for
>  DiamondRapids
> 
> Hi Daniel,
> 
> > > +``DiamondRapids``
> > > +    Intel Xeon Processor.
> > > +
> > > +    Diamond Rapids product has a topology which differs from previous Xeon
> > > +    products. It does not support SMT, but instead features a dual core
> > > +    module (DCM) architecture. It also has core building blocks (CBB - die
> > > +    level in CPU topology). The cache hierarchy is organized as follows:
> > > +    L1 i/d cache is per thread, L2 cache is per DCM, and L3 cache is per
> > > +    CBB. This cache topology can be emulated for DiamondRapids CPU model
> > > +    using the smp-cache configuration as shown below:
> > 
> > Can I request a slight rewording to simplify this:
> 
> Yes, of course.
> 
> >   ``DiamondRapids``
> >      Intel Xeon Processor (DiamondRapids, 2025). This does not include SMT
> >      but allows the module and die topology levels. The cache hierarchy is
> >      L1 i/d cache per thread, L2 cache per module, and L3 cache per die,
> >      which can be emulated using using the smp-cache option:
> 
> Thanks for your words!
> 
> In the previous text, I also aimed to clarify the relationship between
> DCM/CBB and the QEMU topology hierarchy, as these terms appear frequently
> in DMR-related materials. Therefore, I thought a brief explanation of
> DCM/CBB may be helpful:
> 
> This does not include SMT but allows the module (dual core module - DCM)
> and die (core building block - CBB) topology levels.
> 
> What do you think?
> 
> 
> >      Example:
> > 
> >         ::
> > 
> >             -machine smp-cache.0.cache=l1d,smp-cache.0.topology=thread,\
> >                      smp-cache.1.cache=l1i,smp-cache.1.topology=thread,\
> >                      smp-cache.2.cache=l2,smp-cache.2.topology=module,\
> >                      smp-cache.3.cache=l3,smp-cache.3.topology=die,\
> >                      ...
> 
> Thanks,
> Zhao
> 


  reply	other threads:[~2026-01-26 13:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  7:10 [PATCH 00/10] i386/cpu: Add new instructions & CPU model for Intel Diamond Rapids Zhao Liu
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
2025-11-23 23:52   ` Chen, Yu C
2026-01-06 11:20   ` Daniel P. Berrangé
2026-01-07  3:42     ` Zhao Liu
2026-01-26 14:00       ` Zhao Liu [this message]
2026-01-06 11:22   ` Daniel P. Berrangé
2026-01-07  3:44     ` 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=aXdzjevRI51J43xy@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 \
    --cc=yu.c.chen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.