From: Alyssa Ross <hi@alyssa.is>
To: devel@spectrum-os.org
Cc: Valentin Gagarin <valentin@gagarin.work>,
Demi Marie Obenour <demiobenour@gmail.com>,
colbyt <colby@colbyt.com>
Subject: [RFC PATCH 2/3] Documentation: update Cloud Hypervisor GPU outlook
Date: Wed, 8 Jul 2026 17:43:14 +0200 [thread overview]
Message-ID: <20260708154315.678807-3-hi@alyssa.is> (raw)
In-Reply-To: <20260708154315.678807-1-hi@alyssa.is>
Signed-off-by: Alyssa Ross <hi@alyssa.is>
---
.../software/cloud-hypervisor/index.html | 22 +++++--------------
1 file changed, 5 insertions(+), 17 deletions(-)
diff --git a/Documentation/software/cloud-hypervisor/index.html b/Documentation/software/cloud-hypervisor/index.html
index 82c7b24..d746c82 100644
--- a/Documentation/software/cloud-hypervisor/index.html
+++ b/Documentation/software/cloud-hypervisor/index.html
@@ -104,23 +104,11 @@ for <a href="/doc/contributing/">contributing to Spectrum</a>.
<h2>Can these patches be upstreamed?</h2>
<p>
-I don’t think so. The Cloud Hypervisor developers
-are <a href="https://github.com/cloud-hypervisor/cloud-hypervisor/issues/3212#issuecomment-937823742">not
-very interested</a> in GPU support — although perhaps an
-implementation that was just a vfio-user frontend implementation,
-deletaging all of the complexity of rendering, input handling, etc. to
-another process would be light enough to overcome that — but on top of
-that, communicating with crosvm’s GPU device requires using
-non-standard commands that are not part of
-the <a href="https://www.qemu.org/docs/master/interop/vhost-user.html">vhost-user
-specification</a>.
-
-<p>
-It’s possible that, in future, it might be possible to use an external
-virtual GPU device with an unmodified Cloud Hypervisor
-using <a href="https://spdk.io/news/2021/05/04/vfio-user/">vfio-user</a>
-or <a href="https://lore.kernel.org/qemu-devel/20230901110018.3704459-1-alex.bennee@linaro.org/"><code>VHOST_USER_PROTOCOL_F_PROBE</code></a>,
-or that at least the custom vhost-user commands could be standardized.
+Yes! The <code>VHOST_USER_PROTOCOL_F_SHMEM</code> vhost-user feature
+was standardized in June 2026, meaning that non-standard vhost-user
+features are no longer required to use crosvm's GPU device. I expect
+to propose this implementation become part of upstream Cloud
+Hypervisor shortly, once some code quality improvements are made.
<p>
Other Cloud Hypervisor work is
--
2.54.0
next prev parent reply other threads:[~2026-07-08 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 15:43 [RFC PATCH 0/3] lib/nixpkgs.default.nix: update to master Alyssa Ross
2026-07-08 15:43 ` [RFC PATCH 1/3] " Alyssa Ross
2026-07-10 10:28 ` Alyssa Ross
2026-07-11 18:33 ` Alyssa Ross
2026-07-08 15:43 ` Alyssa Ross [this message]
2026-07-08 15:44 ` [RFC PATCH 3/3] xorg.lndir -> lndir 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=20260708154315.678807-3-hi@alyssa.is \
--to=hi@alyssa.is \
--cc=colby@colbyt.com \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
--cc=valentin@gagarin.work \
/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/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
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).