WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [Xen-devel] _text vs _start

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] _text vs _start
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Wed, 03 Jan 2007 15:45:39 -0600
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Magnus Damm <magnus.damm@xxxxxxxxx>, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 03 Jan 2007 13:45:32 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1C1D15A.6AC0%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <C1C1D15A.6AC0%Keir.Fraser@xxxxxxxxxxxx>
Reply-to: Hollis Blanchard <hollisb@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2007-01-03 at 21:32 +0000, Keir Fraser wrote:
> On 3/1/07 9:22 pm, "Hollis Blanchard" <hollisb@xxxxxxxxxx> wrote:
> 
> > On Wed, 2007-01-03 at 15:07 -0600, Hollis Blanchard wrote:
> >> Given that you do arithmetic with _end, can you explain why you're not
> >> using _start, which is a standard symbol provided by the default linker
> >> script?
> >
> > My mistake; _start of course isn't a linker script symbol at all, but
> > rather the entry point code.
> 
> There is an unnecessary disagreement among architectures over what symbols
> should be used to mark section and image boundaries. We could reasonably
> agree on at least _start/_end and _stext/_etext I think. This would allow
> functions like is_kernel_text() to become generic, and make it obvious which
> labels kexec should be using.

Sounds great to me.

PowerPC already arranges for _start to be at the very beginning
of .text, which is at the beginning of the first PT_LOAD segment... so
the end result is that the address of _start is the same as our link
address.

We also provide _etext, and _end, but not _stext (currently).

-- 
Hollis Blanchard
IBM Linux Technology Center


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] _text vs _start, Hollis Blanchard <=