From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56205) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYzrW-0001Jk-Pl for qemu-devel@nongnu.org; Thu, 25 Feb 2016 12:38:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYzrT-0001DN-KD for qemu-devel@nongnu.org; Thu, 25 Feb 2016 12:38:02 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51583) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYzrT-0001D2-FY for qemu-devel@nongnu.org; Thu, 25 Feb 2016 12:37:59 -0500 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id E50567EBAE for ; Thu, 25 Feb 2016 17:37:58 +0000 (UTC) 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> From: Laszlo Ersek Message-ID: <56CF3BF4.1070706@redhat.com> Date: Thu, 25 Feb 2016 18:37:56 +0100 MIME-Version: 1.0 In-Reply-To: <20160225161735-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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: "Michael S. Tsirkin" Cc: Igor Mammedov , qemu devel list , Gerd Hoffmann 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. >> (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