Re: [Xen-devel] Xen 4.0.2 first release candidate

["KUWAMURA Shin'ya" <kuwa@xxxxxxxxxxxxxx>]

Hi Keir,

Could you backport xen-unstable 22092:e0ec7b10f8ce and apply the
attached patch? They are required in order to build 4.0.2-rc1 on ia64.

Notice: the attached patch is required only on xen-4.0-testing.
This issue was introduced by xen-4.0-testing 21300:8bdf09baff30
(xen-unstable 21886:578ed14c3c67),
 which required xen-unstable 21166:07befd9cf6d3.

Best regards,
-- 
  KUWAMURA Shin'ya

# HG changeset patch
# User KUWAMURA Shin'ya <kuwa@xxxxxxxxxxxxxx>
# Date 1294782537 18000
# Node ID e2ea327517357193807e9a4961523108b35145ba
# Parent  d53dbb988624a658370462523d8b7f5aec11da2d
kexec: fix ia64 build for 21300:8bdf09baff30

On ia64, 21300:8bdf09baff30 introduces the following error:
  xen/common/kexec.c:490: undefined reference to `continue_hypercall_on_cpu'

The function continue_hypercall_on_cpu() is defined only on x86.

Signed-off-by: KUWAMURA Shin'ya <kuwa@xxxxxxxxxxxxxx>

diff -r d53dbb988624 -r e2ea32751735 xen/common/kexec.c
--- a/xen/common/kexec.c        Thu Sep 02 13:36:23 2010 +0100
+++ b/xen/common/kexec.c        Tue Jan 11 16:48:57 2011 -0500
@@ -487,7 +487,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