All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Chaohong Guo <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: Mon, 3 Aug 2026 08:30:44 +0200	[thread overview]
Message-ID: <anA1lG8Vw2NHDhVy@gmail.com> (raw)
In-Reply-To: <20260803051248.3684453-1-guochaohong@open-hieco.net>


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

> Consolidate all magic numbers of hygon CPUs into a header file,
> The macros describe the family/model numbers of hygon CPUs.

> +#define	HFM(_family, _model)	VFM_MAKE(X86_VENDOR_HYGON, _family, _model)
> +
> +#define	HYGON_F18_M04		HFM(0x18, 4)
> +#define	HYGON_F18_M06		HFM(0x18, 6)
> +#define	HYGON_F18_M07		HFM(0x18, 7)
> +
> +
> +#define	HYGON_7447V		HYGON_F18_M07

So this is a bit misleading, AFAICT "7447V" is the enterprise server
CPU variant - but there's a bunch of smaller server and desktop
CPU variants as well that are named differently:

	Model Name	Core / Thread Count	Base Clock	Target Segment
	----------      ----------------------  ----------      -------------
	7447V		96 Cores / 192 Threads	~2.6 GHz	Enterprise / Cloud Server
	7490H		96 Cores / 192 Threads	—		High-Density Server
	7490		64 Cores / 128 Threads	2.7 GHz		Enterprise Server
	7470		48 Cores /  96 Threads	—		Enterprise Server
	3490		16 Cores /  32 Threads	2.8 GHz		Desktop / Workstation
	3450E		 8 Cores /  16 Threads	3.6 GHz		Workstation / Desktop
	3450G		 8 Cores /  16 Threads	2.7 GHz		Workstation / Desktop

Assuming that this patch does the right thing for all
these smaller variants as well (does it?), shouldn't
the name be something like HYGON_4G or so, given
that the patch applies to the 4th generation Hygon
microarchitecture, not a specific server CPU configuration
such as 7447V?

Thanks,

	Ingo

  parent reply	other threads:[~2026-08-03  6:30 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 [this message]
2026-08-04  3:11   ` Guo Chaohong
2026-08-04 17:53     ` Ingo Molnar
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=anA1lG8Vw2NHDhVy@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.