From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied-series: [PATCH-SERIES qemu-server v2 0/8] cpu config: support aarch64 CPU models
Date: Wed, 4 Feb 2026 16:48:14 +0100 [thread overview]
Message-ID: <177022008678.742580.10304239501032279130.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260129131021.118199-1-f.ebner@proxmox.com>
On Thu, 29 Jan 2026 14:09:57 +0100, Fiona Ebner wrote:
> Changes in v2:
> * also support querying flags for a specific arch
> * style: fix include ordering in CPU API module
>
> Previously, only the default 'cortex-a57' CPU model would be used
> implicitly. Group models and built-in models by architecture, since
> that is what (most) use sites are interested in. Note that the 'host'
> model only exists if the host arch matches the emulator/vCPU arch.
>
> [...]
Applied, thanks!
[1/8] cpu config: introduce pve-qm-cpu-arch standard option for virtual CPU architecture
commit: 295207f1f17c22e0d2532bd1eccc2ec63cd48296
[2/8] cpu config: guard adding hyperv enlightenments by arch
commit: b4807ba0cb9f745858eeb6814652fcde9f1b15c3
[3/8] cpu config: 'hidden' option only applies to vCPUs with x86_64 arch
commit: 1034ed3e6dcb38203db2f92b9b6e3391d77107f0
[4/8] cpu config: introduce module-wide $host_arch variable
commit: da67dc32f90260fcb58bf24af370306c602971bc
[5/8] cpu config: support aarch64 CPU models
commit: 96f5566c0def3f79bba4fa8a45813d6fad0b833a
[6/8] api: cpu: allow querying CPU models for a given architecture
commit: 3dd62cc7fd7639d17105de44cce412a30f0a2dcf
[7/8] cpu config: support aarch64 CPU flags
commit: e53dd61cf106fd872beff5dea97d97ebfcbf16e6
[8/8] api: cpu flags: allow querying CPU flags for a given architecture
commit: 7f74387c9e62bc95d07a29152b9b6ad3b4d10b47
prev parent reply other threads:[~2026-02-04 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 13:09 Fiona Ebner
2026-01-29 13:09 ` [PATCH qemu-server v2 1/8] cpu config: introduce pve-qm-cpu-arch standard option for virtual CPU architecture Fiona Ebner
2026-01-29 13:09 ` [PATCH qemu-server v2 2/8] cpu config: guard adding hyperv enlightenments by arch Fiona Ebner
2026-01-29 13:10 ` [PATCH qemu-server v2 3/8] cpu config: 'hidden' option only applies to vCPUs with x86_64 arch Fiona Ebner
2026-01-29 13:10 ` [PATCH qemu-server v2 4/8] cpu config: introduce module-wide $host_arch variable Fiona Ebner
2026-02-03 13:51 ` Thomas Lamprecht
[not found] ` <f567ae7c-39aa-40bb-9270-5f7cec6560eb@kohly.de>
2026-02-03 16:21 ` Thomas Lamprecht
2026-01-29 13:10 ` [PATCH qemu-server v2 5/8] cpu config: support aarch64 CPU models Fiona Ebner
2026-01-29 13:10 ` [PATCH qemu-server v2 6/8] api: cpu: allow querying CPU models for a given architecture Fiona Ebner
2026-01-29 13:10 ` [PATCH qemu-server v2 7/8] cpu config: support aarch64 CPU flags Fiona Ebner
2026-01-29 13:10 ` [PATCH qemu-server v2 8/8] api: cpu flags: allow querying CPU flags for a given architecture Fiona Ebner
2026-02-03 14:09 ` [PATCH-SERIES qemu-server v2 0/8] cpu config: support aarch64 CPU models Dominik Csapak
2026-02-03 14:48 ` Thomas Lamprecht
2026-02-04 15:48 ` 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=177022008678.742580.10304239501032279130.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox