x86-64-v2
To a degree, this may be a future consideration for those choosing a GNU/Linux OS for an older PC.
"Tumbleweed currently targets base x86_64 (v1) but now will be moving to x86-64-v2. By going with x86-64-v2, CPU instructions set extensions now required include CMPXCHG16B, LAHF-SAHF, POPCNT, SSE3, SSE4.1, SSE4.2, and SSSE3. This basically shifts the baseline CPU requirements to roughly Intel Nehalem era processors or AMD Bulldozer and newer. Now being able to always assume SSE4.2 / SSSE3 / etc make for better compiler targeting to newer systems.
The x86-64-v2 requirement limits the Tumbleweed CPU support to roughly Intel CPUs of the past 15 years or on the AMD side hardware within roughly the past decade.
This is a sane move for openSUSE/SUSE to make as we roll into 2023. Besides openSUSE ALP requiring x86-64-v2, RHEL9 also mandates x86-64-v2 and being eyed by other distributions too. It's at the x86-64-v3 level where AVX becomes a requirement and other newer instructions that more sharply limit the supported processors, particularly in the low-end and embedded space. But x86-64-v2 for 2023+ Linux distributions makes sense."
28 November 2022
openSUSE Tumbleweed Begins Transitioning To x86-64-v2 CPU Requirements - Phoronix
https://www.phoronix.com/news/openSU...weed-x86-64-v2
https://archive.ph/zjwuA
Things aren't so cut & dried when it comes to what a Nehalem core can support.
Code:
john@john-Latitude-E4310-SSD:~$ cpu-info
Packages:
0: Intel Core i5 560M
Microarchitectures:
2x Nehalem
Cores:
0: 2 processors (0-1), Intel Nehalem
1: 2 processors (2-3), Intel Nehalem
Logical processors (System ID):
0 (0): APIC ID 0x00000000
1 (2): APIC ID 0x00000001
2 (1): APIC ID 0x00000004
3 (3): APIC ID 0x00000005
john@john-Latitude-E4310-SSD:~$
john@john-Latitude-E4310-SSD:~$
john@john-Latitude-E4310-SSD:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 36 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
CPU family: 6
Model: 37
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
Stepping: 5
Frequency boost: enabled
CPU max MHz: 2667.0000
CPU min MHz: 1199.0000
BogoMIPS: 5320.02
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc
a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht
tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon p
ebs bts rep_good nopl xtopology nonstop_tsc cpuid aperf
mperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est t
m2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes l
ahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpri
ority ept vpid dtherm ida arat flush_l1d
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 64 KiB (2 instances)
L1i: 64 KiB (2 instances)
L2: 512 KiB (2 instances)
L3: 3 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Itlb multihit: KVM: Mitigation: VMX disabled
L1tf: Mitigation; PTE Inversion; VMX conditional cache flushe
s, SMT vulnerable
Mds: Vulnerable: Clear CPU buffers attempted, no microcode;
SMT vulnerable
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer
sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIB
P conditional, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
john@john-Latitude-E4310-SSD:~$
Adv Reply
Bookmarks