From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 08D001FF13A for ; Wed, 01 Apr 2026 10:00:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 89A2911B01; Wed, 1 Apr 2026 10:00:38 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: [PATCH qemu-server v2 05/17] cpu config: Add helpers to lock and write config Date: Wed, 1 Apr 2026 10:00:16 +0200 Message-ID: <20260401080028.62513-6-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260401080028.62513-1-a.bied-charreton@proxmox.com> References: <20260401080028.62513-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.124 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: RUBRX3IH5JB24QG7CXK75J3EQDYMQKO2 X-Message-ID-Hash: RUBRX3IH5JB24QG7CXK75J3EQDYMQKO2 X-MailFrom: abied-charreton@jett.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Add lock/write primitives to allow programmatic access to /etc/pve/virtual-guest/cpu-models.conf as a preparatory step for adding a custom CPU models CRUD API to pve-manager. Signed-off-by: Arthur Bied-Charreton --- src/PVE/QemuServer/CPUConfig.pm | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/src/PVE/QemuServer/CPUConfig.pm b/src/PVE/QemuServer/CPUConfig.pm index 0ee9b991..65ced94f 100644 --- a/src/PVE/QemuServer/CPUConfig.pm +++ b/src/PVE/QemuServer/CPUConfig.pm @@ -6,7 +6,7 @@ use warnings; use JSON; use PVE::JSONSchema qw(json_bool); -use PVE::Cluster qw(cfs_register_file cfs_read_file); +use PVE::Cluster qw(cfs_register_file cfs_read_file cfs_lock_file cfs_write_file); use PVE::ProcFSTools; use PVE::RESTEnvironment qw(log_warn); use PVE::Tools qw(run_command); @@ -50,6 +50,17 @@ sub load_custom_model_conf { return cfs_read_file($cpu_models_filename); } +sub write_custom_model_conf { + my ($conf) = @_; + cfs_write_file($cpu_models_filename, $conf); +} + +sub lock_cpu_config { + my ($code) = @_; + cfs_lock_file($cpu_models_filename, undef, $code); + die $@ if $@; +} + #builtin models : reported-model is mandatory my $builtin_models_by_arch = { x86_64 => { -- 2.47.3