From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] qm: cpu types: list that Haswell supports x86-64-v3 ABI
Date: Thu, 17 Jul 2025 01:09:11 +0200 [thread overview]
Message-ID: <175270732670.3546807.4953931801950907278.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250513080108.17210-1-f.ebner@proxmox.com>
On Tue, 13 May 2025 10:01:08 +0200, Fiona Ebner wrote:
> 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,
>
> [...]
Applied, thanks!
[1/1] qm: cpu types: list that Haswell supports x86-64-v3 ABI
commit: 838ad7efee0039d878452ff953b10f69431a3799
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-16 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 8:01 [pve-devel] " Fiona Ebner
2025-07-16 23:09 ` Thomas Lamprecht [this message]
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=175270732670.3546807.4953931801950907278.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.