From: Dave Hansen <dave.hansen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
"Luck, Tony" <tony.luck@intel.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] x86/cpu: Add two Intel CPU model numbers
Date: Fri, 14 Feb 2025 08:23:32 -0800 [thread overview]
Message-ID: <6ec8839e-cdd9-4607-8556-dd412aed41a5@intel.com> (raw)
In-Reply-To: <20250214130205.GK14028@noisy.programming.kicks-ass.net>
On 2/14/25 05:02, Peter Zijlstra wrote:
> Isn't the only reason we're doing a new Family because we can out of
> module number space? It's not magically different from Fam6.
Right. That was the primary motivation.
But the new scheme should also make a little more logical sense. The
family numbers are supposed to move up at a steady rate and also
separate desktop and server.
Or maybe we'll realize we miss all the fun of family 6 and just start
shoving everything as models in family 19 randomly instead. ;)
next prev parent reply other threads:[~2025-02-14 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 17:37 [PATCH] x86/cpu: Add two Intel CPU model numbers Tony Luck
2025-02-12 1:39 ` Andrew Cooper
2025-02-12 16:09 ` Luck, Tony
2025-02-14 13:02 ` Peter Zijlstra
2025-02-14 16:23 ` Dave Hansen [this message]
2025-02-14 17:17 ` Luck, Tony
2025-04-18 6:40 ` Ingo Molnar
2025-02-14 13:03 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2025-04-14 14:42 Christian Ludloff
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=6ec8839e-cdd9-4607-8556-dd412aed41a5@intel.com \
--to=dave.hansen@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox