From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Young Subject: Re: [PATCH 00/12] Fixing TI Keystone2 kexec Date: Wed, 11 May 2016 16:29:23 +0800 Message-ID: <20160511082923.GC8995@dhcp-128-65.nay.redhat.com> References: <20160428092644.GX19428@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20160428092644.GX19428@n2100.arm.linux.org.uk> Sender: linux-doc-owner@vger.kernel.org To: Russell King - ARM Linux Cc: linux-arm-kernel@lists.infradead.org, Mark Rutland , devicetree@vger.kernel.org, Tony Luck , linux-ia64@vger.kernel.org, linux-doc@vger.kernel.org, Pawel Moll , Jonathan Corbet , Ian Campbell , kexec@lists.infradead.org, Fenghua Yu , Haren Myneni , Rob Herring , Eric Biederman , Santosh Shilimkar , Kumar Gala , Vivek Goyal List-Id: devicetree@vger.kernel.org Hi, Russell On 04/28/16 at 10:26am, Russell King - ARM Linux wrote: > These changes are required for TI Keystone2 kexec to be functional. TI > Keystone2 has the run-time view of physical memory above 4GiB, but with > a boot time alias below 4GiB which can only be used during the early > boot. > > This means we need to translate run-time physical addresses (which the > kernel uses) to boot-time physical addresses, which, having discussed > with Eric, is what the kexec tools and kexec kernel API requires. > > We publish a special set of boot time resources in /proc/iomem, which > the (modified) kexec tools look for in preference to the normal resources. > Hence, if these are found, the kexec tools make use of these resources, > and thus kexec tools use the boot-time view of physical memory. I think getting memory ranges from device tree will be better than adding more stuff to /proc/iomem. Geoff's arm64 kexec patches is using dtb you can refer to the patchset. Thanks Dave