public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] qm: cpu types: list that Haswell supports x86-64-v3 ABI
Date: Tue, 13 May 2025 10:01:08 +0200	[thread overview]
Message-ID: <20250513080108.17210-1-f.ebner@proxmox.com> (raw)

As reported in the community forum [0] and mentioned in the QEMU
documentation [1], Haswell already supports the x86-64-v3 ABI. This
can also be seen in the QEMU source code [2] by checking that the
necessary flags are supported for the QEMU Haswell models.

[0]: https://forum.proxmox.com/threads/166061/post-770368
[1]: https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html#id1
[2]: in target/i386/cpu.c:
> .name = "Haswell",
> .level = 0xd,
> .vendor = CPUID_VENDOR_INTEL,
> .family = 6,
> .model = 60,
> .stepping = 4,
> .features[FEAT_1_EDX] =
>     CPUID_VME | CPUID_SSE2 | CPUID_SSE | CPUID_FXSR | CPUID_MMX |
>     CPUID_CLFLUSH | CPUID_PSE36 | CPUID_PAT | CPUID_CMOV | CPUID_MCA |
>     CPUID_PGE | CPUID_MTRR | CPUID_SEP | CPUID_APIC | CPUID_CX8 |
>     CPUID_MCE | CPUID_PAE | CPUID_MSR | CPUID_TSC | CPUID_PSE |
>     CPUID_DE | CPUID_FP87,
> .features[FEAT_1_ECX] =
>     CPUID_EXT_AVX | CPUID_EXT_XSAVE | CPUID_EXT_AES |
>     CPUID_EXT_POPCNT | CPUID_EXT_X2APIC | CPUID_EXT_SSE42 |
>     CPUID_EXT_SSE41 | CPUID_EXT_CX16 | CPUID_EXT_SSSE3 |
>     CPUID_EXT_PCLMULQDQ | CPUID_EXT_SSE3 |
>     CPUID_EXT_TSC_DEADLINE_TIMER | CPUID_EXT_FMA | CPUID_EXT_MOVBE |
>     CPUID_EXT_PCID | CPUID_EXT_F16C | CPUID_EXT_RDRAND,
> .features[FEAT_8000_0001_EDX] =
>     CPUID_EXT2_LM | CPUID_EXT2_RDTSCP | CPUID_EXT2_NX |
>     CPUID_EXT2_SYSCALL,
> .features[FEAT_8000_0001_ECX] =
>     CPUID_EXT3_ABM | CPUID_EXT3_LAHF_LM,
> .features[FEAT_7_0_EBX] =
>     CPUID_7_0_EBX_FSGSBASE | CPUID_7_0_EBX_BMI1 |
>     CPUID_7_0_EBX_HLE | CPUID_7_0_EBX_AVX2 | CPUID_7_0_EBX_SMEP |
>     CPUID_7_0_EBX_BMI2 | CPUID_7_0_EBX_ERMS | CPUID_7_0_EBX_INVPCID |
>     CPUID_7_0_EBX_RTM,

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
 qm.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qm.adoc b/qm.adoc
index 8b9e096..5cdb374 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -515,7 +515,7 @@ Added CPU flags compared to 'x86-64-v1': '+cx16', '+lahf-lm', '+popcnt', '+pni',
 * 'x86-64-v2-AES': Compatible with Intel CPU >= Westmere, AMD CPU >= Opteron_G4.
 Added CPU flags compared to 'x86-64-v2': '+aes'.
 +
-* 'x86-64-v3': Compatible with Intel CPU >= Broadwell, AMD CPU >= EPYC. Added
+* 'x86-64-v3': Compatible with Intel CPU >= Haswell, AMD CPU >= EPYC. Added
 CPU flags compared to 'x86-64-v2-AES': '+avx', '+avx2', '+bmi1', '+bmi2',
 '+f16c', '+fma', '+movbe', '+xsave'.
 +
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


                 reply	other threads:[~2025-05-13  8:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250513080108.17210-1-f.ebner@proxmox.com \
    --to=f.ebner@proxmox.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