From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH-SERIES v6 qemu-server/manager] add and set x86-64-v2-AES as default model for new vms
Date: Mon, 19 Jun 2023 09:11:59 +0200 [thread overview]
Message-ID: <bd0c2b18-3cbf-5df2-dfcd-c9e553780fef@proxmox.com> (raw)
In-Reply-To: <20230608095106.2238253-1-aderumier@odiso.com>
Am 08/06/2023 um 11:51 schrieb Alexandre Derumier:
> Here the new builtin models:
>
>
> x86-64-v1 : not implemented, as it's basicaly qemu64|kvm64 -vme,-cx16 for compat Opteron_G1 from 2004
> so will use it as qemu64|kvm64 is higher are not working on opteron_g1 anyway
>
> x86-64-v2 : Derived from qemu, +popcnt;+pni;+sse4.1;+sse4.2;+ssse3
>
> min intel: Nehalem
> min amd : Opteron_G3
>
> x86-64-v2-AES : Derived from qemu, +aes;+popcnt;+pni;+sse4.1;+sse4.2;+ssse3
>
> min intel: Westmere
Could confirm this.
> min amd : Opteron_G3
Could not confirm this, QEMU mentions that for this model it means AMD Opteron 23xx
(Gen 3 Class Opteron) CPUs, but I couldn't find any mentioning that those had already
AES support.
The first model that mentioned support for this were the Bulldozer based ones, i.e.,
Opteron 6200-series "Interlagos" and consorts, which QEMU lists under Opteron_G4.
Did I overlook something or is here the minimum really G4? Not that it's a big Problem,
but we need to know exactly what models can work with the new default for support
reasons.
>
> x86-64-v3 : Derived from qemu64 +aes;+popcnt;+pni;+sse4.1;+sse4.2;+ssse3;+avx;+avx2;+bmi1;+bmi2;+f16c;+fma;+abm;+movbe;+xsave
>
> min intel: Haswell
> min amd : EPYC_v1
>
> x86-64-v4 : Derived from qemu64 +aes;+popcnt;+pni;+sse4.1;+sse4.2;+ssse3;+avx;+avx2;+bmi1;+bmi2;+f16c;+fma;+abm;+movbe;+xsave;+avx512f;+avx512bw;+avx512cd;+avx512dq;+avx512vl
>
> min intel: Skylake
> min amd : EPYC_v4
next prev parent reply other threads:[~2023-06-19 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 9:51 Alexandre Derumier
2023-06-08 9:51 ` [pve-devel] [PATCH v6 qemu-server 1/1] cpuconfig: add new x86-64-vX models Alexandre Derumier
2023-06-08 9:51 ` [pve-devel] [PATCH v3 pve-manager 1/1] qemu: processor : set x86-64-v2-AES as default cputype for create wizard Alexandre Derumier
2023-06-12 16:23 ` [pve-devel] applied-series: [PATCH-SERIES v6 qemu-server/manager] add and set x86-64-v2-AES as default model for new vms Fiona Ebner
2023-06-19 7:11 ` Thomas Lamprecht [this message]
2023-06-19 7:16 ` [pve-devel] " DERUMIER, Alexandre
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=bd0c2b18-3cbf-5df2-dfcd-c9e553780fef@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/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