All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Guo Chaohong <guochaohong@open-hieco.net>
Cc: peterz@infradead.org, tim.c.chen@linux.intel.com, bp@alien8.de,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/cpu/hygon: Introduce macros for hygon family numbers
Date: Tue, 4 Aug 2026 19:53:04 +0200	[thread overview]
Message-ID: <anInAH0NrWvoVI3m@gmail.com> (raw)
In-Reply-To: <9f99123f-25be-440d-a5c1-9e213c8e8f3f@open-hieco.net>


* Guo Chaohong <guochaohong@open-hieco.net> wrote:

> hi, Ingo,
> 
> 
> Hygon model 7 CPUs have either 4 or 6 dies. All 6‑die variants share the
> same interconnect topology.
> The Hygon‑4G family includes several model numbers, not just model 7. The
> 3‑series CPUs are designed
> for desktop/workstation use and are only available in single‑socket systems.
> 
> The following is a summary of key Hygon models:
> 
> Model Name   Cores / Threads    Clock Speed   Target Segment           Model
> Number
> 7447V               96 / 192               ~2.6 GHz Enterprise / Cloud
> Server     7
> 7490H              96 / 192                —  High‑Density Server           
>  7 (now 7446)
> 7490                 64 / 128               2.7 GHz  Enterprise Serve       
>            4
> 7470                 48 / 96                  —  Enterprise Server         
>         4
> 
> Therefore, we will restrict this patch to apply only to model 7 CPUs that
> have 6 dies on a multi‑socket
> system and add sched domains topology after the change into commit message 
> in the V2 patch.

Understood - but my point is that the "HYGON_7447V" symbol name
is inaccurate:

	+#define        HYGON_F18_M07           HFM(0x18, 7)
	+
	+#define        HYGON_7447V             HYGON_F18_M07

Note how 'HYGON_7447V' also covers 7490H/7446.

IMHO it will be less confusing if you skip the HYGON_7447V interim
symbol and just use HYGON_F18_M07 in arch_sched_node_distance(),
and add a comment that clarifies that the additional conditions
basically filter for the 7447V variant.

Or if you want a clean 7447V enumeration function, add it as
an inline function and use that in arch_sched_node_distance().

Both approaches would be acceptable.

Thanks,

	Ingo

  reply	other threads:[~2026-08-04 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  5:12 [PATCH 1/2] x86/cpu/hygon: Introduce macros for hygon family numbers Chaohong Guo
2026-08-03  5:12 ` [PATCH 2/2] sched/numa: Apply remote socket distance averaging for Hygon 7447V Chaohong Guo
2026-08-03  6:10   ` Ingo Molnar
2026-08-03  6:10 ` [PATCH 1/2] x86/cpu/hygon: Introduce macros for hygon family numbers Peter Zijlstra
2026-08-03  6:25   ` Borislav Petkov
2026-08-04  2:57   ` Guo Chaohong
2026-08-04 17:55     ` Ingo Molnar
2026-08-03  6:30 ` Ingo Molnar
2026-08-04  3:11   ` Guo Chaohong
2026-08-04 17:53     ` Ingo Molnar [this message]
2026-08-05  1:35       ` Guo Chaohong
2026-08-05  2:33         ` Guo Chaohong

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=anInAH0NrWvoVI3m@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=guochaohong@open-hieco.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tim.c.chen@linux.intel.com \
    --cc=x86@kernel.org \
    /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.