public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server v5 10/21] api: cpu flags: improve flags list returned by endpoint
Date: Fri, 15 May 2026 11:28:27 +0200	[thread overview]
Message-ID: <20260515092839.238064-11-a.bied-charreton@proxmox.com> (raw)
In-Reply-To: <20260515092839.238064-1-a.bied-charreton@proxmox.com>

Enhance the cpu-flags endpoint's list of flags by using the new
query_available_cpu_flags utility, which for each flag, additionally
returns a list of nodes supporting it, e.g.:

```
name: 'aes',
'supported-on': ['node1', 'node2'],
description: '...',
```

An `accel` parameter selects the acceleration type, `kvm` (default) or
`tcg` for which the flag-to-node compatibility is evaluated. The now-
unused get_supported_cpu_flags helper is removed.

Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
---
 src/PVE/API2/Qemu/CPUFlags.pm  | 24 +++++++++++++++++++++---
 src/PVE/QemuServer/CPUFlags.pm | 14 --------------
 2 files changed, 21 insertions(+), 17 deletions(-)

diff --git a/src/PVE/API2/Qemu/CPUFlags.pm b/src/PVE/API2/Qemu/CPUFlags.pm
index 4b409a40..873441d9 100644
--- a/src/PVE/API2/Qemu/CPUFlags.pm
+++ b/src/PVE/API2/Qemu/CPUFlags.pm
@@ -7,6 +7,7 @@ use PVE::RESTHandler;
 use PVE::Tools qw(extract_param);
 
 use PVE::QemuServer::CPUFlags;
+use PVE::QemuServer::Helpers;
 
 use base qw(PVE::RESTHandler);
 
@@ -14,13 +15,22 @@ __PACKAGE__->register_method({
     name => 'index',
     path => '',
     method => 'GET',
-    description => 'List of available VM-specific CPU flags.',
+    description =>
+        "List of available VM-specific CPU flags. Returns an empty list for 'aarch64' "
+        . "as no VM-specific flags are defined for it yet.",
     permissions => { user => 'all' },
     parameters => {
         additionalProperties => 0,
         properties => {
             node => get_standard_option('pve-node'),
             arch => get_standard_option('pve-qm-cpu-arch', { optional => 1 }),
+            accel => {
+                description => 'Acceleration type to check node compatibility for.',
+                type => 'string',
+                enum => [qw(kvm tcg)],
+                optional => 1,
+                default => 'kvm',
+            },
         },
     },
     returns => {
@@ -36,15 +46,23 @@ __PACKAGE__->register_method({
                     type => 'string',
                     description => "Description of the CPU flag.",
                 },
+                'supported-on' => {
+                    description =>
+                        'List of nodes supporting the CPU flag with the selected acceleration type ("accel").',
+                    type => 'array',
+                    items => get_standard_option('pve-node'),
+                    optional => 1,
+                },
             },
         },
     },
     code => sub {
         my ($param) = @_;
 
-        my $arch = extract_param($param, 'arch');
+        my $arch = extract_param($param, 'arch') // PVE::QemuServer::Helpers::get_host_arch();
+        my $accel = extract_param($param, 'accel') // 'kvm';
 
-        return PVE::QemuServer::CPUFlags::get_supported_cpu_flags($arch);
+        return PVE::QemuServer::CPUFlags::query_available_cpu_flags($accel, 1, $arch);
     },
 });
 
diff --git a/src/PVE/QemuServer/CPUFlags.pm b/src/PVE/QemuServer/CPUFlags.pm
index 709828d7..09a4ab0b 100644
--- a/src/PVE/QemuServer/CPUFlags.pm
+++ b/src/PVE/QemuServer/CPUFlags.pm
@@ -6,13 +6,11 @@ use Exporter qw(import);
 
 use PVE::Cluster;
 use PVE::File;
-use PVE::QemuServer::Helpers qw(get_host_arch);
 
 our @EXPORT_OK = qw(
     cpu_flag_supported_re
     cpu_flag_any_re
     supported_cpu_flags_names
-    get_supported_cpu_flags
     query_understood_cpu_flags
     normalize_cpu_flag
     query_available_cpu_flags
@@ -168,18 +166,6 @@ sub cpu_flag_any_re() {
     return qr/([+-])([a-zA-Z0-9\-_\.]+)/;
 }
 
-=head3 get_supported_cpu_flags($arch)
-
-Return supported VM-specific CPU flags for $arch. $arch defaults to the host architecture
-if C<undef>.
-
-=cut
-
-sub get_supported_cpu_flags($arch) {
-    $arch = get_host_arch() if !defined($arch);
-    return $supported_vm_specific_cpu_flags_by_arch->{$arch};
-}
-
 sub query_understood_cpu_flags($arch) {
     my $filepath = "$understood_cpu_flag_dir/recognized-CPUID-flags-$arch";
 
-- 
2.47.3




  parent reply	other threads:[~2026-05-15  9:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  9:28 [PATCH docs/manager/qemu-server v5 00/21] Add API and UI for custom CPU models Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-docs v5 01/21] qm: add anchor to "CPU Type" section Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 02/21] cpu config: rename CPU models config path variable Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 03/21] cpu flags: move cpu flags-related utilities to their own module Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 04/21] cpu flags: compare against JSON::true when querying supported flags Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 05/21] cpu flags: normalize CPU flags to QEMU's format Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 06/21] cpu flags: add helper querying CPU flags with nodes supporting them Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 07/21] cpu config: rename custom CPU model config loader Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 08/21] cpu config: add helpers to lock and write config Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH qemu-server v5 09/21] cpu: register standard option for CPU format Arthur Bied-Charreton
2026-05-15  9:28 ` Arthur Bied-Charreton [this message]
2026-05-15  9:28 ` [PATCH qemu-server v5 11/21] custom cpu models: avoid redundant config load Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 12/21] cluster: reorder imports Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 13/21] cluster: makefile: reorder perl sources and align backslashes Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 14/21] api: add endpoint querying available CPU flags cluster-wide Arthur Bied-Charreton
2026-05-15  9:45   ` Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 15/21] api: add CRUD handlers for custom CPU models Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 16/21] ui: cpu model selector: allow filtering out custom models Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 17/21] ui: add basic custom CPU model editor Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 18/21] ui: cpu flags selector: add CPU flag editor for custom models Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 19/21] ui: cpu flags selector: allow filtering out flags supported on 0 nodes Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 20/21] ui: cpu flags selector: add search bar for large lists of flags Arthur Bied-Charreton
2026-05-15  9:28 ` [PATCH pve-manager v5 21/21] ui: group custom CPU with resource mappings Arthur Bied-Charreton
2026-05-15 17:05 ` [PATCH docs/manager/qemu-server v5 00/21] Add API and UI for custom CPU models Max R. Carrara

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=20260515092839.238064-11-a.bied-charreton@proxmox.com \
    --to=a.bied-charreton@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