From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33360) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VbVKr-0005tc-J3 for qemu-devel@nongnu.org; Wed, 30 Oct 2013 08:57:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VbVKl-0008GR-KI for qemu-devel@nongnu.org; Wed, 30 Oct 2013 08:57:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32549) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VbVKl-0008GG-7X for qemu-devel@nongnu.org; Wed, 30 Oct 2013 08:57:15 -0400 Message-ID: <1383137830.22559.29.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Wed, 30 Oct 2013 13:57:10 +0100 In-Reply-To: <20131029185242.GC20848@redhat.com> References: <1383051455-28188-1-git-send-email-imammedo@redhat.com> <20131029151047.GA20242@redhat.com> <20131029162825.6fe5a0ae@nial.usersys.redhat.com> <20131029185242.GC20848@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/2 v2] pc: inform SeaBIOS where 64-bit PCI hole begins List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Igor Mammedov , pbonzini@redhat.com, qemu-devel@nongnu.org, aliguori@amazon.com, afaerber@suse.de Hi, > > Well, BIOS have to know where it could start 64-bit BARs mappings > > and > > telling it explicitly where, looks like a good way to do it. > > As far as I can tell, BIOS can start any mappings anywhere it wants to > as long as they don't overlap anything else. > What is has to know is what hardware is there. Use case is memory hotplug. Once we generate the acpi tables in qemu seabios doesn't need to know anything about hotpluggable memory slots. Still it better should not map 64bit pci bars into that address space. So it IMHO makes sense to give seabios a hit where it should map the 64bit pci bars. cheers, Gerd