From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55108) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tkyxl-0006XB-2C for qemu-devel@nongnu.org; Tue, 18 Dec 2012 10:20:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TkyxH-00037t-Sc for qemu-devel@nongnu.org; Tue, 18 Dec 2012 10:20:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:22056) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TkyxH-00037b-Hx for qemu-devel@nongnu.org; Tue, 18 Dec 2012 10:19:39 -0500 Date: Tue, 18 Dec 2012 17:22:40 +0200 From: "Michael S. Tsirkin" Message-ID: <20121218152239.GE27400@redhat.com> References: <1355144985-12897-1-git-send-email-stefanha@redhat.com> <1355144985-12897-13-git-send-email-stefanha@redhat.com> <20121216160853.GC15790@redhat.com> <20121218145717.GA11063@stefanha-thinkpad.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121218145717.GA11063@stefanha-thinkpad.redhat.com> Subject: Re: [Qemu-devel] [PATCH v6 12/12] virtio-blk: add x-data-plane=on|off performance feature List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Kevin Wolf , Anthony Liguori , rusty@rustcorp.com.au, yvugenfi@redhat.com, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , khoa@us.ibm.com, Stefan Hajnoczi , Paolo Bonzini , Asias He On Tue, Dec 18, 2012 at 03:57:17PM +0100, Stefan Hajnoczi wrote: > > > @@ -407,6 +409,14 @@ static void virtio_blk_handle_output(VirtIODevice *vdev, VirtQueue *vq) > > > .num_writes = 0, > > > }; > > > > > > + /* Some guests kick before setting VIRTIO_CONFIG_S_DRIVER_OK so start > > > + * dataplane here instead of waiting for .set_status(). > > > + */ > > > > By the way which guests are these? > > I ran a Windows 8 guest today with build 48 virtio-win drivers. It > notifies before the device gets its .set_status() callback invoked. > But I could swear I've seen Linux guests do this too. That's very broken. But looking at linux drivers it also seems linux guests do this even today. We have: err = drv->probe(dev); if (err) add_status(dev, VIRTIO_CONFIG_S_FAILED); else { add_status(dev, VIRTIO_CONFIG_S_DRIVER_OK); if (drv->scan) drv->scan(dev); } this means that unless drivers implement scan() they will make device active before DRIVER_OK is written as the result linux can access it and kick. And almost no drivers implement scan. Nasty. Rusty, what do you think? Worth fixing? It does mean that for now we are stuck with a work around, but I think we need it in virtio core in qemu, it's not dataplane specific. -- MST