From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyI4Y-0005BL-U9 for qemu-devel@nongnu.org; Tue, 09 Dec 2014 05:31:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XyI4P-0003YH-8e for qemu-devel@nongnu.org; Tue, 09 Dec 2014 05:31:14 -0500 Received: from mail-wg0-f41.google.com ([74.125.82.41]:47568) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyI4P-0003Y3-3B for qemu-devel@nongnu.org; Tue, 09 Dec 2014 05:31:05 -0500 Received: by mail-wg0-f41.google.com with SMTP id y19so424264wgg.0 for ; Tue, 09 Dec 2014 02:31:04 -0800 (PST) Message-ID: <5486CF14.30501@linaro.org> Date: Tue, 09 Dec 2014 11:29:40 +0100 From: Eric Auger MIME-Version: 1.0 References: <1417371570-11789-1-git-send-email-eric.auger@linaro.org> <1417371570-11789-2-git-send-email-eric.auger@linaro.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v5 1/6] hw/arm/boot: load_dtb becomes non static arm_load_dtb List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Joel Schopp , Kim Phillips , eric.auger@st.com, Antonios Motakis , Alvise Rigo , manish.jaggi@caviumnetworks.com, Ard Biesheuvel , Will Deacon , QEMU Developers , Alexander Graf , Bharat Bhushan , Alex Williamson , Patch Tracking , Shannon Zhao , Stuart Yoder , Paolo Bonzini , "kvmarm@lists.cs.columbia.edu" , Christoffer Dall On 12/05/2014 07:16 PM, Peter Maydell wrote: > On 5 December 2014 at 16:38, Peter Maydell wrote: >> On 30 November 2014 at 18:19, Eric Auger wrote: >>> load_dtb is renamed into arm_load_dtb and becomes non static. >>> it will be used by machvirt for dynamic instantiation of >>> platform devices >> >> 'virt' shouldn't be a special case -- we should always >> handle setting up the DTB in guest memory in the same >> way, whether there happens to be a vfio platform device >> available or not. > > ...this probably means that a bunch of the work currently > done in arm_load_kernel() should be deferred to a 'machine > init complete' hook (perhaps all of it?). Hi Peter, OK I moved the arm_load_kernel code into a machine init done notify and arm_load_kernel now only registers the notifier. For machine files willing to support platform bus, the arm_load_kernel must happen before the registration of the notifier that adds platform bus nodes and after CPU init (notifiers are executed in registration reverse order). Best Regards Eric > > -- PMM >