From: "Eugenio Pérez" <eperezma@redhat.com>
To: jasowang@redhat.com
Cc: "Yongji Xie" <xieyongji@bytedance.com>,
"Cindy Lu" <lulu@redhat.com>,
linux-kernel@vger.kernel.org,
"Eugenio Pérez" <eperezma@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Maxime Coquelin" <mcoqueli@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux.dev,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Laurent Vivier" <lvivier@redhat.com>
Subject: [RFC 5/6] vduse: reset group asid in reset
Date: Fri, 6 Jun 2025 13:50:11 +0200 [thread overview]
Message-ID: <20250606115012.1331551-6-eperezma@redhat.com> (raw)
In-Reply-To: <20250606115012.1331551-1-eperezma@redhat.com>
Is the expected behavior with vdpa_sim and mlx.
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
---
drivers/vdpa/vdpa_user/vduse_dev.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c b/drivers/vdpa/vdpa_user/vduse_dev.c
index 151c6d133e76..5f0032df43b8 100644
--- a/drivers/vdpa/vdpa_user/vduse_dev.c
+++ b/drivers/vdpa/vdpa_user/vduse_dev.c
@@ -445,6 +445,9 @@ static __poll_t vduse_dev_poll(struct file *file, poll_table *wait)
return mask;
}
+static int vduse_set_group_asid(struct vdpa_device *vdpa, unsigned int group,
+ unsigned int asid);
+
static void vduse_dev_reset(struct vduse_dev *dev)
{
int i;
@@ -457,6 +460,9 @@ static void vduse_dev_reset(struct vduse_dev *dev)
vduse_domain_reset_bounce_map(domain);
}
+ for (i = 0; i < dev->ngroups; i++)
+ vduse_set_group_asid(&dev->vdev->vdpa, i, 0);
+
down_write(&dev->rwsem);
dev->status = 0;
--
2.49.0
next prev parent reply other threads:[~2025-06-06 11:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 11:50 [RFC 0/6] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-06-06 11:50 ` [RFC 1/6] vduse: add v1 API definition Eugenio Pérez
2025-06-09 1:41 ` Jason Wang
2025-06-09 1:50 ` Jason Wang
2025-06-09 6:10 ` Eugenio Perez Martin
2025-06-10 8:35 ` Jason Wang
2025-08-07 10:55 ` Eugenio Perez Martin
2025-08-08 0:50 ` Jason Wang
2025-08-10 10:18 ` Eugenio Perez Martin
2025-08-11 2:58 ` Jason Wang
2025-08-11 9:01 ` Eugenio Perez Martin
2025-08-12 2:55 ` Jason Wang
2025-08-12 6:03 ` Eugenio Perez Martin
2025-06-06 11:50 ` [RFC 2/6] vduse: add vq group support Eugenio Pérez
2025-06-09 1:55 ` Jason Wang
2025-06-09 6:03 ` Eugenio Perez Martin
2025-06-10 8:53 ` Jason Wang
2025-06-06 11:50 ` [RFC 3/6] vduse: add vq group asid support Eugenio Pérez
2025-06-12 0:30 ` Jason Wang
2025-06-12 7:24 ` Eugenio Perez Martin
2025-06-13 1:21 ` Jason Wang
2025-08-07 11:10 ` Eugenio Perez Martin
2025-06-06 11:50 ` [RFC 4/6] vduse: send update_iotlb_v2 message Eugenio Pérez
2025-06-06 11:50 ` Eugenio Pérez [this message]
2025-06-12 0:32 ` [RFC 5/6] vduse: reset group asid in reset Jason Wang
2025-06-12 7:24 ` Eugenio Perez Martin
2025-06-06 11:50 ` [RFC 6/6] vduse: bump version number Eugenio Pérez
2025-06-09 5:51 ` [RFC 0/6] Add multiple address spaces support to VDUSE Christoph Hellwig
2025-06-20 6:25 ` Eugenio Perez Martin
2025-06-23 5:09 ` Christoph Hellwig
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=20250606115012.1331551-6-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mcoqueli@redhat.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xieyongji@bytedance.com \
--cc=xuanzhuo@linux.alibaba.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®