RE: [Xen-ia64-devel] Re: [PATCH] ia64 build fixes

["Benson, Ronald A" <ronald.a.benson@xxxxxxxxx>]

Any ideas on this failure when I try to boot Xen/ia64 on an Itanium 2
Processor system, the following message is repeated:

"unknown hypercall 17c6"

The number 17c6 sometimes changes and sometimes doesn't. 


Ronald A. Benson
 
 

-----Original Message-----
From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Alex
Williamson
Sent: Saturday, April 01, 2006 1:47 PM
To: Keir Fraser
Cc: xen-devel; xen-ia64-devel
Subject: [Xen-ia64-devel] Re: [PATCH] ia64 build fixes

On Sat, 2006-04-01 at 11:10 +0100, Keir Fraser wrote:
> Taken, thanks. Can you also look at supporting HYPERVISOR_sched_op() 
> before 3.0.2, in addition to the old HYPERVISOR_sched_op_compat()?

Keir,

   Here's a patch that enables HYPERVISOR_sched_op() and
HYPERVISOR_sched_opt_compat() for ia64.  We currently have no users of
this call, but there's no harm in enabling it (tested by adding a
HYPERVISOR_yield() call to default_idle()).  I did notice a problem with
the compat interface though, nothing defines __XEN_INTERFACE_VERSION__
for the build of xen.  We're therefore stuck on interface version
0x00000000 where __HYPERVISOR_sched_op_compat == __HYPERVISOR_sched_op.
Thanks,

        Alex

Signed-off-by: Alex Williamson <alex.williamson@xxxxxx>
---

diff -r 60071beccf18 xen/arch/ia64/xen/hypercall.c
--- a/xen/arch/ia64/xen/hypercall.c     Sat Apr  1 14:59:12 2006 +0100
+++ b/xen/arch/ia64/xen/hypercall.c     Sat Apr  1 14:35:19 2006 -0700
@@ -38,7 +38,7 @@ hypercall_t ia64_hypercall_table[] =
        (hypercall_t)do_ni_hypercall,           /* do_stack_switch */
        (hypercall_t)do_ni_hypercall,           /* do_set_callbacks */
        (hypercall_t)do_ni_hypercall,           /* do_fpu_taskswitch */
/*  5 */
-       (hypercall_t)do_ni_hypercall,           /* do_sched_op_compat */
+       (hypercall_t)do_sched_op_compat,
        (hypercall_t)do_dom0_op,
        (hypercall_t)do_ni_hypercall,           /* do_set_debugreg */
        (hypercall_t)do_ni_hypercall,           /* do_get_debugreg */
@@ -61,7 +61,7 @@ hypercall_t ia64_hypercall_table[] =
        (hypercall_t)do_ni_hypercall,           /* do_mmuext_op */
        (hypercall_t)do_ni_hypercall,           /* do_acm_op */
        (hypercall_t)do_ni_hypercall,           /* do_nmi_op */
-       (hypercall_t)do_ni_hypercall,           /*  */
+       (hypercall_t)do_sched_op,
        (hypercall_t)do_ni_hypercall,           /*  */
/* 30 */
        (hypercall_t)do_ni_hypercall            /*  */
        };
@@ -70,6 +70,11 @@ xen_hypercall (struct pt_regs *regs)
 xen_hypercall (struct pt_regs *regs)
 {
        switch (regs->r2) {
+           case __HYPERVISOR_sched_op_compat:
+               regs->r8 = do_sched_op_compat((int) regs->r14,
+                                             (unsigned long)
regs->r15);
+               break;
+
            case __HYPERVISOR_dom0_op:
                regs->r8 = do_dom0_op(guest_handle_from_ptr(regs->r14,
                                                            dom0_op_t));
@@ -116,6 +121,13 @@ xen_hypercall (struct pt_regs *regs)
            case __HYPERVISOR_multicall:
                regs->r8 = do_multicall(guest_handle_from_ptr(regs->r14,
multicall_entry_t), (unsigned int) regs->r15);
                break;
+
+#if __XEN_INTERFACE_VERSION__ >= 0x00030101
+           case __HYPERVISOR_sched_op:
+               regs->r8 = do_sched_op((int) regs->r14,
+                                      guest_handle_from_ptr(regs->r15,
void));
+               break;
+#endif
 
            default:
                printf("unknown xen hypercall %lx\n", regs->r2);



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

--- Begin Message ---

• To: "Dong, Eddie" <eddie.dong@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
• From: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
• Date: Mon, 27 Feb 2006 21:32:16 -0700
• Thread-index: AcY7cu5GMk+yV8ITSb+XZVkCa1+MogArK+ZQ
• Thread-topic: [Xen-ia64-devel] CONFIG_DOMAIN0_CONTIGUOUS in domain.c

Hi Eddie,

         When disable this compile option CONFIG_DOMAIN0_CONTIGUOUS with the 
latest CSet# 9000,  Xen hangs  during its boot process ,but when enable this 
option , It has nothing wrong .

 the serial output is as below : 

(XEN) About to call timer_init()

(XEN) About to call sort_main_extable()

(XEN) About to call domain_create()

(XEN) ###allocating rid_range, domain f000000007ff8900: starting_rid=40000, 
ending_rid=80000

(XEN) arch_domain_create: domain=f000000007ff8900

(XEN) About to call construct_dom0()

(XEN) *** LOADING DOMAIN 0 ***

(XEN) METAPHYSICAL MEMORY ARRANGEMENT:

(XEN)  Kernel image:  4000000->4dd00d0

(XEN)  Entry address: 400ff20

(XEN)  Init. ramdisk: 1fac0000 len 13e853

(XEN)  Start info.:   1fc00000->1fc04000

(XEN) assign_new_domain_page: Can't alloc!!!! Aaaargh!

(XEN) BUG at xen/domain.c:661

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

(XEN) unknown hypercall 1270

Thanks 
     Xiantao
CSD-OTC PRC Virtualization
Intel (China) Limited

________________________________

From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dong, Eddie
Sent: 2006年2月27日 15:54
To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-ia64-devel] CONFIG_DOMAIN0_CONTIGUOUS in domain.c

 

All:

    I am not sure if somebody has tested the path with 
CONFIG_DOMAIN0_CONTIGUOUS in xen/arch/ia64/xen/domain.c disabled, as this is a 
must for p2m/vp coming patches, please echo if yes? If no, then it is an urgent 
task now to either remove the code or disable the configuration by default.

 

Thanks,eddie

 

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

--- End Message ---

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