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

[Xen-ia64-devel] Re: [PATCH] fix the ia64 p2m semantic

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Re: [PATCH] fix the ia64 p2m semantic
From: Doi.Tsunehisa@xxxxxxxxxxxxxx
Date: Mon, 26 Mar 2007 12:13:29 +0900
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 25 Mar 2007 20:12:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of Fri, 23 Mar 2007 11:38:34 +0900. <20070323023834.GG18975%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070323023834.GG18975%yamahata@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Isaku,

  Sorry for late response.

You (yamahata) said:
> Tsunehisa.
> I haven't tested arch_memory_op(). Could you verify it?

  I've checked this patch on the latest change set(cs:14513).

  It occured hypervisor crash at that xen-platform.ko was inserted.
And, hypervisor said as follow:

(XEN) BUG at mm.c:1050
(XEN) FIXME: implement ia64 dump_execution_state()
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) BUG at mm.c:1050
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

  The code shown by it is...

   1045
   1046 static void
   1047 adjust_page_count_info(struct page_info* page)
   1048 {
   1049     struct domain* d = page_get_owner(page);
   1050     BUG_ON(page->count_info != 1);    <<==== this point.
   1051     if (d != NULL) {
   1052         int ret = get_page(page, d);
   1053         BUG_ON(ret == 0);
   1054     } else {
   1055         u64 x, nx, y;
   1056
   1057         y = *((u64*)&page->count_info);
   1058         do {
   1059             x = y;
   1060             nx = x + 1;
   1061
   1062             BUG_ON((x >> 32) != 0);
   1063             BUG_ON((nx & PGC_count_mask) != 2);
   1064             y = cmpxchg((u64*)&page->count_info, x, nx);
   1065         } while (unlikely(y != x));
   1066     }
   1067 }

  I'll check, which hypercall occures hyper crash.

Thanks,
- Tsunehisa Doi

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