From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from out01.mta.xmission.com ([166.70.13.231]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1LUT2S-0002Px-PM for kexec@lists.infradead.org; Tue, 03 Feb 2009 21:42:50 +0000 References: <4C94DE2070B172459E4F1EE14BD2364E027534BA@HQ-EXCH-5.corp.brocade.com> <4C94DE2070B172459E4F1EE14BD2364E027DFC66@HQ-EXCH-5.corp.brocade.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: Tue, 03 Feb 2009 13:42:56 -0800 In-Reply-To: <4C94DE2070B172459E4F1EE14BD2364E027DFC66@HQ-EXCH-5.corp.brocade.com> (Ming Lei's message of "Tue\, 3 Feb 2009 12\:06\:02 -0800") Message-ID: MIME-Version: 1.0 Subject: Re: should kernel image destination address be picked up by kernel itself? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Ming Lei Cc: kexec@lists.infradead.org "Ming Lei" writes: > Hi Eric, > > I tried run latest kexec-tools v2.0 on ppc freescale 85xx platforms. > >>- All of the policy decisions are made in user space (such as where to >> execute from) > Is where to execute from the physical address or the virtual address? > How do we know it is available to kexec, it may be taken. It should be physical and there should be an API in linux like /proc/iomem which will report which addresses are memory. ppc is a little different than x86 so I'm not up to speed on how it reports things. I think it is with the device tree. >>- standalone executables are loaded into an address space where >> physical address and virtual address are the same. > There may be case that physical address and virtual address not the same > on linux, such as vmalloc. In the environment that kexec exports there should not be any. >>What problem do you see in that model? >>Why is it a problem for you? > > Can we put something like -1 to indicate to kernel that user space wants > kernel to choose the virtual address to load the standalone executable, > then linux kernel can kmalloc this area and then load the standalone > executable. You can do something like create a proper static ET_DYN executable and then /sbin/kexec will look for an address and load it there. Eric _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec