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 2FE041FF144 for ; Tue, 10 Mar 2026 10:00:48 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 98A8B145F4; Tue, 10 Mar 2026 10:00:39 +0100 (CET) Date: Tue, 10 Mar 2026 10:00:31 +0100 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= Subject: partially-applied: [PATCH common/debcargo-conf/manager/proxmox-perl-rs/qemu-server 00/13] use NVML for vGPU info querying To: Dominik Csapak , pve-devel@lists.proxmox.com References: <20260305091711.1221589-1-d.csapak@proxmox.com> In-Reply-To: <20260305091711.1221589-1-d.csapak@proxmox.com> MIME-Version: 1.0 User-Agent: astroid/0.17.0 (https://github.com/astroidmail/astroid) Message-Id: <1773133204.h3neq6o26o.astroid@yuna.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773133201007 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.013 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: TD5E4T3CAD2QM4EC7AUMW6I74WYLA5MI X-Message-ID-Hash: TD5E4T3CAD2QM4EC7AUMW6I74WYLA5MI X-MailFrom: f.gruenbichler@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 March 5, 2026 10:16 am, Dominik Csapak wrote: > This series replaces Christoph's previous series[0] >=20 > It's more or less a rewrite, thus no v2 or similar, but some patches dire= ctly > take code from Christoph's attempt, so i marked those commits as > co-developed-by. >=20 > Changes: >=20 > Instead of using our own wrapper+high level abstraction use the already e= xisting > 'nvml-wrapper' and 'nvml-wrapper-sys' which had a very similar approach, = but are > already packaged in debian. (though not fully up-to-date to what we need,= so > i updated/backported the patches). Please tell me if when i should send > these kind of patches differently. >=20 > Also i expose two functions, 'creatable' and 'supported' for future proof= ing, > since we want to have a more complete response in the api about which pro= files > are available. >=20 > I moved the code that depends on the perlmod binding to qemu-server for n= ow > as it seemed fitting, we only need it there and in pve-manager >=20 > If wanted I can split it out into it's own package (proxmox-pci? > proxmox-hardware? proxmox-mdev?, not sure what's a good name for this), b= ut > that could also be done later when we need it. >=20 > Also changed the format of the description from 'x,y,z' to 'x > y > z' since > that's what was there previously and what the gui expects. Also the field= s > themselves can contain ',' so parsing would be unnecessarily hard when we= do > that. >=20 > The pve-common cleanup patch is optional, and as an alternative we could > just mark these deprecated and remove them with e.g. 10.0 so we can save = us a > breaks cyclye for pve-common <-> qemu-server. >=20 > 0: https://lore.proxmox.com/pve-devel/20260120131319.949986-1-c.heiss@pro= xmox.com/ >=20 > debcargo-conf: >=20 > Dominik Csapak (4): > nvml-wrapper: Update to 0.12.0 > nvml-wrapper: add patch for vgpu ids > backport nvml-wrapper-sys 0.9.0-1 > backport nvml-wrapper 0.12.0-1 >=20 > Matthias Geiger (4): > nvml-wrapper-sys: Update to 0.9.0 > nvml-wrapper-sys: release 0.9.0-1 > nvml-wrapper: Update to 0.11.0 > nvml-wrapper: release 0.11.0-1 >=20 > src/nvml-wrapper-sys/debian/changelog | 12 +++++++ > .../debian/copyright.debcargo.hint | 7 ++++ > src/nvml-wrapper/debian/changelog | 20 ++++++++++++ > .../debian/copyright.debcargo.hint | 11 +++++-- > ...-method-for-getting-the-vGPU-type-id.patch | 32 +++++++++++++++++++ > src/nvml-wrapper/debian/patches/series | 1 + > 6 files changed, 81 insertions(+), 2 deletions(-) > create mode 100644 src/nvml-wrapper/debian/patches/add-method-for-gettin= g-the-vGPU-type-id.patch this part here ^