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 70D871FF138 for ; Wed, 04 Feb 2026 16:48:15 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4CD56190A1; Wed, 4 Feb 2026 16:48:47 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Fiona Ebner 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 Message-ID: <177022008678.742580.10304239501032279130.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260129131021.118199-1-f.ebner@proxmox.com> References: <20260129131021.118199-1-f.ebner@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: 1770220047112 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.145 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_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish 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: HYSTYVUOBSCQPPZVXBUDCS7O7RX3RYX3 X-Message-ID-Hash: HYSTYVUOBSCQPPZVXBUDCS7O7RX3RYX3 X-MailFrom: t.lamprecht@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 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