From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48129) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhGX1-0005jn-UX for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:26:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XhGWv-00071o-SG for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:26:15 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38394 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XhGWv-00071f-Mp for qemu-devel@nongnu.org; Thu, 23 Oct 2014 07:26:09 -0400 Message-ID: <5448E5D0.6070701@suse.de> Date: Thu, 23 Oct 2014 13:26:08 +0200 From: Alexander Graf MIME-Version: 1.0 References: <5448D400.6010503@linaro.org> <5448E515.80300@suse.de> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] dynamic sysbus instantiation and load_dtb implementation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Eric Auger , Ard Biesheuvel , qemu list , Alex Williamson , Antonios Motakis , Paolo Bonzini , Christoffer Dall On 23.10.14 13:24, Peter Maydell wrote: > On 23 October 2014 12:23, Alexander Graf wrote: >> On 23.10.14 12:19, Ard Biesheuvel wrote: >>> The reason for this change was that, before, the DTB would only be >>> generated once, and after a reset, the machine would go through the >>> kernel boot protocol as before but the DTB pointer would point to >>> garbage. Any idea how ppc deals with this? Do they recreate the device >>> tree after each reset? >> >> Yes, we regenerate the device tree on each reset. > > Any particular reason? Surely it's always the same... We have the code in place anyway, it's not a performance critical code path and putting it into a rom would be a waste of RAM, as it'd keep yet another copy of something we can easily regenerate. It's a matter of personal preference I guess. Alex