From mboxrd@z Thu Jan  1 00:00:00 1970
From: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH] vhost: fix MQ fails to startup
Date: Thu, 27 Apr 2017 10:05:11 +0200
Message-ID: <92318dc5-ad68-fa83-cea4-0b739a12a97f@redhat.com>
References: <1493274893-40764-1-git-send-email-zhiyong.yang@intel.com>
 <57212715-6192-dba2-418a-2418a5d14953@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: yuanhan.liu@linux.intel.com, ciara.loftus@intel.com,
 =?UTF-8?Q?Marc-Andr=c3=a9_Lureau?= <mlureau@redhat.com>
To: Zhiyong Yang <zhiyong.yang@intel.com>, dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 62716D00F
 for <dev@dpdk.org>; Thu, 27 Apr 2017 10:05:15 +0200 (CEST)
In-Reply-To: <57212715-6192-dba2-418a-2418a5d14953@redhat.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>



On 04/27/2017 09:56 AM, Maxime Coquelin wrote:
> Hi Zhiyong,
> 
> +Marc-André
> 
> On 04/27/2017 08:34 AM, Zhiyong Yang wrote:
>> vhost since dpdk17.02 + qemu2.7 and above will 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 dealing 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. DPDK code works in the right way.
> 
> I'm looking at Qemu's vhost_user_set_mem_table() function, but fail to
> see how it could wait for the reply-ack if it didn't send the
> VHOST_USER_SET_MEM_TABLE request before.

Oh, sorry, I get it now.
Are you working for a fix in Qemu, or have you already reported the
problem?

Thanks,
Maxime