From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MsxrQ-0005uq-2x for qemu-devel@nongnu.org; Wed, 30 Sep 2009 08:00:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MsxrL-0005t3-Gm for qemu-devel@nongnu.org; Wed, 30 Sep 2009 08:00:43 -0400 Received: from [199.232.76.173] (port=49678 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MsxrL-0005sv-1z for qemu-devel@nongnu.org; Wed, 30 Sep 2009 08:00:39 -0400 Received: from ozlabs.org ([203.10.76.45]:50399) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MsxrK-0002uk-66 for qemu-devel@nongnu.org; Wed, 30 Sep 2009 08:00:38 -0400 From: Rusty Russell Date: Wed, 30 Sep 2009 21:30:32 +0930 References: <4AB7A01A.3000206@redhat.com> <200909301049.08434.rusty@rustcorp.com.au> <4AC2BF9C.9050403@codemonkey.ws> In-Reply-To: <4AC2BF9C.9050403@codemonkey.ws> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200909302130.33454.rusty@rustcorp.com.au> Subject: [Qemu-devel] Re: [PATCH 0/2] fix virtio_blk serial pci config breakage List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: john cooper , "Michael S. Tsirkin" , john cooper , qemu-devel@nongnu.org, Avi Kivity , jens.axboe@oracle.com, Vadim Rozenfeld On Wed, 30 Sep 2009 11:47:00 am Anthony Liguori wrote: > Rusty Russell wrote: > > On Wed, 30 Sep 2009 06:25:39 am Anthony Liguori wrote: > > > >> virtio-blk isn't an ATA device so why pretend like it is? ... > That's an argument to implement the HDIO_GET_IDENTITY ioctl in the Linux > virtio-blk driver. That's a totally reasonable thing to do. Your second sentence contradicts your first here. If it's reasonable to imitate ATA in Linux, it's reasonable to imitate ATA in virtio. Using an existing standard should always be the default; one should need a compelling reason *not* to do so. In practice, (1) that code already exists in kvm, and (2) it makes the Linux implementation trivial. So, what are the real arguments? (1) Some fields are redundant (eg. geometry) with existing fields already. (2) Future fields will have to decide whether to use ATA IDENTIFY or normal features, (3) We don't know enough about ATA IDENTIFY to do a decent job of filling it in. I can buy (1), but I still have to deal with (2) and (3) if they're inside the virtio_blk driver anyway. Anything else? Rusty.