Processor microarchitecture for platform

LustigPenguin · Dec 13, 2024

So I was reviewing the DCG call and noticed a new requirement on processor architecture for evo nodes.

How do I check which version microarchitecture I have? My lscpu command outputs:

Bash:

Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         40 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  4
  On-line CPU(s) list:   0-3
Vendor ID:               AuthenticAMD
  Model name:            AMD EPYC Processor (with IBPB)
    CPU family:          23
    Model:               1
    Thread(s) per core:  1
    Core(s) per socket:  4
    Socket(s):           1
    Stepping:            2
    BogoMIPS:            5190.24
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx f
                         xsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm rep_good nopl cpuid extd
                         _apicid tsc_known_freq pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt
                          aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalig
                         nsse 3dnowprefetch osvw topoext ssbd ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2
                         rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 arat
Virtualization features:
  Hypervisor vendor:     KVM
  Virtualization type:   full
Caches (sum of all):   
  L1d:                   128 KiB (4 instances)
  L1i:                   256 KiB (4 instances)
  L2:                    2 MiB (4 instances)
  L3:                    8 MiB (1 instance)
NUMA:                 
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-3
Vulnerabilities:       
  Gather data sampling:  Not affected
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Mitigation; untrained return thunk; SMT disabled
  Spec rstack overflow:  Mitigation; SMT disabled
  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, STIBP disabled, RSB filling, PBRSB-eIBRS No
                         t affected
  Srbds:                 Not affected
  Tsx async abort:       Not affected

Is did a few duckduckgo searches for AMD EPYC but it's not obvious what type of microarchitecture the virtual chip is using.

LustigPenguin · Dec 13, 2024

If someone reads this thread with a similar question. I looked up the wikipedia page suggested on the slide. I found AMD Excavator and later are v3. Excavator came out June 2, 2015. My chip was AMD EPYC, and EPYC came out June 20, 2017 so I think I'm good to go for v3.

qwizzie · Dec 13, 2024

I just checked my own VPS, turns out that even the 16 cores Intel Xeon E5-2698v3 with 32GB RAM is not supported. Sure it is part of the Haswell family, but it is not part of x86-64-v3. According ChatGPT the x86-64-v3 is used for processors starting with later microarchitectures (e.g., Skylake and beyond).