[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240517144607.2595798-2-niuxuewei.nxw@antgroup.com>
Date: Fri, 17 May 2024 22:46:03 +0800
From: Xuewei Niu <niuxuewei97@...il.com>
To: stefanha@...hat.com,
sgarzare@...hat.com
Cc: mst@...hat.com,
davem@...emloft.net,
kvm@...r.kernel.org,
virtualization@...ts.linux.dev,
netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Xuewei Niu <niuxuewei.nxw@...group.com>
Subject: [RFC PATCH 1/5] vsock/virtio: Extend virtio-vsock spec with an "order" field
The "order" field determines the location of the device in the linked list,
the device with CID 4, having a smallest order, is in the first place, and
so forth.
Rules:
* It doesn’t have to be continuous;
* It cannot exist conflicts;
* It is optional for the mode of a single device, but is required for the
mode of multiple devices.
Signed-off-by: Xuewei Niu <niuxuewei.nxw@...group.com>
---
include/uapi/linux/virtio_vsock.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/virtio_vsock.h b/include/uapi/linux/virtio_vsock.h
index 64738838bee5..b62ec7d2ab1e 100644
--- a/include/uapi/linux/virtio_vsock.h
+++ b/include/uapi/linux/virtio_vsock.h
@@ -43,6 +43,7 @@
struct virtio_vsock_config {
__le64 guest_cid;
+ __le64 order;
} __attribute__((packed));
enum virtio_vsock_event_id {
--
2.34.1
Powered by blists - more mailing lists