From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: xen/ia64 and elilo relocation Date: Wed, 16 Feb 2005 17:53:23 -0800 Message-ID: <4213F913.9020607@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net Cc: "Magenheimer, Dan (HP Labs Fort Collins)" , eranian@hpl.hp.com List-Id: xen-devel@lists.xenproject.org I noticed that elilo occassionally loads xen/ia64 at: 0x14000000 instead of the usual 0x4000000 (especially if you interrupt the loading process by pressing a key). This results in TR map setup from: fffc000014000000 (virtual) -> 0x4000000 (physical). Further, __alloc_bootmem() gives out fffc000004000000 as free memory and memsets it to 0. Now xen is going to insert a second TC from fffc000004000000 (virtual) -> 0x4000000 (physical) i.e. we have two virtual addresses mapping to the same physical address. The memset essentially corrupts xen's text. We have to figure out a way of telling elilo to always load xen at the same physical address. I thought the relocatable flag was off by default? -Arun ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click