From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Cindy Lu <lulu@redhat.com>,
jasowang@redhat.com, mst@redhat.com, xieyongji@bytedance.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [RFC 1/4] vduse: Add the struct to save the vq reconnect info
Date: Tue, 11 Jul 2023 16:16:52 +0200 [thread overview]
Message-ID: <3a8073d5-dab4-ed13-2c53-84ed5093bacb@redhat.com> (raw)
In-Reply-To: <20230628065919.54042-2-lulu@redhat.com>
Hello Cindy,
On 6/28/23 08:59, Cindy Lu wrote:
> From: Your Name <you@example.com>
>
> this struct is to save the reconnect info struct, in this
> struct saved the page info that alloc to save the
> reconnect info
>
> Signed-off-by: Cindy Lu <lulu@redhat.com>
> ---
> drivers/vdpa/vdpa_user/vduse_dev.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c b/drivers/vdpa/vdpa_user/vduse_dev.c
> index 26b7e29cb900..f845dc46b1db 100644
> --- a/drivers/vdpa/vdpa_user/vduse_dev.c
> +++ b/drivers/vdpa/vdpa_user/vduse_dev.c
> @@ -72,6 +72,12 @@ struct vduse_umem {
> struct page **pages;
> struct mm_struct *mm;
> };
> +struct vdpa_reconnect_info {
> + u32 index;
> + phys_addr_t addr;
> + unsigned long vaddr;
> + phys_addr_t size;
> +};
>
> struct vduse_dev {
> struct vduse_vdpa *vdev;
> @@ -106,6 +112,7 @@ struct vduse_dev {
> u32 vq_align;
> struct vduse_umem *umem;
> struct mutex mem_lock;
> + struct vdpa_reconnect_info reconnect_info[64];
Why 64?
Shouldn't it be part of struct vduse_virtqueue instead?
> };
>
> struct vduse_dev_msg {
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-07-11 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230628065919.54042-1-lulu@redhat.com>
[not found] ` <20230628065919.54042-2-lulu@redhat.com>
2023-06-28 8:03 ` [RFC 1/4] vduse: Add the struct to save the vq reconnect info Jason Wang
[not found] ` <CACLfguWx2hjNyyVC_JM1VBCGj3AqRZsygHJ3JGcb8erknBo-sA@mail.gmail.com>
2023-07-03 6:25 ` Jason Wang
2023-07-11 14:16 ` Maxime Coquelin [this message]
[not found] ` <20230628065919.54042-4-lulu@redhat.com>
2023-06-28 8:11 ` [RFC 3/4] vduse: Add the function for get/free the mapp pages Jason Wang
[not found] ` <20230628065919.54042-5-lulu@redhat.com>
2023-06-28 8:13 ` [RFC 4/4] vduse: update the vq_info in ioctl Jason Wang
[not found] ` <20230628065919.54042-3-lulu@redhat.com>
2023-06-28 8:08 ` [RFC 2/4] vduse: Add file operation for mmap Jason Wang
2023-07-11 14:18 ` Maxime Coquelin
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=3a8073d5-dab4-ed13-2c53-84ed5093bacb@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@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;
as well as URLs for NNTP newsgroup(s).