From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [patch] architecture-specific ELF header checking Date: Wed, 14 Jun 2006 09:39:38 +0200 Message-ID: <448FBD3A.1050701@suse.de> References: <1150143142.9179.36.camel@basalt.austin.ibm.com> <1150211844.31548.10.camel@basalt.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel , Hollis Blanchard , xen-ia64-devel List-Id: xen-devel@lists.xenproject.org > For libxc we probably need per-arch subdirectories for arch-specific > source files. There's all sorts of intermingled arch-specific code in > tools/libxc right now. We could then have arch-specific implementations > of xc_elf_check_header() or somesuch in tools/libxc/, like we do > for Xen's domain0 elf-parsing code. That would be cleaner and give more > per-arch flexibility. btw: for the elf parser it is probably useful to switch around using -Dsomething, so one can simply compile the elf loader twice. We'll need something like that in case we'll support both 32bit + 64bit guests in a 64bit hypervisor. With my domain builder rewrite it should be easy to do that ;) cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg