From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id C8F40F8AA for ; Wed, 4 Jan 2017 08:22:12 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga105.jf.intel.com with ESMTP; 03 Jan 2017 23:22:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,458,1477983600"; d="scan'208";a="25928554" Received: from shwdeisgchi083.ccr.corp.intel.com (HELO [10.239.67.193]) ([10.239.67.193]) by orsmga002.jf.intel.com with ESMTP; 03 Jan 2017 23:22:10 -0800 To: Yuanhan Liu References: <1480689075-66977-1-git-send-email-jianfeng.tan@intel.com> <1482477266-39199-1-git-send-email-jianfeng.tan@intel.com> <1482477266-39199-6-git-send-email-jianfeng.tan@intel.com> <20161226074437.GD19288@yliu-dev.sh.intel.com> Cc: dev@dpdk.org, ferruh.yigit@intel.com, cunming.liang@intel.com From: "Tan, Jianfeng" Message-ID: <59e32f20-fe7a-20ad-1aa6-99fc90322a42@intel.com> Date: Wed, 4 Jan 2017 15:22:08 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <20161226074437.GD19288@yliu-dev.sh.intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2 5/7] net/virtio_user: add vhost kernel support 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: Wed, 04 Jan 2017 07:22:13 -0000 Sorry, I forget to reply this comment. On 12/26/2016 3:44 PM, Yuanhan Liu wrote: > [...] >> + >> + /* Does not work when VIRTIO_F_IOMMU_PLATFORM now, why? */ > Because this feature need the vhost IOTLB support from the device > emulation. Patches for QEMU hasn't been merged yet, but it has been > there for a while. Yes. And it's in need of help from QEMU. > > Since we don't have the support yet, for sure it won't work. But > I'm wondering why you have to disable it explicitly? Here we do not have QEMU. Frontend driver talks with vhost-net through virtio_user_dev. And both ends claim to support VIRTIO_F_IOMMU_PLATFORM. So this feature bit will be negotiated if we don't explicitly disable it. In my previous test, it fails in vhost_init_device_iotlb() of vhost kernel module. My guess is that, for this feature, without the help of QEMU, vhost kernel module cannot work independently. Thanks, Jianfeng