From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, jasowang@redhat.com, mst@redhat.com,
maxime.coquelin@redhat.com, xieyongji@bytedance.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: [RFC 4/4] vduse: update the vq_info in ioctl
Date: Wed, 28 Jun 2023 14:59:19 +0800 [thread overview]
Message-ID: <20230628065919.54042-5-lulu@redhat.com> (raw)
In-Reply-To: <20230628065919.54042-1-lulu@redhat.com>
From: Your Name <you@example.com>
in VDUSE_VQ_GET_INFO, driver will sync the last_avail_idx
with reconnect info, I have olny test the split mode, so
only use this here, will add more information later
Signed-off-by: Cindy Lu <lulu@redhat.com>
---
drivers/vdpa/vdpa_user/vduse_dev.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c b/drivers/vdpa/vdpa_user/vduse_dev.c
index 3df1256eccb4..b8e453eac0ce 100644
--- a/drivers/vdpa/vdpa_user/vduse_dev.c
+++ b/drivers/vdpa/vdpa_user/vduse_dev.c
@@ -141,6 +141,11 @@ static u32 allowed_device_id[] = {
VIRTIO_ID_NET,
};
+struct vhost_reconnect_vring {
+ uint16_t last_avail_idx;
+ bool avail_wrap_counter;
+};
+
static inline struct vduse_dev *vdpa_to_vduse(struct vdpa_device *vdpa)
{
struct vduse_vdpa *vdev = container_of(vdpa, struct vduse_vdpa, vdpa);
@@ -1176,6 +1181,17 @@ static long vduse_dev_ioctl(struct file *file, unsigned int cmd,
vq->state.split.avail_index;
vq_info.ready = vq->ready;
+ struct vdpa_reconnect_info *area;
+
+ area = &dev->reconnect_info[index];
+ struct vhost_reconnect_vring *log_reconnect;
+
+ log_reconnect = (struct vhost_reconnect_vring *)area->vaddr;
+ if (log_reconnect->last_avail_idx !=
+ vq_info.split.avail_index) {
+ vq_info.split.avail_index =
+ log_reconnect->last_avail_idx;
+ }
ret = -EFAULT;
if (copy_to_user(argp, &vq_info, sizeof(vq_info)))
--
2.34.3
next prev parent reply other threads:[~2023-06-28 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 6:59 [RFC 0/4] reconnect support in vduse Cindy Lu
2023-06-28 6:59 ` [RFC 1/4] vduse: Add the struct to save the vq reconnect info Cindy Lu
2023-06-28 8:03 ` Jason Wang
2023-07-01 9:24 ` Cindy Lu
2023-07-03 6:25 ` Jason Wang
2023-07-11 14:16 ` Maxime Coquelin
2023-06-28 6:59 ` [RFC 2/4] vduse: Add file operation for mmap Cindy Lu
2023-06-28 8:08 ` Jason Wang
2023-07-01 9:23 ` Cindy Lu
2023-07-11 14:18 ` Maxime Coquelin
2023-06-28 6:59 ` [RFC 3/4] vduse: Add the function for get/free the mapp pages Cindy Lu
2023-06-28 8:11 ` Jason Wang
2023-07-01 9:16 ` Cindy Lu
2023-06-28 6:59 ` Cindy Lu [this message]
2023-06-28 8:13 ` [RFC 4/4] vduse: update the vq_info in ioctl Jason Wang
2023-07-01 9:14 ` Cindy Lu
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=20230628065919.54042-5-lulu@redhat.com \
--to=lulu@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--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®