From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39172) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZ1qH-00054G-D2 for qemu-devel@nongnu.org; Thu, 25 Feb 2016 14:44:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZ1qD-0003lp-6W for qemu-devel@nongnu.org; Thu, 25 Feb 2016 14:44:53 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46400) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZ1qD-0003lh-0R for qemu-devel@nongnu.org; Thu, 25 Feb 2016 14:44:49 -0500 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id CE73235A805 for ; Thu, 25 Feb 2016 19:44:47 +0000 (UTC) Date: Thu, 25 Feb 2016 21:44:44 +0200 From: "Michael S. Tsirkin" Message-ID: <20160225214231-mutt-send-email-mst@redhat.com> References: <20160225135613-mutt-send-email-mst@redhat.com> <56CEF746.1070502@redhat.com> <56CEFAD9.3030803@redhat.com> <20160225153043-mutt-send-email-mst@redhat.com> <56CF0A14.5060607@redhat.com> <20160225161735-mutt-send-email-mst@redhat.com> <56CF3BF4.1070706@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56CF3BF4.1070706@redhat.com> Subject: Re: [Qemu-devel] how Windows treats BARs of driver-less devices when other devices are hotplugged List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Igor Mammedov , qemu devel list , Gerd Hoffmann On Thu, Feb 25, 2016 at 06:37:56PM +0100, Laszlo Ersek wrote: > On 02/25/16 15:18, Michael S. Tsirkin wrote: > > On Thu, Feb 25, 2016 at 03:05:08PM +0100, Laszlo Ersek wrote: > >> On 02/25/16 14:30, Michael S. Tsirkin wrote: > > >>> virtio? > >> > >> ... was my first thought as well, but OVMF at the moment supports only > >> legacy (0.9.5) virtio-pci devices > > > > Oh. We'll have to fix that too :( > > Yes, there's a BZ open about it. It's very big work. Due to independent > reasons, I skimmed the virtio 1.0 spec the other day, specifically for > seeing what it would take to port the OVMF drivers forward to virtio > 1.0. It's going to be a *lot* of work. A hint: review at least cs03 or latest draft csprd05. First hint on google is ancient draft csprd01. > >> (and virtio-mmio only on AARCH64) -- > >> those don't have MMIO BARs, only IO BARs. > > > > Well that's not exactly true - there is an MSI-X BAR. > > Maybe OVMF does not enable that, though. > > Correct. > > The virtio stuff in OVMF adheres extremely closely to the 0.9.5 spec > (and the actual QEMU code was only studied when the guest wouldn't work > as described by the 0.9.5 spec -- this usually boiled down to silent > framing assumptions made by QEMU, and then the guest code was > accomodated), but the virtio code in OVMF is purposely absolutely > minimal, feature-wise. > > I also looked up Gerd's virtio 1.0 patch series in the SeaBIOS git > history (from summer 2015, IIRC). It was extensive. Extrapolating from > that, you can imagine what it will take for OVMF. > > Thanks > Laszlo Basically the same amount as seabios I guess. -- MST