From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42449) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XExC9-0000st-U7 for qemu-devel@nongnu.org; Wed, 06 Aug 2014 05:07:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XExC3-0000FY-Pd for qemu-devel@nongnu.org; Wed, 06 Aug 2014 05:07:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55878) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XExC3-0000FI-IN for qemu-devel@nongnu.org; Wed, 06 Aug 2014 05:07:35 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7697Ylp018024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 6 Aug 2014 05:07:35 -0400 Date: Wed, 6 Aug 2014 17:07:53 +0800 From: Fam Zheng Message-ID: <20140806090753.GA1484@T430.redhat.com> References: <1407303308-4615-1-git-send-email-famz@redhat.com> <1407303308-4615-10-git-send-email-famz@redhat.com> <53E1EB1B.4040304@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53E1EB1B.4040304@redhat.com> Subject: Re: [Qemu-devel] [RFC PATCH v2 09/10] virtio-scsi-dataplane: Code to run virtio-scsi on iothread List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com On Wed, 08/06 10:45, Paolo Bonzini wrote: > Il 06/08/2014 07:35, Fam Zheng ha scritto: > > ifeq ($(CONFIG_VIRTIO),y) > > -obj-y += virtio-scsi.o > > +obj-y += virtio-scsi.o virtio-scsi-dataplane.o > > obj-$(CONFIG_VHOST_SCSI) += vhost-scsi.o > > endif > > I first thought that this must be conditional on > CONFIG_VIRTIO_BLK_DATA_PLANE. However, CONFIG_VIRTIO_BLK_DATA_PLANE is > itself obsolete: > > ########################################## > # adjust virtio-blk-data-plane based on linux-aio > > if test "$virtio_blk_data_plane" = "yes" -a \ > "$linux_aio" != "yes" ; then > error_exit "virtio-blk-data-plane requires Linux AIO, please try --enable-linux-aio" > elif test -z "$virtio_blk_data_plane" ; then > virtio_blk_data_plane=$linux_aio > fi > > and there's no requirement to have Linux AIO anymore. Can you prepare a > patch to drop CONFIG_VIRTIO_BLK_DATA_PLANE, and replace patch 1 with it? > > We can leave --disable-virtio-blk-data-plane and --enable-virtio-blk-data-plane > in for a couple of releases. > Yes. Sounds a good idea. Fam