From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59304) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoWTU-000674-Om for qemu-devel@nongnu.org; Wed, 12 Nov 2014 06:52:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XoWTL-0005TT-OE for qemu-devel@nongnu.org; Wed, 12 Nov 2014 06:52:36 -0500 Received: from mail-wg0-x230.google.com ([2a00:1450:400c:c00::230]:50729) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoWTL-0005TE-I9 for qemu-devel@nongnu.org; Wed, 12 Nov 2014 06:52:27 -0500 Received: by mail-wg0-f48.google.com with SMTP id y19so3136926wgg.21 for ; Wed, 12 Nov 2014 03:52:26 -0800 (PST) Sender: Paolo Bonzini Message-ID: <546349F6.10300@redhat.com> Date: Wed, 12 Nov 2014 12:52:22 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1414691045-4793-1-git-send-email-a.spyridakis@virtualopensystems.com> <20141030180216.GD31629@leverpostej> <5459F4CB.1000009@huawei.com> <20141111152932.GA25295@leverpostej> <20141111163101.GB23267@cbox> <20141111164807.GC25295@leverpostej> <20141111213312.GC19598@cbox> <20141112103854.GA28015@leverpostej> In-Reply-To: <20141112103854.GA28015@leverpostej> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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: Mark Rutland , Christoffer Dall 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 , "tech@virtualopensystems.com" , Parth Dixit 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. 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. Paolo