From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MqH8T-0006kB-4e for qemu-devel@nongnu.org; Tue, 22 Sep 2009 21:59:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MqH8O-0006hq-Bv for qemu-devel@nongnu.org; Tue, 22 Sep 2009 21:59:12 -0400 Received: from [199.232.76.173] (port=56837 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MqH8O-0006hi-7D for qemu-devel@nongnu.org; Tue, 22 Sep 2009 21:59:08 -0400 Received: from qw-out-1920.google.com ([74.125.92.149]:52558) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MqH8N-0007ZI-OD for qemu-devel@nongnu.org; Tue, 22 Sep 2009 21:59:07 -0400 Received: by qw-out-1920.google.com with SMTP id 5so111172qwc.4 for ; Tue, 22 Sep 2009 18:59:07 -0700 (PDT) Message-ID: <4AB980E6.2070203@codemonkey.ws> Date: Tue, 22 Sep 2009 20:59:02 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] qemu: make virtio-blk PCI compliant by default 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> In-Reply-To: <4AB8E88C.4040103@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: john cooper Cc: qemu-devel@nongnu.org, jens.axboe@oracle.com, Rusty Russell , Avi Kivity , "Michael S. Tsirkin" john cooper wrote: > Avi Kivity wrote: > >> On 09/22/2009 05:21 PM, john cooper wrote: >> >>>> Can we just read this page as a virtqueue command instead of having it >>>> mapped permanently? >>>> >>>> >>> Probably although I hadn't looked specifically >>> at doing so. Mapping the data via an unused >>> pci bar is pretty trivial and seemed minimally >>> intrusive to the existing driver. >>> >>> >> We'll run out of bars if we expend them like that. >> > > Agreed. However my motivation here was to use a > single additional bar specifically to compensate > for the PCI spec imposed 256 byte size limitation > of the config space mapping. As we're defining the > content/size of this area, future use to accommodate > additional data should be unrestricted. > Why expose the whole ATAPI page instead of just the serial number? I think the proper solution is to move the config to a separate bar that's MMIO instead of PIO. config access is never performance sensitive and an MMIO bar has less restrictions on size. Regards, Anthony Liguori