From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Msjjg-0007Ps-UF for qemu-devel@nongnu.org; Tue, 29 Sep 2009 16:55:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Msjjc-0007NZ-Et for qemu-devel@nongnu.org; Tue, 29 Sep 2009 16:55:48 -0400 Received: from [199.232.76.173] (port=49282 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Msjjc-0007NW-5A for qemu-devel@nongnu.org; Tue, 29 Sep 2009 16:55:44 -0400 Received: from mail-qy0-f173.google.com ([209.85.221.173]:41837) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Msjjb-0003cH-Or for qemu-devel@nongnu.org; Tue, 29 Sep 2009 16:55:43 -0400 Received: by qyk3 with SMTP id 3so4270396qyk.4 for ; Tue, 29 Sep 2009 13:55:42 -0700 (PDT) Message-ID: <4AC2744B.1080601@codemonkey.ws> Date: Tue, 29 Sep 2009 15:55:39 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <4AB7A01A.3000206@redhat.com> <4AB8992B.7070709@redhat.com> <4AB8DD53.7070806@redhat.com> <4AB8DECA.3090908@redhat.com> <4AB8E88C.4040103@redhat.com> <4AB980E6.2070203@codemonkey.ws> <4AB9AA8E.7060800@third-harmonic.com> <4AC1A49A.1010308@redhat.com> <20090929065856.GC25389@redhat.com> <4AC1B5CD.7050702@redhat.com> <20090929085450.GE25389@redhat.com> <4AC211C8.1060202@codemonkey.ws> <4AC25599.1090400@third-harmonic.com> In-Reply-To: <4AC25599.1090400@third-harmonic.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: john cooper Cc: "Michael S. Tsirkin" , john cooper , Rusty Russell , qemu-devel@nongnu.org, Avi Kivity , jens.axboe@oracle.com, Vadim Rozenfeld john cooper wrote: > Anthony Liguori wrote: > >> 2) Passing an ATA identity page is goofy. We should just pass the >> serial number and let Linux generate the identity page. > > I have a hard time disagreeing with that comment. > > But the rationale that got us here was from the > user's perspective this information could be > trivially exposed via a preexisting interface vs. > creating a new interface as I'd done initially. > It was also pointed out other defined fields in > the identify page exist which were potentially > useful. So pressing a HDIO_GET_IDENTITY ioctl > into service here didn't seem unreasonable. virtio-blk isn't an ATA device so why pretend like it is? We can present the information we think is useful to the guest in a concise format and then if the guest wants to pretend it's an ATA device, it can create the ATA identify page on the fly. >> Just because Linux requires this as it's user space interface, that >> doesn't mean that other guests will (like Windows). Instead of >> exposing an opaque blob, we should expose the information we need in >> a structured way. > > The identify page is defined as the return of an > "identify drive" command from an ATA drive/controller. > I'd hazard it is a familiar structure in a windows > driver/userland context as well. Regards, Anthony Liguori