From: Hollis Blanchard Subject: Re: ELF headers Date: Tue, 28 Mar 2006 13:47:40 -0600 Message-ID: <200603281347.41896.hollisb@us.ibm.com> References: <20060322063040.960068000@sorel.sous-sol.org> <200603281100.57586.hollisb@us.ibm.com> <3d8eece20603281020s3691322bi9b11deb902db1a87@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3d8eece20603281020s3691322bi9b11deb902db1a87@mail.gmail.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christian.Limpach@cl.cam.ac.uk Cc: Gerd Hoffmann , xen-devel@lists.xensource.com, xen-ppc-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tuesday 28 March 2006 12:20, Christian Limpach wrote: > On 3/28/06, Hollis Blanchard wrote: > > On Tuesday 28 March 2006 02:49, Gerd Hoffmann wrote: > > > + * bug comparibility alert: old linux kernels used to have > > > + * virtual addresses in the paddr headers, whereas newer ones > > > + * (since kexec merge, around 2.6.14) correctly use physical > > > + * addresses. > > > > I can't speak for IA64, but PPC kernels still have virtual addresses in the > > paddr fields. Accordingly, I would reword it like this: > > Some Linux kernels have virtual addresses in the paddr headers, and some > > correctly use physical addresses. > > How is that correct? The ELF spec is quite vague on what is supposed > to be in the paddr fields... It seems to me that 0xc000000000000000 is not supposed to be in a field that contains a "physical address". Is that in question? -- Hollis Blanchard IBM Linux Technology Center