From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH 5/8] arm: remove the hack for loading vmlinux images Date: Wed, 14 Mar 2012 10:51:42 +0000 Message-ID: <4F60783E.4070401@citrix.com> References: <1330448064-32267-1-git-send-email-david.vrabel@citrix.com> <1330448064-32267-6-git-send-email-david.vrabel@citrix.com> <1331720231.23971.370.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1331720231.23971.370.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 14/03/12 10:17, Ian Campbell wrote: > On Tue, 2012-02-28 at 16:54 +0000, David Vrabel wrote: >> From: David Vrabel >> >> Don't adjust the RAM location/size when loading an ELF for dom0. It >> was vmlinux specific and no longer needed because Linux can be loaded >> from a zImage. > > I'm a bit confused, aren't kernel_try_zimage_prepare and > kernel_try_elf_prepare two different methods for loading the kernel? If > the adjustment is needed for vmlinux how does the fact that you could > load via zImage allow you to remove that adjustment in the vmlinux case? > > Could we consider removing support for loading an ELF file entirely? I left the ELF support in case we need to load some other (non-vmlinux) ELF image. David