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

[Xen-devel] Why Xen use mkelf32 instead of lds?


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: 焦冶 <uframer@xxxxxxxxx>
  • Date: Thu, 17 Nov 2005 22:22:02 +0800
  • Delivery-date: Thu, 17 Nov 2005 14:22:10 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:in-reply-to:x-mimeole:message-id; b=KduwErfMwKEZXbYtKZHNjxfVgEI7ekl+mVSmUaRtUGd45fsZuhAVAkhBQxYupuVC/N5mgLAfoVIFdq8MR58mSXKLQomthsDQp5Qzd6mad7O5nyhWZu1lSR0TUy9ySYPpO7qnN3d8+XxQyMfO3p/RVt8m8rYZfo6hOeSY7XcOJRo=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcXrZM7gzYUq8xO2RUW2pZqLWgOEXAAHJeWQ

Hi,Guys!
  I read the xen source and find that xen.lds locates the xen binary image
at 0xFC500000, and then mkelf32(generated from mkelf32.c) to relocated it at
0x100000. And my question is WHY? Why doesn't xen.lds directly locate xen
image at 0x100000? Is there any reason?


_______________________________________________
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®.