patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: colbyt <colby@colbyt.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 2/6] pkgs/cloud-hypervisor: update GPU patchset to v52
Date: Fri, 26 Jun 2026 16:06:41 +0200	[thread overview]
Message-ID: <87h5mpflam.fsf@alyssa.is> (raw)
In-Reply-To: <7cb1c12557f07e353186254250bfea29e36c8f30.1782409229.git.colby@colbyt.com>

[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]

colbyt <colby@colbyt.com> 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 <colby@colbyt.com>
> ---

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…), 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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2026-06-26 14:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 17:48 [PATCH 0/6] cloud-hypervisor v52 and VM runtime fixes colbyt
2026-06-25 17:48 ` [PATCH 1/6] pkgs/skaware: vendor backported patches colbyt
2026-06-26 13:39   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 2/6] pkgs/cloud-hypervisor: update GPU patchset to v52 colbyt
2026-06-26 14:06   ` Alyssa Ross [this message]
2026-06-25 17:48 ` [PATCH 3/6] vm: use vhost-user networking for crosvm colbyt
2026-06-26 14:45   ` Alyssa Ross
2026-07-02  9:07   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 4/6] Documentation: use crosvm GPU socket-path option colbyt
2026-06-26 14:18   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 5/6] installer: suppress boot console status noise colbyt
2026-06-26 14:46   ` Alyssa Ross
2026-06-26 19:09     ` colby
2026-07-02 11:44       ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 6/6] start-vmm: test GPU socket configuration colbyt
2026-06-26 14:18   ` Alyssa Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h5mpflam.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=colby@colbyt.com \
    --cc=devel@spectrum-os.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).