From: Zhiyong Yang <zhiyong.yang@intel.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, Zhiyong Yang <zhiyong.yang@intel.com>
Subject: [Qemu-devel] [PATCH] hw/virtio: fix vhost user fails to startup when MQ
Date: Fri, 28 Apr 2017 15:09:32 +0800 [thread overview]
Message-ID: <1493363372-16861-1-git-send-email-zhiyong.yang@intel.com> (raw)
Qemu2.7~2.9 and vhost user for dpdk 17.02 release work together
to cause failures of new connection when negotiating to set MQ.
(one queue pair works well).
Because there exist some bugs in qemu code when introducing
VHOST_USER_PROTOCOL_F_REPLY_ACK to qemu. When vhost_user_set_mem_table
is invoked to deal with the vhost message VHOST_USER_SET_MEM_TABLE
for the second time, qemu indeed doesn't send the messge (The message
needs to be sent only once)but still will be waiting for dpdk's reply
ack, then, qemu is always freezing, while DPDK is always waiting for
next vhost message from qemu.
The patch aims to fix the bug, MQ can work well.
The same bug is found in function vhost_user_net_set_mtu, it is fixed
at the same time.
DPDK related patch is as following:
http://www.dpdk.org/dev/patchwork/patch/23955/
Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
---
hw/virtio/vhost-user.c | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
index 9334a8a..c2c54ce 100644
--- a/hw/virtio/vhost-user.c
+++ b/hw/virtio/vhost-user.c
@@ -205,10 +205,11 @@ static int vhost_user_write(struct vhost_dev *dev, VhostUserMsg *msg,
/*
* For non-vring specific requests, like VHOST_USER_SET_MEM_TABLE,
* we just need send it once in the first time. For later such
- * request, we just ignore it.
+ * request, we just ignore it. In this case, return value is 1 which is
+ * different from 0 that stands for message written successfully.
*/
if (vhost_user_one_time_request(msg->request) && dev->vq_index != 0) {
- return 0;
+ return 1;
}
if (qemu_chr_fe_set_msgfds(chr, fds, fd_num) < 0) {
@@ -270,7 +271,7 @@ static int vhost_user_set_mem_table(struct vhost_dev *dev,
struct vhost_memory *mem)
{
int fds[VHOST_MEMORY_MAX_NREGIONS];
- int i, fd;
+ int i, fd, ret;
size_t fd_num = 0;
bool reply_supported = virtio_has_feature(dev->protocol_features,
VHOST_USER_PROTOCOL_F_REPLY_ACK);
@@ -315,11 +316,12 @@ static int vhost_user_set_mem_table(struct vhost_dev *dev,
msg.size += sizeof(msg.payload.memory.padding);
msg.size += fd_num * sizeof(VhostUserMemoryRegion);
- if (vhost_user_write(dev, &msg, fds, fd_num) < 0) {
+ ret = vhost_user_write(dev, &msg, fds, fd_num);
+ if (ret < 0) {
return -1;
}
- if (reply_supported) {
+ if (reply_supported && (ret == 0)) {
return process_message_reply(dev, msg.request);
}
@@ -691,6 +693,7 @@ static bool vhost_user_can_merge(struct vhost_dev *dev,
static int vhost_user_net_set_mtu(struct vhost_dev *dev, uint16_t mtu)
{
VhostUserMsg msg;
+ int ret;
bool reply_supported = virtio_has_feature(dev->protocol_features,
VHOST_USER_PROTOCOL_F_REPLY_ACK);
@@ -706,12 +709,13 @@ static int vhost_user_net_set_mtu(struct vhost_dev *dev, uint16_t mtu)
msg.flags |= VHOST_USER_NEED_REPLY_MASK;
}
- if (vhost_user_write(dev, &msg, NULL, 0) < 0) {
+ ret = vhost_user_write(dev, &msg, NULL, 0);
+ if (ret < 0) {
return -1;
}
/* If reply_ack supported, slave has to ack specified MTU is valid */
- if (reply_supported) {
+ if (reply_supported && (ret == 0)) {
return process_message_reply(dev, msg.request);
}
--
2.7.4
next reply other threads:[~2017-04-28 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 7:09 Zhiyong Yang [this message]
2017-05-02 12:22 ` [Qemu-devel] [PATCH] hw/virtio: fix vhost user fails to startup when MQ Maxime Coquelin
2017-05-03 3:07 ` Yang, Zhiyong
2017-05-03 12:37 ` Marc-André Lureau
2017-05-04 14:02 ` Yang, Zhiyong
2017-05-04 16:25 ` [Qemu-devel] [PATCH v2] " Zhiyong Yang
2017-05-04 21:10 ` Marc-André Lureau
2017-05-05 7:26 ` Jens Freimann
2017-05-05 7:34 ` Maxime Coquelin
2017-05-05 20:37 ` 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=1493363372-16861-1-git-send-email-zhiyong.yang@intel.com \
--to=zhiyong.yang@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).