From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQJlq-0003jT-Ql for qemu-devel@nongnu.org; Fri, 04 May 2012 10:46:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SQJlk-0004Lj-I4 for qemu-devel@nongnu.org; Fri, 04 May 2012 10:46:10 -0400 Received: from mail-qc0-f173.google.com ([209.85.216.173]:38783) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQJlk-0004LY-EP for qemu-devel@nongnu.org; Fri, 04 May 2012 10:46:04 -0400 Received: by qcsc20 with SMTP id c20so2083836qcs.4 for ; Fri, 04 May 2012 07:46:02 -0700 (PDT) Date: Fri, 4 May 2012 10:46:00 -0400 From: Kevin O'Connor Message-ID: <20120504144600.GA4597@morn.localdomain> References: <1336119687-6295-1-git-send-email-kraxel@redhat.com> <20120504131833.GC668@morn.localdomain> <4FA3E154.7010306@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FA3E154.7010306@redhat.com> Subject: Re: [Qemu-devel] [SeaBIOS] [seabios patch 0/5] dynamic pci i/o windows List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: seabios@seabios.org, qemu-devel@nongnu.org On Fri, May 04, 2012 at 04:01:56PM +0200, Gerd Hoffmann wrote: > On 05/04/12 15:18, Kevin O'Connor wrote: > > On Fri, May 04, 2012 at 10:21:22AM +0200, Gerd Hoffmann wrote: > >> Hi, > >> > >> This patch series makes the PCI I/O windows runtime-configurable via > >> qemu firmware config interface. Main advantage is that we can size and > >> shuffle around the PCI i/O windows according to the amount of memory the > >> virtual machine has. We don't need a hole for 64bit PCI bars, we can > >> just map them above the main memory. The hole for 32bit PCI bars can be > >> enlarged for guests with less than 3.5 GB of memory. > > > > Why pass in a PCI IO range through fw_cfg if SeaBIOS can figure out an > > acceptable range from the amount of memory in the machine? > > Suggestions on how to update the pci host bridge windows in the dsdt then? Perhaps malloc_high() a struct with the info you need and then create an OperationRegion() in the dynamically generated SSDT with the address of the struct. -Kevin