[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] _text vs _start


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Magnus Damm" <magnus.damm@xxxxxxxxx>
  • Date: Fri, 5 Jan 2007 12:09:49 +0900
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Hollis Blanchard <hollisb@xxxxxxxxxx>
  • Delivery-date: Thu, 04 Jan 2007 19:09:31 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FG87eOSkS7B5jzG+qsfGcLI7c+r6o2sdBCrQHIvIUTGVLTMqQmKzs0FKWvSmhNU31GaYTgNFG53U94M0TTWXk2xrLOFyIS20YReHw97tDnkZhiGxfvNAr6Lms20lE4f73MmNDDCDSamm+LzdT3ZZ3uuJNREma221STSwt/UKrus=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 1/4/07, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
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.

I was about to suggest to move the prototypes to a generic header file
while at it, but it seems like that someone already done that...
Thanks!

/ magnus

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.