From: luzhixing12345 <luzhixing12345@gmail.com>
To: sgarzare@redhat.com
Cc: luzhixing12345@gmail.com, mst@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] vhost-user: add NEED_REPLY flag
Date: Fri, 6 Sep 2024 09:50:26 +0800 [thread overview]
Message-ID: <20240906015026.17138-1-luzhixing12345@gmail.com> (raw)
In-Reply-To: <gtpj4yn3kkvawrjlcdq7zrg7bsfe2wlt2x5eh3pfmiygzkoxtc@pyak5vt5ap3a>
Signed-off-by: luzhixing12345 <luzhixing12345@gmail.com>
>On Mon, Aug 12, 2024 at 12:53:19PM GMT, 陆知行 wrote:
>>Hi, can someone review this patch?
>>I find requests which call vhost_user_get_u64 does not set NEED_REPLY flag
>
>Can you provide an example to trigger this issue?
>
>Also, with this change all calls to vhost_user_get_u64() will set that
>flag, is that following the vhost-user user specification?
It will not trigger a bug.
For each function that calls vhost_user_get_u64() like vhost_user_get_features/vhost_user_get_status, if you set a breakpoint in gdb at subprojects/libvhost-user/libvhost-user.c/vu_dispatch and you will find that
```
bool
vu_dispatch(VuDev *dev)
{
// ...
need_reply = vmsg.flags & VHOST_USER_NEED_REPLY_MASK; // 0
reply_requested = vu_process_message(dev, &vmsg); // 1
// ...
}
vhost-user protocol doc list some requests that need reply like VHOST_USER_GET_FEATURES/VHOST_USER_GET_PROTOCOL_FEATURES, the flag should be set with NEED_REPLY_MASK.
The current code does not raise an error because in libvhost-user(vu_process_message) it will not check this flag and always choose whether or not reply based on the request type.
So this patch fills the flag and make sure need_reply to 1 for the requests that need reply.
>Please use `scripts/checkpatch.pl` before sending patches, this one for
>example is missing SoB.
>
>Thanks,
>Stefano
>
>>
>>luzhixing12345 <luzhixing12345@gmail.com> 于2024年8月4日周日 23:50写道:
>>
>>> Front-end message requests which need reply should set NEED_REPLY_MASK
>>> in flag, and response from slave need clear NEED_REPLY_MASK flag.
>>>
>>> ---
>>> hw/virtio/vhost-user.c | 2 +-
>>> subprojects/libvhost-user/libvhost-user.c | 1 +
>>> 2 files changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
>>> index 00561daa06..edf2271e0a 100644
>>> --- a/hw/virtio/vhost-user.c
>>> +++ b/hw/virtio/vhost-user.c
>>> @@ -1082,7 +1082,7 @@ static int vhost_user_get_u64(struct vhost_dev *dev,
>>> int request, uint64_t *u64)
>>> int ret;
>>> VhostUserMsg msg = {
>>> .hdr.request = request,
>>> - .hdr.flags = VHOST_USER_VERSION,
>>> + .hdr.flags = VHOST_USER_VERSION | VHOST_USER_NEED_REPLY_MASK,
>>> };
>>>
>>> if (vhost_user_per_device_request(request) && dev->vq_index != 0) {
>>> diff --git a/subprojects/libvhost-user/libvhost-user.c
>>> b/subprojects/libvhost-user/libvhost-user.c
>>> index 9c630c2170..40f665bd7f 100644
>>> --- a/subprojects/libvhost-user/libvhost-user.c
>>> +++ b/subprojects/libvhost-user/libvhost-user.c
>>> @@ -667,6 +667,7 @@ vu_send_reply(VuDev *dev, int conn_fd, VhostUserMsg
>>> *vmsg)
>>> {
>>> /* Set the version in the flags when sending the reply */
>>> vmsg->flags &= ~VHOST_USER_VERSION_MASK;
>>> + vmsg->flags &= ~VHOST_USER_NEED_REPLY_MASK;
>>> vmsg->flags |= VHOST_USER_VERSION;
>>> vmsg->flags |= VHOST_USER_REPLY_MASK;
>>>
>>> --
>>> 2.34.1
>>>
>>>
next prev parent reply other threads:[~2024-09-06 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 15:48 [PATCH] vhost-user: add NEED_REPLY flag luzhixing12345
2024-08-12 4:53 ` 陆知行
2024-08-27 13:29 ` Stefano Garzarella
2024-09-06 1:50 ` luzhixing12345 [this message]
2024-09-10 15:23 ` Michael S. Tsirkin
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=20240906015026.17138-1-luzhixing12345@gmail.com \
--to=luzhixing12345@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.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).