x86/cpu: Rename Denverton and Gemini Lake
PATCH 1/1 x86/cpu: Rename Denverton and Gemini Lake
From: Kan Liang <[email protected]>
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
DENVERTON is Goldmont server SoC. Rename DENVERTON to GOLDMONT2, similar to SILVERMONT2 being the silvermont server SoCs.
Rename GEMINI_LAKE to GOLDMONT_PLUS.
--- arch/x86/events/intel/core.c | 4 ++-- arch/x86/events/intel/cstate.c | 4 ++-- arch/x86/events/intel/rapl.c | 4 ++-- arch/x86/events/msr.c | 4 ++-- arch/x86/include/asm/intel-family.h | 4 ++-- arch/x86/kernel/tsc.c | 2 +- drivers/cpufreq/intel_pstate.c | 2 +- drivers/edac/pnd2_edac.c | 2 +- drivers/idle/intel_idle.c | 6 +++--- drivers/platform/x86/intel_telemetry_debugfs.c | 2 +- drivers/platform/x86/intel_telemetry_pltdrv.c | 2 +- drivers/powercap/intel_rapl.c | 4 ++-- tools/power/x86/turbostat/turbostat.c | 22 +++++++++++----------- 13 files changed, 31 insertions(+), 31 deletions(-)
arch/x86/events/intel/core.c +2 -2
@@ -4042,7 +4042,7 @@ __init int intel_pmu_init(void)break ;case INTEL_FAM6_ATOM_GOLDMONT : -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT2 :memcpy (hw_cache_event_ids, glm_hw_cache_event_ids,sizeof (hw_cache_event_ids)); memcpy(hw_cache_extra_regs, glm_hw_cache_extra_regs,
@@ -4068,7 +4068,7 @@ __init int intel_pmu_init(void) name ="goldmont" ;break ; -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS :memcpy (hw_cache_event_ids, glp_hw_cache_event_ids,sizeof (hw_cache_event_ids)); memcpy(hw_cache_extra_regs, glp_hw_cache_extra_regs,
arch/x86/events/intel/cstate.c +2 -2
@@ -581,9 +581,9 @@ static const struct x86_cpu_id intel_cstates_match[] __initconst = {X86_CSTATES_MODEL (INTEL_FAM6_XEON_PHI_KNM , knl_cstates),X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GOLDMONT , glm_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_ATOM_DENVERTON , glm_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GOLDMONT2 , glm_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GEMINI_LAKE , glm_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GOLDMONT_PLUS , glm_cstates), { }, };MODULE_DEVICE_TABLE (x86cpu, intel_cstates_match);
arch/x86/events/intel/rapl.c +2 -2
@@ -777,9 +777,9 @@ static const struct x86_cpu_id rapl_cpu_match[] __initconst = {X86_RAPL_MODEL_MATCH (INTEL_FAM6_CANNONLAKE_MOBILE , skl_rapl_init),X86_RAPL_MODEL_MATCH (INTEL_FAM6_ATOM_GOLDMONT , hsw_rapl_init), -X86_RAPL_MODEL_MATCH (INTEL_FAM6_ATOM_DENVERTON , hsw_rapl_init), +X86_RAPL_MODEL_MATCH (INTEL_FAM6_ATOM_GOLDMONT2 , hsw_rapl_init), - X86_RAPL_MODEL_MATCH(INTEL_FAM6_ATOM_GEMINI_LAKE, hsw_rapl_init), + X86_RAPL_MODEL_MATCH(INTEL_FAM6_ATOM_GOLDMONT_PLUS, hsw_rapl_init), {}, };
arch/x86/events/msr.c +2 -2
@@ -74,9 +74,9 @@ static bool test_intel(int idx)case INTEL_FAM6_ATOM_AIRMONT :case INTEL_FAM6_ATOM_GOLDMONT : -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT2 : -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS :case INTEL_FAM6_XEON_PHI_KNL :case INTEL_FAM6_XEON_PHI_KNM :
arch/x86/include/asm/intel-family.h +2 -2
@@ -68,8 +68,8 @@#define INTEL_FAM6_ATOM_MERRIFIELD 0x4A/* Tangier */ #define INTEL_FAM6_ATOM_MOOREFIELD 0x5A/* Anniedale */ #define INTEL_FAM6_ATOM_GOLDMONT 0x5C -#define INTEL_FAM6_ATOM_DENVERTON 0x5F/* Goldmont Microserver */ -#define INTEL_FAM6_ATOM_GEMINI_LAKE 0x7A +#define INTEL_FAM6_ATOM_GOLDMONT2 0x5F/* Goldmont Microserver */ +#define INTEL_FAM6_ATOM_GOLDMONT_PLUS 0x7A/* Xeon Phi */
arch/x86/kernel/tsc.c +1 -1
@@ -620,7 +620,7 @@ unsigned long native_calibrate_tsc(void)case INTEL_FAM6_KABYLAKE_DESKTOP : crystal_khz =24000 ;/* 24.0 MHz */ break ; -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT2 : crystal_khz =25000 ;/* 25.0 MHz */ break ;case INTEL_FAM6_ATOM_GOLDMONT :
drivers/cpufreq/intel_pstate.c +1 -1
@@ -1785,7 +1785,7 @@ static const struct x86_cpu_id intel_pstate_cpu_ids[] = {ICPU (INTEL_FAM6_XEON_PHI_KNL , knl_funcs),ICPU (INTEL_FAM6_XEON_PHI_KNM , knl_funcs),ICPU (INTEL_FAM6_ATOM_GOLDMONT , core_funcs), -ICPU (INTEL_FAM6_ATOM_GEMINI_LAKE , core_funcs), +ICPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , core_funcs), ICPU(INTEL_FAM6_SKYLAKE_X, core_funcs), {} };
drivers/edac/pnd2_edac.c +1 -1
@@ -1541,7 +1541,7 @@ static struct dunit_ops dnv_ops = {static const struct x86_cpu_id pnd2_cpuids[] = { {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_GOLDMONT ,0 , (kernel_ulong_t)&apl_ops }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_DENVERTON ,0 , (kernel_ulong_t)&dnv_ops }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_GOLDMONT2 ,0 , (kernel_ulong_t)&dnv_ops }, { } };MODULE_DEVICE_TABLE (x86cpu, pnd2_cpuids);
drivers/idle/intel_idle.c +3 -3
@@ -1104,8 +1104,8 @@ static const struct x86_cpu_id intel_idle_ids[] __initconst = {ICPU (INTEL_FAM6_XEON_PHI_KNL , idle_cpu_knl),ICPU (INTEL_FAM6_XEON_PHI_KNM , idle_cpu_knl),ICPU (INTEL_FAM6_ATOM_GOLDMONT , idle_cpu_bxt), -ICPU (INTEL_FAM6_ATOM_GEMINI_LAKE , idle_cpu_bxt), - ICPU(INTEL_FAM6_ATOM_DENVERTON, idle_cpu_dnv), +ICPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , idle_cpu_bxt), + ICPU(INTEL_FAM6_ATOM_GOLDMONT2, idle_cpu_dnv), {} };
@@ -1322,7 +1322,7 @@ static void intel_idle_state_table_update(void)ivt_idle_state_table_update ();break ;case INTEL_FAM6_ATOM_GOLDMONT : -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS :bxt_idle_state_table_update ();break ;case INTEL_FAM6_SKYLAKE_DESKTOP :
drivers/platform/x86/intel_telemetry_debugfs.c +1 -1
@@ -320,7 +320,7 @@ static struct telemetry_debugfs_conf telem_apl_debugfs_conf = {static const struct x86_cpu_id telemetry_debugfs_cpu_ids[] = {TELEM_DEBUGFS_CPU (INTEL_FAM6_ATOM_GOLDMONT , telem_apl_debugfs_conf), -TELEM_DEBUGFS_CPU (INTEL_FAM6_ATOM_GEMINI_LAKE , telem_apl_debugfs_conf), +TELEM_DEBUGFS_CPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , telem_apl_debugfs_conf), {} };
drivers/platform/x86/intel_telemetry_pltdrv.c +1 -1
@@ -192,7 +192,7 @@ static struct telemetry_plt_config telem_glk_config = {static const struct x86_cpu_id telemetry_cpu_ids[] = {TELEM_CPU (INTEL_FAM6_ATOM_GOLDMONT , telem_apl_config), -TELEM_CPU (INTEL_FAM6_ATOM_GEMINI_LAKE , telem_glk_config), +TELEM_CPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , telem_glk_config), {} };
drivers/powercap/intel_rapl.c +2 -2
@@ -1169,8 +1169,8 @@ static const struct x86_cpu_id rapl_ids[] __initconst = {RAPL_CPU (INTEL_FAM6_ATOM_MERRIFIELD , rapl_defaults_tng),RAPL_CPU (INTEL_FAM6_ATOM_MOOREFIELD , rapl_defaults_ann),RAPL_CPU (INTEL_FAM6_ATOM_GOLDMONT , rapl_defaults_core), -RAPL_CPU (INTEL_FAM6_ATOM_GEMINI_LAKE , rapl_defaults_core), -RAPL_CPU (INTEL_FAM6_ATOM_DENVERTON , rapl_defaults_core), +RAPL_CPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , rapl_defaults_core), +RAPL_CPU (INTEL_FAM6_ATOM_GOLDMONT2 , rapl_defaults_core),RAPL_CPU (INTEL_FAM6_XEON_PHI_KNL , rapl_defaults_hsw_server), RAPL_CPU(INTEL_FAM6_XEON_PHI_KNM, rapl_defaults_hsw_server),
tools/power/x86/turbostat/turbostat.c +11 -11
@@ -2084,7 +2084,7 @@ int has_turbo_ratio_group_limits(int family, int model)switch (model) {case INTEL_FAM6_ATOM_GOLDMONT :case INTEL_FAM6_SKYLAKE_X : -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT2 :return 1 ; }return 0 ;
@@ -3177,8 +3177,8 @@ int probe_nhm_msrs(unsigned int family, unsigned int model) pkg_cstate_limits = phi_pkg_cstate_limits;break ;case INTEL_FAM6_ATOM_GOLDMONT :/* BXT */ -case INTEL_FAM6_ATOM_GEMINI_LAKE : -case INTEL_FAM6_ATOM_DENVERTON :/* DNV */ +case INTEL_FAM6_ATOM_GOLDMONT_PLUS : +case INTEL_FAM6_ATOM_GOLDMONT2 :/* DNV */ pkg_cstate_limits = bxt_pkg_cstate_limits;break ;default :
@@ -3221,7 +3221,7 @@ int is_dnv(unsigned int family, unsigned int model)return 0 ;switch (model) { -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT2 :return 1 ; }return 0 ;
@@ -3805,7 +3805,7 @@ void rapl_probe(unsigned int family, unsigned int model) }break ;case INTEL_FAM6_ATOM_GOLDMONT :/* BXT */ -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS : do_rapl =RAPL_PKG |RAPL_PKG_POWER_INFO ;if (rapl_joules)BIC_PRESENT (BIC_Pkg_J);
@@ -3875,7 +3875,7 @@ void rapl_probe(unsigned int family, unsigned int model)BIC_PRESENT (BIC_CorWatt); }break ; -case INTEL_FAM6_ATOM_DENVERTON :/* DNV */ +case INTEL_FAM6_ATOM_GOLDMONT2 :/* DNV */ do_rapl =RAPL_PKG |RAPL_DRAM |RAPL_DRAM_POWER_INFO |RAPL_DRAM_PERF_STATUS |RAPL_PKG_PERF_STATUS |RAPL_PKG_POWER_INFO |RAPL_CORES_ENERGY_STATUS ;BIC_PRESENT (BIC_PKG__ );BIC_PRESENT (BIC_RAM__ );
@@ -4155,8 +4155,8 @@ int has_snb_msrs(unsigned int family, unsigned int model)case INTEL_FAM6_CANNONLAKE_MOBILE :/* CNL */ case INTEL_FAM6_SKYLAKE_X :/* SKX */ case INTEL_FAM6_ATOM_GOLDMONT :/* BXT */ -case INTEL_FAM6_ATOM_GEMINI_LAKE : -case INTEL_FAM6_ATOM_DENVERTON :/* DNV */ +case INTEL_FAM6_ATOM_GOLDMONT_PLUS : +case INTEL_FAM6_ATOM_GOLDMONT2 :/* DNV */ return 1 ; }return 0 ;
@@ -4188,7 +4188,7 @@ int has_hsw_msrs(unsigned int family, unsigned int model)case INTEL_FAM6_KABYLAKE_DESKTOP :/* KBL */ case INTEL_FAM6_CANNONLAKE_MOBILE :/* CNL */ case INTEL_FAM6_ATOM_GOLDMONT :/* BXT */ -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS :return 1 ; }return 0 ;
@@ -4593,11 +4593,11 @@ void process_cpuid()case INTEL_FAM6_KABYLAKE_DESKTOP :/* KBL */ crystal_hz =24000000 ;/* 24.0 MHz */ break ; -case INTEL_FAM6_ATOM_DENVERTON :/* DNV */ +case INTEL_FAM6_ATOM_GOLDMONT2 :/* DNV */ crystal_hz =25000000 ;/* 25.0 MHz */ break ;case INTEL_FAM6_ATOM_GOLDMONT :/* BXT */ -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS : crystal_hz =19200000 ;/* 19.2 MHz */ break ;default :
Signature · 1 line
2.7.4
Peter Zijlstra
maintainerQuoted 5 lines · On Tue, Aug 07, 2018 at 10:17:27AM -0700, [email protected] wrote:
From: Kan Liang <[email protected]>
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
Quoted 7 lines
DENVERTON is Goldmont server SoC. Rename DENVERTON to GOLDMONT2, similar to SILVERMONT2 being the silvermont server SoCs.
Rename
GEMINI_LAKEtoGOLDMONT_PLUS.Suggested-by Peter Zijlstra (Intel) <[email protected]>Signed-off-by Kan Liang <[email protected]>
Thanks! the alternative to 2 is _X like we have with the big cores to denote server chips, but this is already a nice improvement.
Dave Hansen
maintainerQuoted 2 lines · On 08/07/2018 10:17 AM, [email protected] wrote:
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
Why?
Denverton is the platform. "Goldmont" is literally the microarchitecture, and you are suggesting moving *to* the microarchitecture name, which contradicts the description.
I'm confused.
Peter Zijlstra
maintainerQuoted 9 lines · Dave Hansen
Quoted 2 lines · On 08/07/2018 10:17 AM, [email protected] wrote:
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
Why?
Denverton is the platform. "Goldmont" is literally the microarchitecture, and you are suggesting moving *to* the microarchitecture name, which contradicts the description.
All the other (big core) are uarch names. Atom is weird in that it mixes uarch with platform names.
Dave Hansen
maintainerQuoted 11 lines · Peter Zijlstra
Quoted 8 lines · Dave Hansen
Quoted 2 lines · On 08/07/2018 10:17 AM, [email protected] wrote:
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
Why?
Denverton is the platform. "Goldmont" is literally the microarchitecture, and you are suggesting moving *to* the microarchitecture name, which contradicts the description.
All the other (big core) are uarch names. Atom is weird in that it mixes uarch with platform names.
Good point.
Feel free to add: Acked-by: Dave Hansen <[email protected]>
Quoted 9 lines · On Tue, Aug 07, 2018 at 10:17:27AM -0700, [email protected] wrote:
From: Kan Liang <[email protected]>
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
DENVERTON is Goldmont server SoC. Rename DENVERTON to GOLDMONT2, similar to SILVERMONT2 being the silvermont server SoCs.
Rename
GEMINI_LAKEtoGOLDMONT_PLUS.
That doesn't make sense. Goldmont Plus can be in other SOCs with different Model numbers too. 0x7a really means Gemini Lake SOC, but not all systems containing a Goldmont Plus.
Also all the other identifiers are for SOCs too.
-Andi
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Dave Hansen
Quoted 2 lines · On 08/07/2018 10:17 AM, [email protected] wrote:
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
Quoted 8 lines
Quoted 5 lines
Why?
Denverton is the platform. "Goldmont" is literally the microarchitecture, and you are suggesting moving *to* the microarchitecture name, which contradicts the description.
All the other (big core) are uarch names. Atom is weird in that it mixes uarch with platform names.
On most big core the platform/SOC just happens to have the same name as the uarch. But the identifiers really have to be per SOC because that is how Intel model numbers work.
It should be always the SOC.
-Andi
Peter Zijlstra
maintainerQuoted 12 lines · Andi Kleen
Quoted 11 lines · Peter Zijlstra
Quoted 9 lines · Dave Hansen
Quoted 2 lines · On 08/07/2018 10:17 AM, [email protected] wrote:
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
Why?
Denverton is the platform. "Goldmont" is literally the microarchitecture, and you are suggesting moving *to* the microarchitecture name, which contradicts the description.
Quoted 6 lines
Quoted 2 lines
All the other (big core) are uarch names. Atom is weird in that it mixes uarch with platform names.
On most big core the platform/SOC just happens to have the same name as the uarch. But the identifiers really have to be per SOC because that is how Intel model numbers work.
I'm sure that is how we ended up with two SKX parts with identical model numbers but different crystal frequencies :-(
Let's just keep consistency and use MICROARCH_TYPE things for everything.
Quoted 12 lines · Andi Kleen
Quoted 11 lines · Peter Zijlstra
Quoted 9 lines · Dave Hansen
Quoted 2 lines · On 08/07/2018 10:17 AM, [email protected] wrote:
Denverton and Gemini Lake are platform names and should not be used for Processor Family stuff. The microarchitecture codename should be used.
Why?
Denverton is the platform. "Goldmont" is literally the microarchitecture, and you are suggesting moving *to* the microarchitecture name, which contradicts the description.
Quoted 8 lines
Quoted 2 lines
All the other (big core) are uarch names. Atom is weird in that it mixes uarch with platform names.
On most big core the platform/SOC just happens to have the same name as the uarch. But the identifiers really have to be per SOC because that is how Intel model numbers work.
It should be always the SOC.
Which simply does not work. Look at Goldmont Fam 6 Model 5C. The SoCs with that Fam/Model combination are:
- Apollo Lake
- Broxton (has two platforms: Morganfield and Willowtrail)
It's even worse with Silvermont.
So no, the interesting information is the UARCH and the variant of that, e.g. UARCH_CLIENT, UARCH_SERVER, UARCH_WHATEVER. All the magic Code Names and their platform variants are not interesting at all for the Fam/Model information.
Thanks,
tglx
Quoted 5 lines
Which simply does not work. Look at Goldmont Fam 6 Model 5C. The SoCs with that Fam/Model combination are:
- Apollo Lake
- Broxton (has two platforms: Morganfield and Willowtrail)
Right pick one. The others are the same for software purposes and can be handled in the same way.
Quoted 4 lines
It's even worse with Silvermont.
So no, the interesting information is the UARCH and the variant of that,
With Uarch you mean the core uarch? That doesn't really work for something like Silvermont or Goldmont.
Quoted 1 line
e.g.
UARCH_CLIENT,UARCH_SERVER,UARCH_WHATEVER. All the magic Code Names
Right your scheme totally doesn't work on Silvermont because there are multiple client variants.
Quoted 2 lines
and their platform variants are not interesting at all for the Fam/Model information.
You're right platform is misleading. I think the right level are SOCs, because that matches the how the model numbers are allocated.
On Big Core *Lakes are all unique SOCs.
-Andi
Quoted 8 lines · Andi Kleen
Quoted 5 lines
Which simply does not work. Look at Goldmont Fam 6 Model 5C. The SoCs with that Fam/Model combination are:
- Apollo Lake
- Broxton (has two platforms: Morganfield and Willowtrail)Right pick one. The others are the same for software purposes and can be handled in the same way.
Pick one is really not a good choice.
Quoted 11 lines
Quoted 3 lines
It's even worse with Silvermont.
So no, the interesting information is the UARCH and the variant of that,
With Uarch you mean the core uarch? That doesn't really work for something like Silvermont or Goldmont.
Quoted 1 line
e.g.
UARCH_CLIENT,UARCH_SERVER,UARCH_WHATEVER. All the magic Code NamesRight your scheme totally doesn't work on Silvermont because there are multiple client variants.
We have that for the big cores as well:
#define INTEL_FAM6_HASWELL_CORE 0x3C #define INTEL_FAM6_HASWELL_X 0x3F #define INTEL_FAM6_HASWELL_ULT 0x45 #define INTEL_FAM6_HASWELL_GT3E 0x46
Why would we treat ATOM differently? It's all the same scheme:
SILVERMONT_CLIENT 0x37 Baytrail, ValleyviewSILVERMONT_SERVER 0x40 Avaton, Rangely
and on goldmont it's not any different.
We really want one scheme for both Core and ATOM and not randomly picked different ones. For the kernel (aside of some peripheral stuff) the most interesting information is the UARCH plus the extra features which are enabled on a particular SoC.
The current naming scheme e.g. for SILVERMONT is utter crap because the 1/2 variants are in fact CLIENT/SERVER and the comment in the header file, that there is no better name, is just silly.
Thanks,
tglx
Quoted 20 lines · Thomas Gleixner
Quoted 11 lines · Andi Kleen
Quoted 3 lines
It's even worse with Silvermont.
So no, the interesting information is the UARCH and the variant of that,
With Uarch you mean the core uarch? That doesn't really work for something like Silvermont or Goldmont.
Quoted 1 line
e.g.
UARCH_CLIENT,UARCH_SERVER,UARCH_WHATEVER. All the magic Code NamesRight your scheme totally doesn't work on Silvermont because there are multiple client variants.
We have that for the big cores as well:
#define INTEL_FAM6_HASWELL_CORE 0x3C #define INTEL_FAM6_HASWELL_X 0x3F #define INTEL_FAM6_HASWELL_ULT 0x45 #define INTEL_FAM6_HASWELL_GT3E 0x46
Quoted 4 lines
Why would we treat ATOM differently? It's all the same scheme:
SILVERMONT_CLIENT 0x37 Baytrail, Valleyview SILVERMONT_SERVER 0x40 Avaton, Rangely
0x5D SoFIA is another Silvermont variant on the client side, and doesn't fit well in that scheme I'd say. Calling it SILVERMONT_SOFIA would probably be best here so people can figure out what it is.
Arnd
Peter Zijlstra
maintainerQuoted 14 lines · Thomas Gleixner
We have that for the big cores as well:
#define INTEL_FAM6_HASWELL_CORE 0x3C #define INTEL_FAM6_HASWELL_X 0x3F #define INTEL_FAM6_HASWELL_ULT 0x45 #define INTEL_FAM6_HASWELL_GT3E 0x46Why would we treat ATOM differently? It's all the same scheme:
SILVERMONT_CLIENT0x37Baytrail, ValleyviewSILVERMONT_SERVER0x40Avaton, Rangelyand on goldmont it's not any different.
Quoted 8 lines
We really want one scheme for both Core and ATOM and not randomly picked different ones. For the kernel (aside of some peripheral stuff) the most interesting information is the UARCH plus the extra features which are enabled on a particular SoC.
The current naming scheme e.g. for SILVERMONT is utter crap because the 1/2 variants are in fact CLIENT/SERVER and the comment in the header file, that there is no better name, is just silly.
OK, I spend a lot of time googling various things and came up with the below. TL;DR:
/* "Small Core" Processors (Atom) */
#define INTEL_FAM6_ATOM_BONNELL 0x1C /* Diamondville, Pineview */
#define INTEL_FAM6_ATOM_BONNELL_MID 0x26 /* Silverthorne, Lincroft */
#define INTEL_FAM6_ATOM_SALTWELL 0x36 /* Cedarview */
#define INTEL_FAM6_ATOM_SALTWELL_MID 0x27 /* Penwell */
#define INTEL_FAM6_ATOM_SALTWELL_TABLET 0x35 /* Cloverview */
#define INTEL_FAM6_ATOM_SILVERMONT 0x37 /* Bay Trail, Valleyview */
#define INTEL_FAM6_ATOM_SILVERMONT_X 0x4D /* Avaton, Rangely */
#define INTEL_FAM6_ATOM_SILVERMONT_MID 0x4A /* Merriefield */
#define INTEL_FAM6_ATOM_AIRMONT 0x4C /* Cherry Trail, Braswell */
#define INTEL_FAM6_ATOM_AIRMONT_MID 0x5A /* Moorefield */
#define INTEL_FAM6_ATOM_GOLDMONT 0x5C /* Apollo Lake */
#define INTEL_FAM6_ATOM_GOLDMONT_X 0x5F /* Denvertor */
#define INTEL_FAM6_ATOM_GOLDMONT_PLUS 0x7A /* Gemini Lake */
---
Subject: x86/cpu: Sanitize FAM6_ATOM naming
From: Peter Zijlstra <[email protected]>
Date: Tue, 7 Aug 2018 10:17:27 -0700
Going primarily by:
https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors#Silvermont_microarchitecture
with additional information gleaned from other related pages; notably:
- Bonnell shrink was called Saltwell
- Moorefield is the Merriefield refresh which makes it Airmont
The general naming scheme is: FAM6_ATOM_UARCH_SOCTYPE
--- arch/x86/events/intel/core.c | 20 ++++--- arch/x86/events/intel/cstate.c | 8 +-- arch/x86/events/intel/rapl.c | 4 - arch/x86/events/msr.c | 8 +-- arch/x86/include/asm/intel-family.h | 33 ++++++------ arch/x86/kernel/cpu/common.c | 24 ++++----- arch/x86/kernel/tsc.c | 2 arch/x86/kernel/tsc_msr.c | 4 - arch/x86/platform/atom/punit_atom_debug.c | 4 - arch/x86/platform/intel-mid/device_libs/platform_bt.c | 2 drivers/acpi/acpi_lpss.c | 2 drivers/acpi/x86/utils.c | 2 drivers/cpufreq/intel_pstate.c | 4 - drivers/edac/pnd2_edac.c | 2 drivers/idle/intel_idle.c | 18 +++---- drivers/mmc/host/sdhci-acpi.c | 2 drivers/pci/pci-mid.c | 4 - drivers/platform/x86/intel_int0002_vgpio.c | 2 drivers/platform/x86/intel_mid_powerbtn.c | 4 - drivers/platform/x86/intel_telemetry_debugfs.c | 2 drivers/platform/x86/intel_telemetry_pltdrv.c | 2 drivers/powercap/intel_rapl.c | 10 +-- drivers/thermal/intel_soc_dts_thermal.c | 2 sound/soc/intel/boards/bytcr_rt5651.c | 2 tools/power/x86/turbostat/turbostat.c | 46 +++++++++--------- 25 files changed, 108 insertions(+), 105 deletions(-)
arch/x86/events/intel/core.c +11 -9
@@ -4121,11 +4121,11 @@ __init int intel_pmu_init(void) name ="nehalem" ;break ; -case INTEL_FAM6_ATOM_PINEVIEW : -case INTEL_FAM6_ATOM_LINCROFT : -case INTEL_FAM6_ATOM_PENWELL : -case INTEL_FAM6_ATOM_CLOVERVIEW : -case INTEL_FAM6_ATOM_CEDARVIEW : +case INTEL_FAM6_ATOM_BONNELL : +case INTEL_FAM6_ATOM_BONNELL_MID : +case INTEL_FAM6_ATOM_SALTWELL : +case INTEL_FAM6_ATOM_SALTWELL_MID : +case INTEL_FAM6_ATOM_SALTWELL_TABLET :memcpy (hw_cache_event_ids, atom_hw_cache_event_ids,sizeof (hw_cache_event_ids));
@@ -4138,9 +4138,11 @@ __init int intel_pmu_init(void) name ="bonnell" ;break ; -case INTEL_FAM6_ATOM_SILVERMONT1 : -case INTEL_FAM6_ATOM_SILVERMONT2 : +case INTEL_FAM6_ATOM_SILVERMONT : +case INTEL_FAM6_ATOM_SILVERMONT_X : +case INTEL_FAM6_ATOM_SILVERMONT_MID :case INTEL_FAM6_ATOM_AIRMONT : +case INTEL_FAM6_ATOM_AIRMONT_MID :memcpy (hw_cache_event_ids, slm_hw_cache_event_ids,sizeof (hw_cache_event_ids)); memcpy(hw_cache_extra_regs, slm_hw_cache_extra_regs,
@@ -4159,7 +4161,7 @@ __init int intel_pmu_init(void)break ;case INTEL_FAM6_ATOM_GOLDMONT : -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT_X :memcpy (hw_cache_event_ids, glm_hw_cache_event_ids,sizeof (hw_cache_event_ids)); memcpy(hw_cache_extra_regs, glm_hw_cache_extra_regs,
@@ -4185,7 +4187,7 @@ __init int intel_pmu_init(void) name ="goldmont" ;break ; -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS :memcpy (hw_cache_event_ids, glp_hw_cache_event_ids,sizeof (hw_cache_event_ids)); memcpy(hw_cache_extra_regs, glp_hw_cache_extra_regs,
arch/x86/events/intel/cstate.c +4 -4
@@ -559,8 +559,8 @@ static const struct x86_cpu_id intel_cstX86_CSTATES_MODEL (INTEL_FAM6_HASWELL_ULT , hswult_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_ATOM_SILVERMONT1 , slm_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_ATOM_SILVERMONT2 , slm_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_ATOM_SILVERMONT , slm_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_ATOM_SILVERMONT_X , slm_cstates),X86_CSTATES_MODEL (INTEL_FAM6_ATOM_AIRMONT , slm_cstates), X86_CSTATES_MODEL(INTEL_FAM6_BROADWELL_CORE, snb_cstates),
@@ -581,9 +581,9 @@ static const struct x86_cpu_id intel_cstX86_CSTATES_MODEL (INTEL_FAM6_XEON_PHI_KNM , knl_cstates),X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GOLDMONT , glm_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_ATOM_DENVERTON , glm_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GOLDMONT_X , glm_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GEMINI_LAKE , glm_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_ATOM_GOLDMONT_PLUS , glm_cstates), { }, };MODULE_DEVICE_TABLE (x86cpu, intel_cstates_match);
arch/x86/events/intel/rapl.c +2 -2
@@ -777,9 +777,9 @@ static const struct x86_cpu_id rapl_cpu_X86_RAPL_MODEL_MATCH (INTEL_FAM6_CANNONLAKE_MOBILE , skl_rapl_init),X86_RAPL_MODEL_MATCH (INTEL_FAM6_ATOM_GOLDMONT , hsw_rapl_init), -X86_RAPL_MODEL_MATCH (INTEL_FAM6_ATOM_DENVERTON , hsw_rapl_init), +X86_RAPL_MODEL_MATCH (INTEL_FAM6_ATOM_GOLDMONT_X , hsw_rapl_init), - X86_RAPL_MODEL_MATCH(INTEL_FAM6_ATOM_GEMINI_LAKE, hsw_rapl_init), + X86_RAPL_MODEL_MATCH(INTEL_FAM6_ATOM_GOLDMONT_PLUS, hsw_rapl_init), {}, };
arch/x86/events/msr.c +4 -4
@@ -69,14 +69,14 @@ static bool test_intel(int idx)case INTEL_FAM6_BROADWELL_GT3E :case INTEL_FAM6_BROADWELL_X : -case INTEL_FAM6_ATOM_SILVERMONT1 : -case INTEL_FAM6_ATOM_SILVERMONT2 : +case INTEL_FAM6_ATOM_SILVERMONT : +case INTEL_FAM6_ATOM_SILVERMONT_X :case INTEL_FAM6_ATOM_AIRMONT :case INTEL_FAM6_ATOM_GOLDMONT : -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT_X : -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS :case INTEL_FAM6_XEON_PHI_KNL :case INTEL_FAM6_XEON_PHI_KNM :
arch/x86/include/asm/intel-family.h +17 -16
@@ -8,9 +8,6 @@* The "_X" parts are generally the EP and EX Xeons, or the * "Extreme" ones, like Broadwell-E. * -* Things ending in "2" are usually because we have no better -* name for them. There's no processor called "SILVERMONT2". -* * While adding a new CPUID for a new microarchitecture, add a new * group to keep logically sorted out in chronological order. Within * that group keep the CPUID for the variants sorted by model number.
@@ -57,19 +54,23 @@/* "Small Core" Processors (Atom) */ -#define INTEL_FAM6_ATOM_PINEVIEW 0x1C -#define INTEL_FAM6_ATOM_LINCROFT 0x26 -#define INTEL_FAM6_ATOM_PENWELL 0x27 -#define INTEL_FAM6_ATOM_CLOVERVIEW 0x35 -#define INTEL_FAM6_ATOM_CEDARVIEW 0x36 -#define INTEL_FAM6_ATOM_SILVERMONT1 0x37/* BayTrail/BYT / Valleyview */ -#define INTEL_FAM6_ATOM_SILVERMONT2 0x4D/* Avaton/Rangely */ -#define INTEL_FAM6_ATOM_AIRMONT 0x4C/* CherryTrail / Braswell */ -#define INTEL_FAM6_ATOM_MERRIFIELD 0x4A/* Tangier */ -#define INTEL_FAM6_ATOM_MOOREFIELD 0x5A/* Anniedale */ -#define INTEL_FAM6_ATOM_GOLDMONT 0x5C -#define INTEL_FAM6_ATOM_DENVERTON 0x5F/* Goldmont Microserver */ -#define INTEL_FAM6_ATOM_GEMINI_LAKE 0x7A +#define INTEL_FAM6_ATOM_BONNELL 0x1C/* Diamondville, Pineview */ +#define INTEL_FAM6_ATOM_BONNELL_MID 0x26/* Silverthorne, Lincroft */ + +#define INTEL_FAM6_ATOM_SALTWELL 0x36/* Cedarview */ +#define INTEL_FAM6_ATOM_SALTWELL_MID 0x27/* Penwell */ +#define INTEL_FAM6_ATOM_SALTWELL_TABLET 0x35/* Cloverview */ + +#define INTEL_FAM6_ATOM_SILVERMONT 0x37/* Bay Trail, Valleyview */ +#define INTEL_FAM6_ATOM_SILVERMONT_X 0x4D/* Avaton, Rangely */ +#define INTEL_FAM6_ATOM_SILVERMONT_MID 0x4A/* Merriefield */ + +#define INTEL_FAM6_ATOM_AIRMONT 0x4C/* Cherry Trail, Braswell */ +#define INTEL_FAM6_ATOM_AIRMONT_MID 0x5A/* Moorefield */ + +#define INTEL_FAM6_ATOM_GOLDMONT 0x5C/* Apollo Lake */ +#define INTEL_FAM6_ATOM_GOLDMONT_X 0x5F/* Denvertor */ +#define INTEL_FAM6_ATOM_GOLDMONT_PLUS 0x7A/* Gemini Lake */ /* Xeon Phi */
arch/x86/kernel/cpu/common.c +12 -12
@@ -949,11 +949,11 @@ static void identify_cpu_without_cpuid(s }static const __initconst struct x86_cpu_id cpu_no_speculation[] = { - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_CEDARVIEW ,X86_FEATURE_ANY }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_CLOVERVIEW ,X86_FEATURE_ANY }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_LINCROFT ,X86_FEATURE_ANY }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_PENWELL ,X86_FEATURE_ANY }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_PINEVIEW ,X86_FEATURE_ANY }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SALTWELL ,X86_FEATURE_ANY }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SALTWELL_TABLET ,X86_FEATURE_ANY }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_BONNELL_MID ,X86_FEATURE_ANY }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SALTWELL_MID ,X86_FEATURE_ANY }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_BONNELL ,X86_FEATURE_ANY }, {X86_VENDOR_CENTAUR ,5 }, {X86_VENDOR_INTEL ,5 }, {X86_VENDOR_NSC ,5 },
@@ -968,10 +968,10 @@ static const __initconst struct x86_cpu_/* Only list CPUs which speculate but are non susceptible to SSB */ static const __initconst struct x86_cpu_id cpu_no_spec_store_bypass[] = { - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT1 }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_AIRMONT }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT2 }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_MERRIFIELD }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT_X }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT_MID }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_CORE_YONAH }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_XEON_PHI_KNL }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_XEON_PHI_KNM },
@@ -984,11 +984,11 @@ static const __initconst struct x86_cpu_static const __initconst struct x86_cpu_id cpu_no_l1tf[] = {/* in addition to cpu_no_speculation */ - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT1 }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT2 }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT_X }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_AIRMONT }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_MERRIFIELD }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_MOOREFIELD }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT_MID }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_AIRMONT_MID }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_GOLDMONT }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_DENVERTON }, {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_GEMINI_LAKE },
arch/x86/kernel/tsc.c +1 -1
@@ -635,7 +635,7 @@ unsigned long native_calibrate_tsc(void)case INTEL_FAM6_KABYLAKE_DESKTOP : crystal_khz =24000 ;/* 24.0 MHz */ break ; -case INTEL_FAM6_ATOM_DENVERTON : +case INTEL_FAM6_ATOM_GOLDMONT_X : crystal_khz =25000 ;/* 25.0 MHz */ break ;case INTEL_FAM6_ATOM_GOLDMONT :
arch/x86/kernel/tsc_msr.c +2 -2
@@ -59,9 +59,9 @@ static const struct freq_desc freq_desc_ };static const struct x86_cpu_id tsc_msr_cpu_ids[] = { -INTEL_CPU_FAM6 (ATOM_PENWELL , freq_desc_pnw), +INTEL_CPU_FAM6 (ATOM_SALTWELL , freq_desc_pnw),INTEL_CPU_FAM6 (ATOM_CLOVERVIEW , freq_desc_clv), -INTEL_CPU_FAM6 (ATOM_SILVERMONT1 , freq_desc_byt), +INTEL_CPU_FAM6 (ATOM_SILVERMONT , freq_desc_byt),INTEL_CPU_FAM6 (ATOM_AIRMONT , freq_desc_cht),INTEL_CPU_FAM6 (ATOM_MERRIFIELD , freq_desc_tng),INTEL_CPU_FAM6 (ATOM_MOOREFIELD , freq_desc_ann),
arch/x86/platform/atom/punit_atom_debug.c +2 -2
@@ -143,8 +143,8 @@ static void punit_dbgfs_unregister(void) (kernel_ulong_t)&drv_data }static const struct x86_cpu_id intel_punit_cpu_ids[] = { -ICPU (INTEL_FAM6_ATOM_SILVERMONT1 , punit_device_byt), -ICPU (INTEL_FAM6_ATOM_MERRIFIELD , punit_device_tng), +ICPU (INTEL_FAM6_ATOM_SILVERMONT , punit_device_byt), +ICPU (INTEL_FAM6_ATOM_SILVERMONT_MID , punit_device_tng),ICPU (INTEL_FAM6_ATOM_AIRMONT , punit_device_cht), {} };
arch/x86/platform/intel-mid/device_libs/platform_bt.c +1 -1
@@ -68,7 +68,7 @@ static struct bt_sfi_data tng_bt_sfi_dat { X86_VENDOR_INTEL, 6, model, X86_FEATURE_ANY, (kernel_ulong_t)&ddata }static const struct x86_cpu_id bt_sfi_cpu_ids[] = { -ICPU (INTEL_FAM6_ATOM_MERRIFIELD , tng_bt_sfi_data), +ICPU (INTEL_FAM6_ATOM_SILVERMONT_MID , tng_bt_sfi_data), {} };
drivers/acpi/acpi_lpss.c +1 -1
@@ -292,7 +292,7 @@ static const struct lpss_device_desc bsw#define ICPU (model) { X86_VENDOR_INTEL, 6, model, X86_FEATURE_ANY, }static const struct x86_cpu_id lpss_cpu_ids[] = { -ICPU (INTEL_FAM6_ATOM_SILVERMONT1 ),/* Valleyview, Bay Trail */ +ICPU (INTEL_FAM6_ATOM_SILVERMONT ),/* Valleyview, Bay Trail */ ICPU (INTEL_FAM6_ATOM_AIRMONT ),/* Braswell, Cherry Trail */ {} };
drivers/acpi/x86/utils.c +1 -1
@@ -54,7 +54,7 @@ static const struct always_present_id al* Bay / Cherry Trail PWM directly poked by GPU driver in win10, * but Linux uses a separate PWM driver, harmless if not used. */ -ENTRY ("80860F09" ,"1" ,ICPU (INTEL_FAM6_ATOM_SILVERMONT1 ), {}), +ENTRY ("80860F09" ,"1" ,ICPU (INTEL_FAM6_ATOM_SILVERMONT ), {}), ENTRY("80862288", "1", ICPU(INTEL_FAM6_ATOM_AIRMONT), {}),/* * The INT0002 device is necessary to clear wakeup interrupt sources
drivers/cpufreq/intel_pstate.c +2 -2
@@ -1778,7 +1778,7 @@ static const struct pstate_funcs knl_funstatic const struct x86_cpu_id intel_pstate_cpu_ids[] = {ICPU (INTEL_FAM6_SANDYBRIDGE , core_funcs),ICPU (INTEL_FAM6_SANDYBRIDGE_X , core_funcs), -ICPU (INTEL_FAM6_ATOM_SILVERMONT1 , silvermont_funcs), +ICPU (INTEL_FAM6_ATOM_SILVERMONT , silvermont_funcs),ICPU (INTEL_FAM6_IVYBRIDGE , core_funcs),ICPU (INTEL_FAM6_HASWELL_CORE , core_funcs),ICPU (INTEL_FAM6_BROADWELL_CORE , core_funcs),
@@ -1795,7 +1795,7 @@ static const struct x86_cpu_id intel_pstICPU (INTEL_FAM6_XEON_PHI_KNL , knl_funcs),ICPU (INTEL_FAM6_XEON_PHI_KNM , knl_funcs),ICPU (INTEL_FAM6_ATOM_GOLDMONT , core_funcs), -ICPU (INTEL_FAM6_ATOM_GEMINI_LAKE , core_funcs), +ICPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , core_funcs), ICPU(INTEL_FAM6_SKYLAKE_X, core_funcs), {} };
drivers/edac/pnd2_edac.c +1 -1
@@ -1541,7 +1541,7 @@ static struct dunit_ops dnv_ops = {static const struct x86_cpu_id pnd2_cpuids[] = { {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_GOLDMONT ,0 , (kernel_ulong_t)&apl_ops }, - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_DENVERTON ,0 , (kernel_ulong_t)&dnv_ops }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_GOLDMONT_X ,0 , (kernel_ulong_t)&dnv_ops }, { } };MODULE_DEVICE_TABLE (x86cpu, pnd2_cpuids);
drivers/idle/intel_idle.c +9 -9
@@ -1076,14 +1076,14 @@ static const struct x86_cpu_id intel_idlICPU (INTEL_FAM6_WESTMERE , idle_cpu_nehalem),ICPU (INTEL_FAM6_WESTMERE_EP , idle_cpu_nehalem),ICPU (INTEL_FAM6_NEHALEM_EX , idle_cpu_nehalem), -ICPU (INTEL_FAM6_ATOM_PINEVIEW , idle_cpu_atom), -ICPU (INTEL_FAM6_ATOM_LINCROFT , idle_cpu_lincroft), +ICPU (INTEL_FAM6_ATOM_BONNELL , idle_cpu_atom), +ICPU (INTEL_FAM6_ATOM_BONNELL_MID , idle_cpu_lincroft),ICPU (INTEL_FAM6_WESTMERE_EX , idle_cpu_nehalem),ICPU (INTEL_FAM6_SANDYBRIDGE , idle_cpu_snb),ICPU (INTEL_FAM6_SANDYBRIDGE_X , idle_cpu_snb), -ICPU (INTEL_FAM6_ATOM_CEDARVIEW , idle_cpu_atom), -ICPU (INTEL_FAM6_ATOM_SILVERMONT1 , idle_cpu_byt), -ICPU (INTEL_FAM6_ATOM_MERRIFIELD , idle_cpu_tangier), +ICPU (INTEL_FAM6_ATOM_SALTWELL , idle_cpu_atom), +ICPU (INTEL_FAM6_ATOM_SILVERMONT , idle_cpu_byt), +ICPU (INTEL_FAM6_ATOM_SILVERMONT_MID , idle_cpu_tangier),ICPU (INTEL_FAM6_ATOM_AIRMONT , idle_cpu_cht),ICPU (INTEL_FAM6_IVYBRIDGE , idle_cpu_ivb), ICPU(INTEL_FAM6_IVYBRIDGE_X, idle_cpu_ivt),
@@ -1091,7 +1091,7 @@ static const struct x86_cpu_id intel_idlICPU (INTEL_FAM6_HASWELL_X , idle_cpu_hsw),ICPU (INTEL_FAM6_HASWELL_ULT , idle_cpu_hsw),ICPU (INTEL_FAM6_HASWELL_GT3E , idle_cpu_hsw), -ICPU (INTEL_FAM6_ATOM_SILVERMONT2 , idle_cpu_avn), +ICPU (INTEL_FAM6_ATOM_SILVERMONT_X , idle_cpu_avn),ICPU (INTEL_FAM6_BROADWELL_CORE , idle_cpu_bdw),ICPU (INTEL_FAM6_BROADWELL_GT3E , idle_cpu_bdw), ICPU(INTEL_FAM6_BROADWELL_X, idle_cpu_bdw),
@@ -1104,8 +1104,8 @@ static const struct x86_cpu_id intel_idlICPU (INTEL_FAM6_XEON_PHI_KNL , idle_cpu_knl),ICPU (INTEL_FAM6_XEON_PHI_KNM , idle_cpu_knl),ICPU (INTEL_FAM6_ATOM_GOLDMONT , idle_cpu_bxt), -ICPU (INTEL_FAM6_ATOM_GEMINI_LAKE , idle_cpu_bxt), - ICPU(INTEL_FAM6_ATOM_DENVERTON, idle_cpu_dnv), +ICPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , idle_cpu_bxt), + ICPU(INTEL_FAM6_ATOM_GOLDMONT_X, idle_cpu_dnv), {} };
@@ -1322,7 +1322,7 @@ static void intel_idle_state_table_updativt_idle_state_table_update ();break ;case INTEL_FAM6_ATOM_GOLDMONT : -case INTEL_FAM6_ATOM_GEMINI_LAKE : +case INTEL_FAM6_ATOM_GOLDMONT_PLUS :bxt_idle_state_table_update ();break ;case INTEL_FAM6_SKYLAKE_DESKTOP :
drivers/mmc/host/sdhci-acpi.c +1 -1
@@ -246,7 +246,7 @@ static const struct sdhci_acpi_chip sdhcstatic bool sdhci_acpi_byt (void ) {static const struct x86_cpu_id byt[] = { - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT1 }, + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT }, {} };
drivers/pci/pci-mid.c +2 -2
@@ -62,8 +62,8 @@ static const struct pci_platform_pm_ops* arch/x86/platform/intel-mid/pwr.c. */ static const struct x86_cpu_id lpss_cpu_ids[] = { -ICPU (INTEL_FAM6_ATOM_PENWELL ), -ICPU (INTEL_FAM6_ATOM_MERRIFIELD ), +ICPU (INTEL_FAM6_ATOM_SALTWELL_MID ), +ICPU (INTEL_FAM6_ATOM_SILVERMONT_MID ), {} };
drivers/platform/x86/intel_int0002_vgpio.c +1 -1
@@ -60,7 +60,7 @@ static const struct x86_cpu_id int0002_c/* * Limit ourselves to Cherry Trail for now, until testing shows we * need to handle the INT0002 device on Baytrail too. -* ICPU(INTEL_FAM6_ATOM_SILVERMONT1), * Valleyview, Bay Trail * +* ICPU(INTEL_FAM6_ATOM_SILVERMONT), * Valleyview, Bay Trail * */ ICPU(INTEL_FAM6_ATOM_AIRMONT), /* Braswell, Cherry Trail */ {}
drivers/platform/x86/intel_mid_powerbtn.c +2 -2
@@ -125,8 +125,8 @@ static const struct mid_pb_ddata mrfld_d { X86_VENDOR_INTEL, 6, model, X86_FEATURE_ANY, (kernel_ulong_t)&ddata }static const struct x86_cpu_id mid_pb_cpu_ids[] = { -ICPU (INTEL_FAM6_ATOM_PENWELL , mfld_ddata), -ICPU (INTEL_FAM6_ATOM_MERRIFIELD , mrfld_ddata), +ICPU (INTEL_FAM6_ATOM_SALTWELL_MID , mfld_ddata), +ICPU (INTEL_FAM6_ATOM_SILVERMONT_MID , mrfld_ddata), {} };
drivers/platform/x86/intel_telemetry_debugfs.c +1 -1
@@ -320,7 +320,7 @@ static struct telemetry_debugfs_conf telstatic const struct x86_cpu_id telemetry_debugfs_cpu_ids[] = {TELEM_DEBUGFS_CPU (INTEL_FAM6_ATOM_GOLDMONT , telem_apl_debugfs_conf), -TELEM_DEBUGFS_CPU (INTEL_FAM6_ATOM_GEMINI_LAKE , telem_apl_debugfs_conf), +TELEM_DEBUGFS_CPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , telem_apl_debugfs_conf), {} };
drivers/platform/x86/intel_telemetry_pltdrv.c +1 -1
@@ -192,7 +192,7 @@ static struct telemetry_plt_config telemstatic const struct x86_cpu_id telemetry_cpu_ids[] = {TELEM_CPU (INTEL_FAM6_ATOM_GOLDMONT , telem_apl_config), -TELEM_CPU (INTEL_FAM6_ATOM_GEMINI_LAKE , telem_glk_config), +TELEM_CPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , telem_glk_config), {} };
drivers/powercap/intel_rapl.c +5 -5
@@ -1164,13 +1164,13 @@ static const struct x86_cpu_id rapl_ids[RAPL_CPU (INTEL_FAM6_KABYLAKE_DESKTOP , rapl_defaults_core),RAPL_CPU (INTEL_FAM6_CANNONLAKE_MOBILE , rapl_defaults_core), -RAPL_CPU (INTEL_FAM6_ATOM_SILVERMONT1 , rapl_defaults_byt), +RAPL_CPU (INTEL_FAM6_ATOM_SILVERMONT , rapl_defaults_byt),RAPL_CPU (INTEL_FAM6_ATOM_AIRMONT , rapl_defaults_cht), -RAPL_CPU (INTEL_FAM6_ATOM_MERRIFIELD , rapl_defaults_tng), -RAPL_CPU (INTEL_FAM6_ATOM_MOOREFIELD , rapl_defaults_ann), +RAPL_CPU (INTEL_FAM6_ATOM_SILVERMONT_MID , rapl_defaults_tng), +RAPL_CPU (INTEL_FAM6_ATOM_AIRMONT_MID , rapl_defaults_ann),RAPL_CPU (INTEL_FAM6_ATOM_GOLDMONT , rapl_defaults_core), -RAPL_CPU (INTEL_FAM6_ATOM_GEMINI_LAKE , rapl_defaults_core), -RAPL_CPU (INTEL_FAM6_ATOM_DENVERTON , rapl_defaults_core), +RAPL_CPU (INTEL_FAM6_ATOM_GOLDMONT_PLUS , rapl_defaults_core), +RAPL_CPU (INTEL_FAM6_ATOM_GOLDMONT_X , rapl_defaults_core),RAPL_CPU (INTEL_FAM6_XEON_PHI_KNL , rapl_defaults_hsw_server), RAPL_CPU(INTEL_FAM6_XEON_PHI_KNM, rapl_defaults_hsw_server),
drivers/thermal/intel_soc_dts_thermal.c +1 -1
@@ -45,7 +45,7 @@ static irqreturn_t soc_irq_thread_fn(int }static const struct x86_cpu_id soc_thermal_ids[] = { - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT1 ,0 , + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT ,0 ,BYT_SOC_DTS_APIC_IRQ }, {} };
sound/soc/intel/boards/bytcr_rt5651.c +1 -1
@@ -787,7 +787,7 @@ static struct snd_soc_card byt_rt5651_ca };static const struct x86_cpu_id baytrail_cpu_ids[] = { - {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT1 },/* Valleyview */ + {X86_VENDOR_INTEL ,6 ,INTEL_FAM6_ATOM_SILVERMONT },/* Valleyview */ {} };
tools/power/x86/turbostat/turbostat.c +23 -23
134 lines not on this page · raw message
Quoted 41 lines · Peter Zijlstra
Quoted 14 lines · Thomas Gleixner
We have that for the big cores as well:
#define INTEL_FAM6_HASWELL_CORE 0x3C #define INTEL_FAM6_HASWELL_X 0x3F #define INTEL_FAM6_HASWELL_ULT 0x45 #define INTEL_FAM6_HASWELL_GT3E 0x46Why would we treat ATOM differently? It's all the same scheme:
SILVERMONT_CLIENT0x37Baytrail, ValleyviewSILVERMONT_SERVER0x40Avaton, Rangelyand on goldmont it's not any different.
Quoted 8 lines
We really want one scheme for both Core and ATOM and not randomly picked different ones. For the kernel (aside of some peripheral stuff) the most interesting information is the UARCH plus the extra features which are enabled on a particular SoC.
The current naming scheme e.g. for SILVERMONT is utter crap because the 1/2 variants are in fact CLIENT/SERVER and the comment in the header file, that there is no better name, is just silly.
OK, I spend a lot of time googling various things and came up with the below. TL;DR:
/* "Small Core" Processors (Atom) */
#define
INTEL_FAM6_ATOM_BONNELL0x1C/* Diamondville, Pineview */
#defineINTEL_FAM6_ATOM_BONNELL_MID0x26/* Silverthorne, Lincroft */#define
INTEL_FAM6_ATOM_SALTWELL0x36/* Cedarview */
#defineINTEL_FAM6_ATOM_SALTWELL_MID0x27/* Penwell */
#defineINTEL_FAM6_ATOM_SALTWELL_TABLET0x35/* Cloverview */#define
INTEL_FAM6_ATOM_SILVERMONT0x37/* Bay Trail, Valleyview */
#defineINTEL_FAM6_ATOM_SILVERMONT_X0x4D/* Avaton, Rangely */
#defineINTEL_FAM6_ATOM_SILVERMONT_MID0x4A/* Merriefield */
Quoted 6 lines
#define
INTEL_FAM6_ATOM_AIRMONT0x4C/* Cherry Trail, Braswell */
#defineINTEL_FAM6_ATOM_AIRMONT_MID0x5A/* Moorefield */#define
INTEL_FAM6_ATOM_GOLDMONT0x5C/* Apollo Lake */
#defineINTEL_FAM6_ATOM_GOLDMONT_X0x5F/* Denvertor */
#defineINTEL_FAM6_ATOM_GOLDMONT_PLUS0x7A/* Gemini Lake */
Thanks for doing that!
Quoted 16 lines
---
Subject: x86/cpu: SanitizeFAM6_ATOMnaming
From: Peter Zijlstra <[email protected]>
Date: Tue, 7 Aug 2018 10:17:27 -0700Going primarily by:
https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors#Silvermont_microarchitecture
with additional information gleaned from other related pages; notably:
- Bonnell shrink was called Saltwell
- Moorefield is the Merriefield refresh which makes it AirmontThe general naming scheme is:
FAM6_ATOM_UARCH_SOCTYPE
Quoted 7 lines
Which way do we route that?
Thanks,
tglx
Dave Hansen
maintainerQuoted 3 lines · Peter Zijlstra
#define
INTEL_FAM6_ATOM_GOLDMONT0x5C/* Apollo Lake */
#defineINTEL_FAM6_ATOM_GOLDMONT_X0x5F/* Denvertor */
#defineINTEL_FAM6_ATOM_GOLDMONT_PLUS0x7A/* Gemini Lake */
s/Denvertor/Denverton/
But, yeah, that list looks consistent and sane.
Peter Zijlstra
maintainerQuoted 23 lines · Thomas Gleixner
Quoted 15 lines
Subject: x86/cpu: Sanitize
FAM6_ATOMnaming
From: Peter Zijlstra <[email protected]>
Date: Tue, 7 Aug 2018 10:17:27 -0700Going primarily by:
https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors#Silvermont_microarchitecture
with additional information gleaned from other related pages; notably:
- Bonnell shrink was called Saltwell
- Moorefield is the Merriefield refresh which makes it AirmontThe general naming scheme is:
FAM6_ATOM_UARCH_SOCTYPEQuoted 7 lines
Quoted 1 line
Which way do we route that?
I have it stuck in with some perf patches, does that work?
Quoted 24 lines · Peter Zijlstra
Quoted 23 lines · Thomas Gleixner
Quoted 22 lines
Subject: x86/cpu: Sanitize
FAM6_ATOMnaming
From: Peter Zijlstra <[email protected]>
Date: Tue, 7 Aug 2018 10:17:27 -0700Going primarily by:
https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors#Silvermont_microarchitecture
with additional information gleaned from other related pages; notably:
- Bonnell shrink was called Saltwell
- Moorefield is the Merriefield refresh which makes it AirmontThe general naming scheme is:
FAM6_ATOM_UARCH_SOCTYPE
Quoted 3 lines
Quoted 1 line
Which way do we route that?
I have it stuck in with some perf patches, does that work?
Sure. We just should do a quick check against -next for the files outside the tip realm.
Thanks,
tglx
Quoted 1 line
Quoted 1 line
SILVERMONT_CLIENT0x37Baytrail, Valleyview
There is no such product as Valleyview. Some things talk about Valleyview 2 but shouldn't as that is Baytrail.
Quoted 13 lines
/* "Small Core" Processors (Atom) */
#define
INTEL_FAM6_ATOM_BONNELL0x1C/* Diamondville, Pineview */
#defineINTEL_FAM6_ATOM_BONNELL_MID0x26/* Silverthorne, Lincroft */#define
INTEL_FAM6_ATOM_SALTWELL0x36/* Cedarview */
#defineINTEL_FAM6_ATOM_SALTWELL_MID0x27/* Penwell */
#defineINTEL_FAM6_ATOM_SALTWELL_TABLET0x35/* Cloverview */#define
INTEL_FAM6_ATOM_SILVERMONT0x37/* Bay Trail, Valleyview */
#defineINTEL_FAM6_ATOM_SILVERMONT_X0x4D/* Avaton, Rangely */
#defineINTEL_FAM6_ATOM_SILVERMONT_MID0x4A/* Merriefield */
Quoted 6 lines
#define
INTEL_FAM6_ATOM_AIRMONT0x4C/* Cherry Trail, Braswell */
#defineINTEL_FAM6_ATOM_AIRMONT_MID0x5A/* Moorefield */#define
INTEL_FAM6_ATOM_GOLDMONT0x5C/* Apollo Lake */
#defineINTEL_FAM6_ATOM_GOLDMONT_X0x5F/* Denvertor */
#defineINTEL_FAM6_ATOM_GOLDMONT_PLUS0x7A/* Gemini Lake */
Can you decide if you are going to consistently use the -view or the -trail naming ? I think for our use cases you mean Pinetrail, Cedartrail, Clovertrail, Cherrytrail as you are talking about platform (at least in the Intel sense of the word).
Alan
Peter Zijlstra
maintainerQuoted 4 lines · Alan Cox
Quoted 1 line
Quoted 1 line
SILVERMONT_CLIENT0x37Baytrail, ValleyviewThere is no such product as Valleyview. Some things talk about Valleyview 2 but shouldn't as that is Baytrail.
I couldn't find it either, but it is all over the linux code.
I'd be happy to remove it from this comment though.
Quoted 16 lines
Quoted 16 lines
/* "Small Core" Processors (Atom) */
#define
INTEL_FAM6_ATOM_BONNELL0x1C/* Diamondville, Pineview */
#defineINTEL_FAM6_ATOM_BONNELL_MID0x26/* Silverthorne, Lincroft */#define
INTEL_FAM6_ATOM_SALTWELL0x36/* Cedarview */
#defineINTEL_FAM6_ATOM_SALTWELL_MID0x27/* Penwell */
#defineINTEL_FAM6_ATOM_SALTWELL_TABLET0x35/* Cloverview */#define
INTEL_FAM6_ATOM_SILVERMONT0x37/* Bay Trail, Valleyview */
#defineINTEL_FAM6_ATOM_SILVERMONT_X0x4D/* Avaton, Rangely */
#defineINTEL_FAM6_ATOM_SILVERMONT_MID0x4A/* Merriefield */#define
INTEL_FAM6_ATOM_AIRMONT0x4C/* Cherry Trail, Braswell */
#defineINTEL_FAM6_ATOM_AIRMONT_MID0x5A/* Moorefield */
Quoted 8 lines
Quoted 3 lines
#define
INTEL_FAM6_ATOM_GOLDMONT0x5C/* Apollo Lake */
#defineINTEL_FAM6_ATOM_GOLDMONT_X0x5F/* Denvertor */
#defineINTEL_FAM6_ATOM_GOLDMONT_PLUS0x7A/* Gemini Lake */Can you decide if you are going to consistently use the -view or the -trail naming ? I think for our use cases you mean Pinetrail, Cedartrail, Clovertrail, Cherrytrail as you are talking about platform (at least in the Intel sense of the word).
Like I said; I went with whatever is on this here page:
https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors
There is no Cedar Trail, or Bayview. If you could do me a delta patch with the names you think are appropriate i'd be happy to fold it in. Alternatively, I can remove the tail comments entirely.
I spend entirely too much time already trying to come up with sensible names already.