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-devel

Re: [Xen-devel] Problems Building Xen 4.0.x on ia64 (various releases)

To: jortega@xxxxxxxxx
Subject: Re: [Xen-devel] Problems Building Xen 4.0.x on ia64 (various releases)
From: "KUWAMURA Shin'ya" <kuwa@xxxxxxxxxxxxxx>
Date: Mon, 20 Dec 2010 18:10:23 +0900 (JST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 20 Dec 2010 01:13:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101219100816.2455372jqa7en64g@xxxxxxxxxxxxxxxx> <1288882434.2472.22.camel@E4310>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101219100816.2455372jqa7en64g@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

>>>>> On Sun, 19 Dec 2010 10:08:16 -0430
>>>>> jortega@xxxxxxxxx("Julio C. Ortega")  said:
> 
> I've faced a couple of problems building Xen 4.0.0, 4.0.1 and 4.0.2rc1
> from sources on an itanium2 machine running debian 6.0
> I'll describe the problems i've faced with all three releases.
> 
> XEN 4.0.0:
> In file included from xc_dom_ia64.c:26:
> ia64/asm/dom_fw_common.h:47:23: error: asm/fpswa.h: No such file or
> directory

Could you try gcc-4.1 instead of gcc-4.4? Building xen with GCC 4.4
has a known problem and using GCC 4.1 can avoid it:
http://lists.xensource.com/archives/html/xen-ia64-devel/2010-05/msg00007.html

> XEN 4.0.1 & XEN 4.0.2rc1 (testing)
> /root/xen-4.0.1/xen/common/built_in.o: In function `kexec_exec':
> /root/xen-4.0.1/xen/common/kexec.c:493: undefined reference to
> `continue_hypercall_on_cpu'
> 4.0.2rc1:
> /root/xen-4.0.2rc1/xen/common/built_in.o: In function `kexec_exec':
> /root/xen-4.0.2rc1/xen/common/kexec.c:493: undefined reference to
> `continue_hypercall_on_cpu'
> make[3]: *** [/root/xen-4.0.2rc1/xen/xen-syms] Error 1
> Digging up and googling i've found out nothing, but seems weird that
> particularly continue_hypercall_on_cpu() it's only present in
> architecture specific include files.

You are right. Could you apply the attached patch?
# Notice that this fix is ad hoc.

Best regards,
-- 
  KUWAMURA Shin'ya
diff -r b536ebfba183 xen/common/kexec.c
--- a/xen/common/kexec.c        Wed Aug 25 09:22:42 2010 +0100
+++ b/xen/common/kexec.c        Mon Dec 20 14:44:33 2010 +0900
@@ -490,7 +490,12 @@ static int kexec_exec(XEN_GUEST_HANDLE(v
     {
     case KEXEC_TYPE_DEFAULT:
         image = &kexec_image[base + pos];
+#ifdef CONFIG_X86
         ret = continue_hypercall_on_cpu(0, kexec_reboot, image);
+#else
+        one_cpu_only();
+        machine_reboot_kexec(image); /* Does not return */
+#endif
         break;
     case KEXEC_TYPE_CRASH:
         kexec_crash(); /* Does not return */
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel