From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 97922AA52; Fri, 26 Jun 2026 14:06:52 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 77DFFAB0D; Fri, 26 Jun 2026 14:06:50 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from fout-b1-smtp.messagingengine.com (fout-b1-smtp.messagingengine.com [202.12.124.144]) by atuin.qyliss.net (Postfix) with ESMTPS id 02CD9AB0A for ; Fri, 26 Jun 2026 14:06:48 +0000 (UTC) Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfout.stl.internal (Postfix) with ESMTP id 85D0E1D000E2; Fri, 26 Jun 2026 10:06:47 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-06.internal (MEProxy); Fri, 26 Jun 2026 10:06:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1782482807; x=1782569207; bh=vq1SVxq7TY 4wEaMObHgChCEzyFrXGxgplHs30Wv11Eg=; b=U0tfLuElS7ZPZsQo5uNvpuX7Dd waG/S+TzFeuZwqmbDpb1R/ZPRBTxMqLj6MvpbaVOAujxPAPOnWaGGWVvpxNvkbKG 4ZhA4Uiaew//j3nXugNi5/UGTuKiWIs1msRDambvGk1gGKWExj7O34rW0/pj45bQ x78zxLGxGtcMQF3GFcVV+GWZnCnAxwO0QzjPS9+Bi69tMdTwMvMdMnyr6B133UES RqISXUajxqm1NowHV6FZZ07muuIichQMAoOZqKRz6Su/KiuXzquBeNRMD8JXkg0o xSW9AhaOlyJL9hYbUsZWQjEfnHtQPRiuPBXhaatYg+hXiiOM0LA5htf/4Y6A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1782482807; x=1782569207; bh=vq1SVxq7TY4wEaMObHgChCEzyFrXGxgplHs 30Wv11Eg=; b=dYa4iGW8v3zaVzQGVjwmXxSZRWtjjbDLbqiDsKeoXjCQulsBbO4 WBi5q9V36x7cfqmeGN05rxN2aDWlRN4fWCaC2aIvDSTAIZM/le8g5o6yTssl2L5C gFXLTUEd9gAcQFJER2zyq53UL7vPZYZ5CgH7JWyH930JuNnl6qLVmEcHvmMjAXI3 o40wpUv+SBSFwYLD/hY3hSwPScyYcaXGq6tYB4COhcT/QD+OMmLAcvpIKU4V/yuA Aww2d1flqWvc4qbhkL245LVCac4A34ftViBgEt/tjkqygAejkvUwCs67narhPdXT ryqZKovGSHylSZEUB+g9mBrPmqkbb3Zc3mg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTF7sCpzdKyMJMk3QuLMG6PYHZfTvY8nUQiDc/DWDgcrXqkWH4mk7a/bmhG3qB11lw yBhzU8UKWYCx3OmlCRvvjTigG2IZI5FdZUThQNRK5sRVk8eVdGAtIGDEFZV7iqwFpgvK87 GfyOAyueq8Y0xLs7S/SbO/9QIj2v26fBynl6eSnUZoHdn09SqDy3xSi3gZyzT9pKKgJH/y ka0WHKufZLEX/BS/4ZFOUQ7F4/Zvs5ZaJ35WSgKM67PXpubBLlaKKXEOxkHTGCmgXGIXcJ VhsiYfhzv2bdD8s5n56Aun+4o579slwJfeZ3tyt79g5UGIlJuXvVLIMB+AKxpdFGjhllXy sZAm4qsfpBV/v++9F6uLG5sBp/K67cxb6G7j5NrHd5sQdCvZJhSXm4u4njGsU5QwB8BceD 4npT8zOnT4OUiyesaxM7OHrbpgRYlrJ/MsGS5qNt2zgC1HSSP9u/B56pQztot6GiUZ+lCb SDIhw9RGM9e9ZZxETwjtTgaN3jYPR202BwZVgO2e6gqk+CRKz3hTJsdibjne/9vSPFfvOI JVpWOabQwsXLYiioyPGr25Pce2QFgkGmPzyefcIU+2hOzYPaQBRA0sDMU9Mhk3Bund+wNw kNj57SQWlccnJZahcEI+QNxBvoGXSXkAmDePo1ND3GzTPmRYw31qwbwql9xw X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 26 Jun 2026 10:06:46 -0400 (EDT) Received: by fw12.qyliss.net (Postfix, from userid 1000) id B70E0B95C278; Fri, 26 Jun 2026 16:06:43 +0200 (CEST) From: Alyssa Ross To: colbyt Subject: Re: [PATCH 2/6] pkgs/cloud-hypervisor: update GPU patchset to v52 In-Reply-To: <7cb1c12557f07e353186254250bfea29e36c8f30.1782409229.git.colby@colbyt.com> References: <7cb1c12557f07e353186254250bfea29e36c8f30.1782409229.git.colby@colbyt.com> Date: Fri, 26 Jun 2026 16:06:41 +0200 Message-ID: <87h5mpflam.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-ID-Hash: Y6NGODYUPLQTF5PBUVYEJOOAULODXBQW X-Message-ID-Hash: Y6NGODYUPLQTF5PBUVYEJOOAULODXBQW X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: devel@spectrum-os.org X-Mailman-Version: 3.3.10 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable colbyt writes: > Update Spectrum's patched Cloud Hypervisor package to 52.0 and rebase > the local virtio-gpu/vhost-user GPU support onto that release. > > Cloud Hypervisor 52.0 uses vhost 0.16.0 and vhost-user-backend 0.22.0, > so update the paired rust-vmm/vhost checkout as well. The local vhost > shared-memory patches are no longer applied because vhost-user-backend > 0.22.0 already has the protocol support used by the GPU frontend. > > The cargo vendor derivation now vendors dependencies after applying the > local Cloud Hypervisor and vhost patches, so the patched vhost checkout > is included in the fixed-output dependency tree. > > Signed-off-by: colbyt > --- For Cloud Hypervisor 52.0, my plan had been to drop the custom GPU device, and just extend the new generic vhost-user device Demi upstreamed to support SHMEM, reducing the divergence with upstream and easing the path towards upstreaming the rest. I have this version of the patch locally, but had been waiting for the Nixpkgs update that will bring in the new Cloud Hypervisor. I expect that Nixpkgs update will come in the next week or two, after the next Nixpkgs staging cycle (which will bring some package fixes we need). Keeping Nixpkgs up to date = got away from me this year so far, because I was focused on some big organizational/long-term things for the first few months (that I hope will visibly bear fruit shortly=E2=80=A6), but I've been back on it in the = last few weeks getting Nixpkgs back into shape, so it should be back to regular updates shortly. If you'd like though, we could decouple our Cloud Hypervisor version from Nixpkgs' like you've done here, and I could update Cloud Hypervisor to 52.0 with my patch to extend the generic vhost-user device, rather than waiting another week or two for the Nixpkgs update. What do you think? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQGoGac7QfI+H5ZtFCZddwkt31pFQUCaj6HcgAKCRCZddwkt31p FYZ3AQDl9jXRfo4qn+SOiHMxDvuq/lTgjXOkkXJ/ID1LBte4FQEA1YiTj4M//1Lj cRcef9nT4celhmnw8ZmDYL2yg2ygOQs= =jwSY -----END PGP SIGNATURE----- --=-=-=--