From: Jens Freimann <jfreiman@redhat.com>
To: Zhiyong Yang <zhiyong.yang@intel.com>
Cc: qemu-devel@nongnu.org, maxime.coquelin@redhat.com,
marcandre.lureau@gmail.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] hw/virtio: fix vhost user fails to startup when MQ
Date: Fri, 5 May 2017 09:26:46 +0200 [thread overview]
Message-ID: <20170505072646.gubg5i3uqrd5qjwn@dhcp-192-205.str.redhat.com> (raw)
In-Reply-To: <1493915136-19150-1-git-send-email-zhiyong.yang@intel.com>
On Fri, May 05, 2017 at 12:25:36AM +0800, Zhiyong Yang wrote:
> 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>
Tested-by: Jens Freimann <jfreiman@redhat.com>
next prev parent reply other threads:[~2017-05-05 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 7:09 [Qemu-devel] [PATCH] hw/virtio: fix vhost user fails to startup when MQ Zhiyong Yang
2017-05-02 12:22 ` 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 [this message]
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=20170505072646.gubg5i3uqrd5qjwn@dhcp-192-205.str.redhat.com \
--to=jfreiman@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhiyong.yang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.