From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id C72911FF141 for ; Tue, 19 May 2026 11:56:29 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E5CC137CD1; Tue, 19 May 2026 11:56:27 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com, Arthur Bied-Charreton Subject: applied: [PATCH qemu-server v2] cpu models: only include custom models matching the current arch Date: Tue, 19 May 2026 11:55:33 +0200 Message-ID: <177918452857.69241.15028111856898925550.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260519090423.224307-1-a.bied-charreton@proxmox.com> References: <20260519090423.224307-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779184569971 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.009 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: W73IQI3U4MPXJWYE7U6X3L2X3JSASWDV X-Message-ID-Hash: W73IQI3U4MPXJWYE7U6X3L2X3JSASWDV X-MailFrom: f.ebner@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: On Tue, 19 May 2026 11:04:23 +0200, Arthur Bied-Charreton wrote: > The CPU model selector showed all custom models regardless of their > architecture, allowing one to assign an x86_64 host an aarch64 custom > model and vice versa. > > Only return custom models whose reported model matches the $arch > parameter in get_cpu_models. Applied, thanks! Avoided the multi-line post-if and also moved looking up the vendor into the branch where it's actually required. [1/1] cpu models: only include custom models matching the current arch commit: aa8e225a79e3c2b8fd30aa6555244fd7fdd37c1c