From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33894) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoWfF-00038B-1S for qemu-devel@nongnu.org; Wed, 12 Nov 2014 07:04:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XoWf8-0000RN-PC for qemu-devel@nongnu.org; Wed, 12 Nov 2014 07:04:44 -0500 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:40195) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoWf8-0000RI-Fm for qemu-devel@nongnu.org; Wed, 12 Nov 2014 07:04:38 -0500 Date: Wed, 12 Nov 2014 12:04:19 +0000 From: Mark Rutland Message-ID: <20141112120419.GE28015@leverpostej> References: <20141030180216.GD31629@leverpostej> <5459F4CB.1000009@huawei.com> <20141111152932.GA25295@leverpostej> <20141111163101.GB23267@cbox> <20141111164807.GC25295@leverpostej> <20141111213312.GC19598@cbox> <20141112103854.GA28015@leverpostej> <546349F6.10300@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <546349F6.10300@redhat.com> Subject: Re: [Qemu-devel] [Linaro-acpi] [RFC PATCH 0/7] hw/arm/virt: Dynamic ACPI v5.1 table generation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Peter Maydell , "Ian.Campbell@citrix.com" , "linaro-acpi@lists.linaro.org" , Alexander Spyridakis , Julien Grall , Claudio Fontana , QEMU Developers , Leif Lindholm , "stefano.stabellini@citrix.com" , "grant.likely@linaro.org" , "tech@virtualopensystems.com" , Parth Dixit , Christoffer Dall On Wed, Nov 12, 2014 at 11:52:22AM +0000, Paolo Bonzini wrote: > > On 12/11/2014 11:38, Mark Rutland wrote: > > > I share your concern, but running another UEFI instance for Dom0 doesn't > > > seem like a viable alternative either. Why is this a problem on ARM and > > > not on x86 though? > > > > I believe that on x86 the fallback for !UEFI would be the e820 memory > > map, which provides info regarding the type of the memory mapping, as > > opposed to just the base + size. That said, I'm not that familiar with > > e820, and from a quick look the provided information doesn't seem to be > > that detailed. > > The e820 memory map is only part of it. On x86 !UEFI you are supposed > to scan low memory for magic signatures that provides pointers to the > SMBIOS and ACPI tables. Fun... > As Christoffer said, "the good old PC". :) > > SeaBIOS fishes out information from fw_cfg, and puts it in low memory. > On ARM you could use DT binary blobs instead of fw_cfg, as proposed > already (I don't remember if it was in this thread or IRC). Then if you > want to go !UEFI you can extract the tables from those binary blobs. This sounds broken. I am very much not a fan of shoving binary blobs into DT to workaround a shoddy boot interface. Mark.