From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id D84C31FF0BC for ; Thu, 29 Oct 2026 16:36:50 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id ECECA213DC; Thu, 29 Oct 2026 16:36:48 +0100 (CET) Message-ID: <5ec6ad07-7a3b-4195-991a-73042637d8fe@proxmox.com> Date: Thu, 29 Oct 2026 16:36:45 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC proxmox-perl-rs/qemu-server/qemu-server-rs v2 0/9] pci-handling rewrite (part 1/2/3) To: Dominik Csapak , pve-devel@lists.proxmox.com References: <20261015081041.743422-1-d.csapak@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20261015081041.743422-1-d.csapak@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1793288206011 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.322 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: LFMWPKSGZARYX2QIJG24ZVZ3RL7POFLA X-Message-ID-Hash: LFMWPKSGZARYX2QIJG24ZVZ3RL7POFLA 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: Am 15.10.26 um 10:11 AM schrieb Dominik Csapak: > ## Phase 4 - Host and NUMA layouts (the next part) > > With all the pieces in place, we can then easily extend the new layout by PCI > switches that are needed for assigning to NUMA nodes and replicating the host > topology for passed through devices. Can you describe the planned VM configuration settings for this? How do they fit alongside/relate to the "pci-layout" option you introduce in patch 9/9? It would be nice to know before the "pci-layout" option is set in stone.