From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [PATCH v2] vhost: Fix default value of kickfd and callfd Date: Fri, 11 Mar 2016 15:19:07 +0800 Message-ID: <20160311071907.GI979@yliu-dev.sh.intel.com> References: <1457590462-3680-1-git-send-email-mukawa@igel.co.jp> <1457593565-16240-1-git-send-email-mukawa@igel.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Tetsuya Mukawa Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 531172BF3 for ; Fri, 11 Mar 2016 08:16:16 +0100 (CET) Content-Disposition: inline In-Reply-To: <1457593565-16240-1-git-send-email-mukawa@igel.co.jp> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Mar 10, 2016 at 04:06:05PM +0900, Tetsuya Mukawa wrote: > Currently, default values of kickfd and callfd are -1. > If the values are -1, current code guesses kickfd and callfd haven't > been initialized yet. And vhost library will guess the virtqueue isn't > ready for processing. > But callfd and kickfd will be set as -1 when "--enable-kvm" > isn't specified in QEMU command line. It means we cannot treat -1 as > uninitialized state. The patch changes default values to -2. And the > patch defines -2 as VIRTIO_UNINITIALIZED_EVENTFD. This looks more like a workaround to me. Besides, this patch would make following fail: eventfd_write(vq->callfd, (eventfd_t)1); --yliu