From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 54CF9316B for ; Fri, 14 Apr 2017 07:55:21 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Apr 2017 22:55:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,197,1488873600"; d="scan'208";a="845927720" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by FMSMGA003.fm.intel.com with ESMTP; 13 Apr 2017 22:55:20 -0700 Received: from fmsmsx101.amr.corp.intel.com (10.18.124.199) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 13 Apr 2017 22:55:20 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx101.amr.corp.intel.com (10.18.124.199) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 13 Apr 2017 22:55:19 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.117]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.193]) with mapi id 14.03.0319.002; Fri, 14 Apr 2017 13:55:17 +0800 From: "Tan, Jianfeng" To: Yuanhan Liu CC: "dev@dpdk.org" , "maxime.coquelin@redhat.com" Thread-Topic: [PATCH v2] net/virtio-user: fix cannot get initialized Thread-Index: AQHStD4/Rg593vZ12UC4OITHTWR256HDv2OAgACIsaD//4vHAIAAivIQ Date: Fri, 14 Apr 2017 05:55:17 +0000 Message-ID: References: <1491551860-15005-1-git-send-email-jianfeng.tan@intel.com> <1492078287-138040-1-git-send-email-jianfeng.tan@intel.com> <20170414042423.GI7333@yliu-dev.sh.intel.com> <20170414053738.GL7333@yliu-dev.sh.intel.com> In-Reply-To: <20170414053738.GL7333@yliu-dev.sh.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2] net/virtio-user: fix cannot get initialized X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2017 05:55:21 -0000 > -----Original Message----- > From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com] > Sent: Friday, April 14, 2017 1:38 PM > To: Tan, Jianfeng > Cc: dev@dpdk.org; maxime.coquelin@redhat.com > Subject: Re: [PATCH v2] net/virtio-user: fix cannot get initialized >=20 > On Fri, Apr 14, 2017 at 04:35:57AM +0000, Tan, Jianfeng wrote: > > > > > > > -----Original Message----- > > > From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com] > > > Sent: Friday, April 14, 2017 12:24 PM > > > To: Tan, Jianfeng > > > Cc: dev@dpdk.org; maxime.coquelin@redhat.com > > > Subject: Re: [PATCH v2] net/virtio-user: fix cannot get initialized > > > > > > 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-use= r > > > will be broken every time we add a new feature. > > > > > > Applied to dpdk-next-virtio, with the title changed to "fix feature > > > negotitation". > > > > > > > Thanks. By the way, it's better backporting it to stable branches, howe= ver, I > forget to CC stable@dpdk.org. >=20 > As long as we don't backport new features to a stable release, there > should be no problem. >=20 > Besides, the virtio-user features supported in this patch may not match > those supported by a stable release (say 16.11 LTS). For example, F_STATU= S > is just added in this feature. Thus, I don't think it's a good candidate > for a stable release (though a backport could fix it). Make sense. Thanks! Jianfeng