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 91ED22C2E; Wed, 08 Jul 2026 15:44:05 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 578172C11; Wed, 08 Jul 2026 15:44:02 +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-a1-smtp.messagingengine.com (fout-a1-smtp.messagingengine.com [103.168.172.144]) by atuin.qyliss.net (Postfix) with ESMTPS id 420542C01 for ; Wed, 08 Jul 2026 15:44:01 +0000 (UTC) Received: from phl-compute-04.internal (phl-compute-04.internal [10.202.2.44]) by mailfout.phl.internal (Postfix) with ESMTP id 5819FEC0185; Wed, 8 Jul 2026 11:44:00 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-04.internal (MEProxy); Wed, 08 Jul 2026 11:44:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-transfer-encoding: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=fm1; t=1783525440; x=1783611840; bh=ECr3UhTb615tFEcDzDwRVjw1UtjBTLDH6oY/yF6bH5w=; b= VbULqZtyPy2KhXz9tNbJYLqmdMtr/9lR/nPWHTj3cOGEOjBtX8llmV4LVD8v75wa WtyppZZKqnxRVMNCrOIA0IyI825coYLjnvMKpwTDYWSdY/sQqfjiNzHg7MayAdTV lRDxJPhHo5T0A8VWPSOeZ1gg6NNBzW+xoT5Rx6xo7JkNBPHXTzSyDqNXvnJEiBxK 2dAEiqdsvWubUB5zi0jwr1dOAZ1uw+Nt/DalbAFT3rRKoWCJ/7n4p9N0ju4Qwy9Y 8VY9G+Ei+aSk43Z2JEPDMl583oaPxaiSShY+aRMPhV3HVosUxBGKECcX9OakNR2g w8FJhOAAWXUYZ32t7A7h7Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=fm2; t=1783525440; x= 1783611840; bh=ECr3UhTb615tFEcDzDwRVjw1UtjBTLDH6oY/yF6bH5w=; b=l qeVuMHaK9pUdIMQvpUGWCkF28Dxn2co2NK170iUxaVmtjTZlG1igR7mcTJseL5Oa XpPsC0RS4ayct/VJslyI+BGfXL/UrsVwvBg8zOxUROtATQDkeCDI4EEG1gLxgDs/ N/u5DFm2ZRc54C7r3RyNfUsJb6Ykbp7ql0RBnp5q5OTyQK03MXwt/aebqQtlGqWC tZIXl65CqhY6gr04R2cS6C2+bFupAaaHrN4VEvL+11NWeYc9ok0nnFKsYJdtB4r+ Vz5BJ1+U3Kh0xSpXOirzK22arBJW8ZolJbrzcvpGCxHd2/HNC4MpcCF6XjpKH/v8 YiDGeAbjGAiJgMNSjmXgg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTGx+SBVfRZgwJ1pKurABMiZE1qr130ZEw3MpDVjCoXn1xRBLpPLTdhdgAs4HZz/wD KOVt5gMocR+hXsO8XBcI9LZ+BwJPyHWpkfKVGhOXo+0tKA2hNSfa+WSZWP93aEFIXCtfZy 54wciCUu2c4YHbVoVJro8pUZFec566Kv+PoOfzZhFa26LEtAqg/O5UFS93zYUxNnjaRV/3 6yKO97wI1KjpLM5D4FJa0u4C478/d6tsavKTKScSyLLJt4TAF7J6/93uaCPQzhZD1uoKte Y5/7YfkFo6cM1ujvuTQrCZZgA72uKH27wVau4W2QPF1d10F2Z1A7y5RTeUdecnPx+LR+SL tae5I0cdYYQtNw82ikkRkCRUe/Ab+Bq0FjJaUPIULU6q3Wp7KTwObnHY9bgVVJUOu3o+DK v6zHsfahwvu0Nckxu1cxz6iWjmVqB7EnuN9vXatSOnYnWLlG/LBhtFlBpNFF4y8NaDx1pv a06EogWcIR52Zn65TLtTNDTnzS3mVmkf2x0uIKV5uN0XGjj/D+Ndc0N00Ibd7I915ygfwh X3RWWxsV1tiL/Gkhe8Pn/0Bw5fZqI29O70g+wNUp8HEPi6puz4NKBXuKm2Gn8Zxg27J0Dn 8uHvQLZmct8g8YkonI93Rds5XVFRKZdA7C1aYFq3kp11oBwl/CXZujdUCutw X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 8 Jul 2026 11:43:59 -0400 (EDT) Received: by mbp.qyliss.net (Postfix, from userid 1000) id 32698889CEB8; Wed, 08 Jul 2026 17:43:58 +0200 (CEST) From: Alyssa Ross To: devel@spectrum-os.org Subject: [RFC PATCH 2/3] Documentation: update Cloud Hypervisor GPU outlook Date: Wed, 8 Jul 2026 17:43:14 +0200 Message-ID: <20260708154315.678807-3-hi@alyssa.is> X-Mailer: git-send-email 2.54.0 In-Reply-To: <20260708154315.678807-1-hi@alyssa.is> References: <20260708154315.678807-1-hi@alyssa.is> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Message-ID-Hash: J6VCQC5HB327LJ7ZTD42W3GDCUV6HXRV X-Message-ID-Hash: J6VCQC5HB327LJ7ZTD42W3GDCUV6HXRV 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: Valentin Gagarin , Demi Marie Obenour , colbyt 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: Signed-off-by: Alyssa Ross --- .../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 contributing to Spectrum.

Can these patches be upstreamed?

-I don’t think so. The Cloud Hypervisor developers -are not -very interested 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 vhost-user -specification. - -

-It’s possible that, in future, it might be possible to use an external -virtual GPU device with an unmodified Cloud Hypervisor -using vfio-user -or VHOST_USER_PROTOCOL_F_PROBE, -or that at least the custom vhost-user commands could be standardized. +Yes! The VHOST_USER_PROTOCOL_F_SHMEM 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.

Other Cloud Hypervisor work is -- 2.54.0