public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES v6 qemu-server/manager] add and set x86-64-v2-AES as default model for new vms
Date: Mon, 12 Jun 2023 18:23:21 +0200	[thread overview]
Message-ID: <0c44c93d-df34-5c48-8265-89704654ff30@proxmox.com> (raw)
In-Reply-To: <20230608095106.2238253-1-aderumier@odiso.com>

Am 08.06.23 um 11:51 schrieb Alexandre Derumier:
> 
> Hi,
> 
> we used kvm64 as default cpumodel since the begin of proxmox. (basically, it's like a pentium4 cpu flags).
> 
> New distros like rhel9 are compiled to use more modern cpu flags.
> (and windows already use new flags since year, and we already add some extra cpu flags)
> 
> "
> In 2020, AMD, Intel, Red Hat, and SUSE worked together to define
> three microarchitecture levels on top of the historical x86-64
> baseline:
> 
>   * x86-64-v1: original x86_64 baseline instruction set
>   * x86-64-v2: vector instructions up to Streaming SIMD
>                Extensions 4.2 (SSE4.2)  and Supplemental
>                Streaming SIMD Extensions 3 (SSSE3), the
>                POPCNT instruction, and CMPXCHG16B
>   * x86-64-v3: vector instructions up to AVX2, MOVBE,
>                and additional bit-manipulation instructions.
>   * x86-64-v4: vector instructions from some of the
>                AVX-512 variants.
> 
> "
> 
> 
> This patch series add new models inspired from a patch was found on qemu mailing, but never appplied
> 
> https://lore.kernel.org/all/20210526144038.278899-1-berrange@redhat.com/T/
> 
> 
> In addition to theses model, I have enabled aes too.
> I think it's really important, because a lot of users use default values and have
> bad performance with ssl and other crypto stuffs.
>

applied series, thanks!

We could bump the dependency pve-manager -> qemu-server, but when having
different versions across nodes, one would still run into an issue if
the backend doesn't know the new model, so not sure if worth it.




  parent reply	other threads:[~2023-06-12 16:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  9:51 [pve-devel] " 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 ` Fiona Ebner [this message]
2023-06-19  7:11 ` [pve-devel] [PATCH-SERIES v6 qemu-server/manager] add and set x86-64-v2-AES as default model for new vms Thomas Lamprecht
2023-06-19  7:16   ` 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=0c44c93d-df34-5c48-8265-89704654ff30@proxmox.com \
    --to=f.ebner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal