From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, jasowang@redhat.com, mst@redhat.com,
xieyongji@bytedance.com, linux-kernel@vger.kernel.org,
maxime.coquelin@redhat.com
Subject: [PATCH v3 2/7] vduse: Add new uAPI for vduse reconnection
Date: Tue, 5 Dec 2023 16:34:39 +0800 [thread overview]
Message-ID: <20231205083444.3029239-3-lulu@redhat.com> (raw)
In-Reply-To: <20231205083444.3029239-1-lulu@redhat.com>
To synchronize the information for reconnection, add a new structure
struct vduse_dev_reconnect_data to save the device-related information,
Add the VDUSE_RECONNCT_MMAP_SIZE for the size of mapped memory for each vq
and device status.
Signed-off-by: Cindy Lu <lulu@redhat.com>
---
include/uapi/linux/vduse.h | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/include/uapi/linux/vduse.h b/include/uapi/linux/vduse.h
index 11bd48c72c6c..c22838247814 100644
--- a/include/uapi/linux/vduse.h
+++ b/include/uapi/linux/vduse.h
@@ -350,4 +350,26 @@ struct vduse_dev_response {
};
};
+/**
+ * struct vduse_dev_reconnect_data - saved the reconnect info for device
+ * @version; version for userspace APP
+ * @reconnected: indetify if this is reconnected.userspace APP needs set this
+ * to VDUSE_RECONNECT, while reconnecting.kernel will use this
+ * to indetify if this is reconnect
+ * @features; Device features negotiated in the last connect.
+ * @status; Device status in last reconnect
+ */
+
+struct vduse_dev_reconnect_data {
+ __u32 version;
+#define VDUSE_RECONNECT 1
+#define VDUSE_NOT_RECONNECT 0
+ __u32 reconnected;
+ __u64 features;
+ __u8 status;
+};
+
+/* the reconnection mmap size for each VQ and dev status */
+#define VDUSE_RECONNCT_MMAP_SIZE PAGE_SIZE
+
#endif /* _UAPI_VDUSE_H_ */
--
2.34.3
next prev parent reply other threads:[~2023-12-05 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 8:34 [PATCH v3 0/7] vduse: Add support for reconnection Cindy Lu
2023-12-05 8:34 ` [PATCH v3 1/7] vdpa: Move struct vdpa_vq_state to uAPI Cindy Lu
2023-12-05 8:34 ` Cindy Lu [this message]
2023-12-07 8:46 ` [PATCH v3 2/7] vduse: Add new uAPI for vduse reconnection Jason Wang
2023-12-05 8:34 ` [PATCH v3 3/7] vduse: Add new ioctl VDUSE_DEV_GET_CONFIG Cindy Lu
2023-12-05 8:34 ` [PATCH v3 4/7] vduse: Add function to get/free the pages for reconnection Cindy Lu
2023-12-07 8:46 ` Jason Wang
2023-12-05 8:34 ` [PATCH v3 5/7] vduse: Add file operation for mmap Cindy Lu
2023-12-07 8:46 ` Jason Wang
2023-12-05 8:34 ` [PATCH v3 6/7] vduse: Update the vq_info in ioctl VDUSE_VQ_GET_INFO Cindy Lu
2023-12-07 8:46 ` Jason Wang
2023-12-05 8:34 ` [PATCH v3 7/7] Documentation: Add reconnect process for VDUSE Cindy Lu
2023-12-07 8:46 ` Jason Wang
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=20231205083444.3029239-3-lulu@redhat.com \
--to=lulu@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=xieyongji@bytedance.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®