From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52421) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1ysF-0000Yr-7V for qemu-devel@nongnu.org; Wed, 24 Jul 2013 09:13:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1ysC-0000hX-JD for qemu-devel@nongnu.org; Wed, 24 Jul 2013 09:12:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36453) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1ysC-0000hR-CC for qemu-devel@nongnu.org; Wed, 24 Jul 2013 09:12:56 -0400 Date: Wed, 24 Jul 2013 16:14:11 +0300 From: "Michael S. Tsirkin" Message-ID: <20130724131411.GB29428@redhat.com> References: <20130724060104.GA18072@redhat.com> <51EF7BDF.2070503@redhat.com> <20130724095116.GB26778@redhat.com> <51EFCFA6.2050506@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51EFCFA6.2050506@redhat.com> Subject: Re: [Qemu-devel] [PATCH] pc: limit 64 bit hole to 2G by default List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Anthony Liguori , Eduardo Habkost , qemu-devel@nongnu.org, Isaku Yamahata , Alex Williamson , Gerd Hoffmann , Laszlo Ersek , Andreas =?iso-8859-1?Q?F=E4rber?= , David Gibson On Wed, Jul 24, 2013 at 02:59:18PM +0200, Paolo Bonzini wrote: > Il 24/07/2013 11:51, Michael S. Tsirkin ha scritto: > > > Current seabios uses a slightly different approach: the 64bit hole is > > > present only in case it is actually used to map bars there, and seabios > > > tries to fit everything into the 32bit hole first. > > > > Yes. But this doesn't work with device hotplug. > > Are you preserving that behavior for older machine types? Older machine types (1.5 and back) don't report PCI hole size to guests so there's nothing to preserve. This means there's not much I can do for pc-1.5: as before this patch, hotplug of devices with large BARs won't work, and some windows guests will crash if a device with a huge BAR is added statically. > (Also, what happens if you do -global i440FX-pcihost.pci_hole64_size=0? > Does that return a _CRS with only the 32-bit hole)? > > Paolo Yes.