From: Thomas Gleixner <tglx@kernel.org>
To: Borislav Petkov <bp@alien8.de>,
dave.hansen@linux.intel.com,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Vishal Badole <Vishal.Badole@amd.com>,
mingo@redhat.com, x86@kernel.org, hpa@zytor.com,
rafael@kernel.org, lenb@kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, peterz@infradead.org,
tony.luck@intel.com, chang.seok.bae@intel.com,
wei.w.wang@hotmail.com
Subject: Re: [PATCH 1/2] x86/topology: Name the AMD core-type values
Date: Fri, 03 Jul 2026 21:39:59 +0200 [thread overview]
Message-ID: <87jyrblv5c.ffs@fw13> (raw)
In-Reply-To: <20260703193222.GFakgORjvxwnZTPRnI@fat_crate.local>
On Fri, Jul 03 2026 at 12:32, Borislav Petkov wrote:
> Something like the totally untested below - but it builds at least.
>
> We've allocated a u8 for the struct x86_cpu_id member type and we compare that
> to enum x86_topology_cpu_type cpu_type. I guess that's ok for now...
>
> There's potential for more cleanup by removing the ->intel_type and ->amd_type
> and converting them all to our internal represenation of CPU_TYPE but that's
> for later and other patches anyway.
>
> Thoughts?
Looks reasonable to me and should avoid all the nonsense you had to work
around before.
next prev parent reply other threads:[~2026-07-03 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 9:43 [PATCH 0/2] x86/topology: Add support for Low Power cpu_type Vishal Badole
2026-06-29 9:43 ` [PATCH 1/2] x86/topology: Name the AMD core-type values Vishal Badole
2026-07-02 0:27 ` Borislav Petkov
2026-07-02 22:06 ` Thomas Gleixner
2026-07-02 23:03 ` Borislav Petkov
2026-07-03 19:32 ` Borislav Petkov
2026-07-03 19:39 ` Thomas Gleixner [this message]
2026-07-06 18:29 ` Pawan Gupta
2026-07-07 0:47 ` Borislav Petkov
2026-07-07 17:52 ` Pawan Gupta
2026-07-07 19:29 ` Thomas Gleixner
2026-07-07 20:46 ` Pawan Gupta
2026-07-07 23:24 ` Thomas Gleixner
2026-06-29 9:43 ` [PATCH 2/2] x86/topology: Add TOPO_CPU_TYPE_LOW_POWER Vishal Badole
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=87jyrblv5c.ffs@fw13 \
--to=tglx@kernel.org \
--cc=Vishal.Badole@amd.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=wei.w.wang@hotmail.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.