From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Msd7g-0007Qv-GE for qemu-devel@nongnu.org; Tue, 29 Sep 2009 09:52:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Msd7Z-0007Ok-TA for qemu-devel@nongnu.org; Tue, 29 Sep 2009 09:52:06 -0400 Received: from [199.232.76.173] (port=57089 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Msd7Z-0007OX-Bn for qemu-devel@nongnu.org; Tue, 29 Sep 2009 09:52:01 -0400 Received: from qw-out-1920.google.com ([74.125.92.144]:61710) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Msd7Y-0003g9-GQ for qemu-devel@nongnu.org; Tue, 29 Sep 2009 09:52:00 -0400 Received: by qw-out-1920.google.com with SMTP id 5so1669857qwc.4 for ; Tue, 29 Sep 2009 06:51:59 -0700 (PDT) Message-ID: <4AC210FB.8030204@codemonkey.ws> Date: Tue, 29 Sep 2009 08:51:55 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <20090907181436.GA8538@redhat.com> <4AA60A58.4090703@redhat.com> <20090908075831.GA9875@redhat.com> <200909212039.01126.rusty@rustcorp.com.au> <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> In-Reply-To: <4AC1A49A.1010308@redhat.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: john cooper , "Michael S. Tsirkin" , Rusty Russell , qemu-devel@nongnu.org, Avi Kivity , jens.axboe@oracle.com, Vadim Rozenfeld john cooper wrote: > This is a correction to the previous version > which violated the PCI config space 256 byte > limitation. > > The crux of the feature is simply passing a qemu > received virtio serial number to/through the guest > driver and making it available to guest userspace > via a preexisting interface. > > To accomplish this, ATA IDENTIFY data as implemented > by the HDIO_GET_IDENTITY ioctl is returned to the > caller for the virtio_blk drive of interest. Content > of this identify structure is created by qemu and > passed wholesale to guest userspace without > interpretation by the guest driver. > > The change this patch implements is passing of the > identify data through a mapping established by > PCI BAR #5 rather than the PCI config area, the > latter of which resulted in the above breakage. > This is a massive layering violation. The virtio-blk ABI cannot make demands of the transport. The better solution would be to move the entire virtio-pci config space to a separate BAR that's an MMIO region. Then there is no practical limit on the size of the config area. Regards, Anthony Liguori