From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [PATCH v2] net/virtio-user: fix cannot get initialized Date: Fri, 14 Apr 2017 12:24:23 +0800 Message-ID: <20170414042423.GI7333@yliu-dev.sh.intel.com> References: <1491551860-15005-1-git-send-email-jianfeng.tan@intel.com> <1492078287-138040-1-git-send-email-jianfeng.tan@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, maxime.coquelin@redhat.com To: Jianfeng Tan Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id EF203316B for ; Fri, 14 Apr 2017 06:27:21 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1492078287-138040-1-git-send-email-jianfeng.tan@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Apr 13, 2017 at 10:11:27AM +0000, Jianfeng Tan wrote: > The feature negotiation in virtio-user is proven to be broken, > which results in device initialization failure. > > Originally, we get features from vhost backend, and remove those > that are not supported. But when new feature is added, for example, > VIRTIO_NET_F_MTU, we fail to remove this new feature. Then, this > new feature will be negotiated, as both frontend and backend claim > to support this feature. > > To fix it, we add a macro to record supported featues, as a filter > to remove newly added features. Yes, this is much better! You now don't have to worry that virtio-user will be broken every time we add a new feature. Applied to dpdk-next-virtio, with the title changed to "fix feature negotitation". Thanks. --yliu