[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 1/3] docs: add documentation for Argo as a feature
- To: Teddy Astie <teddy.astie@xxxxxxxxxx>, Christopher Clark <christopher.w.clark@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Jason Andryuk <jason.andryuk@xxxxxxx>
- Date: Wed, 4 Jun 2025 11:42:33 -0400
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=vates.tech smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0)
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=eSOJ6meNppqIJCtLKD1Winmsj/qxt0d4kcfO69cMtAo=; b=IYajzAh0DhBxwgTtDiho7j/3035nlyJvymyClvv7b0SVaK96+pEr3NQbwd7XcMqFiXhqGdbPGyz/XLcVFBmopQAWqOVU/CvdJvQ1s7Y57N9QKDLEVSzerzmxiQVWfwONZT1VjnqypEuKlRexPrPeyOQG3foZ3d4K3c9tDgm+PM9L+g4eUCn3NiYugz28P+JAhSf1Ev6D6M+htpB9PZVyaTufD7BsDv5CuB1TWBHN3SqOSA7rUa/1ncYLlzRtjbrd1pWha/Zm2RHnNZ0nETVvice5sRG6xngTyparLUTqAqmeNp4hE91JjQDtTBhzVCh7sW4KvXo+hL/Twlzf1AwNmQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=nOxm7/JMk7hRVq01wVdPUm+RhxTw7uD+Wnu/nHXFKL9PVPinddFR1Zz7tx98lXtkektc84dx9y5KhdWpSpc+MN4aRngHzZYSWoo23z/rUyWMYEflt6o3b7cdrmOz3GfxIgwm02YfvKNuZ9IzuBxrHs19+wXYAFkj7FN1D0mt/aJMc2TUDUfKbyyAD8vb/gJ91gPty8Qgyv+rSavAK8Q5rIxs4NqnG/cY70QeTMaa9lmTKJjrVl12h5Y+iDnl6eE7yfpKxcog3IYfRvMfhNU83q+nE/OooaXaOYYK6ihAzv1CV19h4Gzf2RPkqxxICYun2AfS2i7WmtmGG/XBkGGxFg==
- Cc: Daniel Smith <dpsmith@xxxxxxxxxxxxxxxxxxxx>, Rich Persaud <persaur@xxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, "Anthony PERARD" <anthony.perard@xxxxxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, "Jan Beulich" <jbeulich@xxxxxxxx>, Julien Grall <julien@xxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>
- Delivery-date: Wed, 04 Jun 2025 16:14:55 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 2025-05-29 18:40, Teddy Astie wrote:
Hello Christopher,
Le 28/05/2025 à 23:13, Christopher Clark a écrit :
+## Argo and VirtIO
+
+References to design documentation for the development of an Argo
+transport for VirtIO are available via:
+https://wiki.xenproject.org/wiki/Virtio_On_Xen
+
Are there news regarding this ?
There is work done on virtio-msg [1], which looks fairly similar to
virtio-argo (or at least, virtio-msg could work with Argo in a similar
fashion to what's described on the virtio-argo design).
[1] https://linaro.atlassian.net/wiki/spaces/HVAC/overview
I think this should be dropped. We don't need a link to a design
document without an implementation. You can add it once you've
upstreamed the implementation.
+# Known issues
+
+* For development: sysctl/domctls for toolstack to control per-VM access
+ to Argo
+
Is it regarding disabling the argo on a per-guest basis, or regarding if
a specific VM can communicate with another VM ? i.e can the toolstack
decide to prevent 2 guest from communicating ?
IIRC, in Argo, a guest on his own can decide who can communicate with
him using separate registered rings. But I am not sure if there is more
on that regard.
Yes, I think the existing text needs to be rephrased to be more explicit
on the issue. I can guess what it is, but I shouldn't have to. I'd
recommend stating the issue as it exists, and then optionally clearly
state a proposed solution.
Regards,
Jason
|
