From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y8w1P-0002wU-D2 for qemu-devel@nongnu.org; Wed, 07 Jan 2015 14:12:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y8w1K-0003Hs-BI for qemu-devel@nongnu.org; Wed, 07 Jan 2015 14:11:59 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46628) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y8w1K-0003Hl-4a for qemu-devel@nongnu.org; Wed, 07 Jan 2015 14:11:54 -0500 Date: Wed, 7 Jan 2015 21:11:44 +0200 From: "Michael S. Tsirkin" Message-ID: <20150107191144.GC8734@redhat.com> References: <1418304322-7546-1-git-send-email-cornelia.huck@de.ibm.com> <1418304322-7546-20-git-send-email-cornelia.huck@de.ibm.com> <20141228102446.GA9260@redhat.com> <20150107172949.11f374bf.cornelia.huck@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150107172949.11f374bf.cornelia.huck@de.ibm.com> Subject: Re: [Qemu-devel] [PATCH RFC v6 19/20] virtio-blk: revision specific feature bits List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cornelia Huck Cc: thuth@linux.vnet.ibm.com, rusty@rustcorp.com.au, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org On Wed, Jan 07, 2015 at 05:29:49PM +0100, Cornelia Huck wrote: > On Sun, 28 Dec 2014 12:24:46 +0200 > "Michael S. Tsirkin" wrote: > > > On Thu, Dec 11, 2014 at 02:25:21PM +0100, Cornelia Huck wrote: > > > Wire up virtio-blk to provide different feature bit sets depending > > > on whether legacy or v1.0 has been requested. > > > > > > Note that VERSION_1 is still disabled due to missing ANY_LAYOUT support. > > > > > > Signed-off-by: Cornelia Huck > > > > So we need some way for devices to tell transports > > not to negotiate rev 1. > > Does clearing VERSION_1 have this effect? > > > I just noticed that my patch is running in circles here. > > What we need is probably the transport-dependent maximum revision > checker (which at least for ccw is acting on a device) pass in the > requested revision and check if the feature bits for the revision > include VERSION_1. Does that make sense? Just make devices set 'rev 1 supported' flag?