From: Dominik Csapak <d.csapak@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH-SERIES qemu-server v2 0/8] cpu config: support aarch64 CPU models
Date: Tue, 3 Feb 2026 15:09:50 +0100 [thread overview]
Message-ID: <b413f1be-36ed-4f72-839d-637b8fd9bc48@proxmox.com> (raw)
In-Reply-To: <20260129131021.118199-1-f.ebner@proxmox.com>
Aside from what Thomas found with 'get_host_arch'
there is one high level comment i have, but IMHO it's not a blocker:
I'm not a super fan of "sprinkling" `eq 'x86_64'` or similar throughout
the code, but for the cases used here it's probably ok.
If we encounter more such things though, I'd really like some
more general lookup for arch -> values or something like this.
even if it's just a 'supports_x' helper that has a hash
like
{
x86_64 => 1,
aarch64 => 0,
xxx => yyy,
}
etc
But as I wrote, for these use cases here probably ok, and
definitely no blocker for now since that can be cleaned
up whenever we see fit.
Aside from that,
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
Tested-by: Dominik Csapak <d.csapak@proxmox.com>
On 1/29/26 2:09 PM, 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.
>
> Some use sites do require a list of all possible ones, e.g. custom
> types, because they are not namespaced by arch.
>
> qemu-server:
>
> Fiona Ebner (8):
> cpu config: introduce pve-qm-cpu-arch standard option for virtual CPU
> architecture
> cpu config: guard adding hyperv enlightenments by arch
> cpu config: 'hidden' option only applies to vCPUs with x86_64 arch
> cpu config: introduce module-wide $host_arch variable
> cpu config: support aarch64 CPU models
> api: cpu: allow querying CPU models for a given architecture
> cpu config: support aarch64 CPU flags
> api: cpu flags: allow querying CPU flags for a given architecture
>
> src/PVE/API2/Qemu/CPU.pm | 8 +-
> src/PVE/API2/Qemu/CPUFlags.pm | 11 +-
> src/PVE/QemuServer.pm | 7 +-
> src/PVE/QemuServer/CPUConfig.pm | 453 ++++++++++++++++++--------------
> 4 files changed, 279 insertions(+), 200 deletions(-)
>
>
> Summary over all repositories:
> 4 files changed, 279 insertions(+), 200 deletions(-)
>
next prev parent reply other threads:[~2026-02-03 14:09 UTC|newest]
Thread overview: 13+ 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 ` Dominik Csapak [this message]
2026-02-03 14:48 ` [PATCH-SERIES qemu-server v2 0/8] cpu config: support aarch64 CPU models Thomas Lamprecht
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=b413f1be-36ed-4f72-839d-637b8fd9bc48@proxmox.com \
--to=d.csapak@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