[Xen-ia64-devel] code in vms_fault.c

2007-08-31 Thread Tristan Gingold
Hi, in vms_fault.c:leave_hypervisor_tail(): if (v->vcpu_id == 0) { unsigned long callback_irq = d->arch.hvm_domain.params[HVM_PARAM_CALLBACK_IRQ]; if ( v->arch.arch_vmx.pal_init_pending ) { /*inject INIT interruption to guest pal*/

[Xen-ia64-devel] Re: [Xen-devel] [PATCH 1/3] continuable destroy domain: common part

2007-08-31 Thread Isaku Yamahata
Sorry, I sent out the old one. Here is the correct patch. The difference is the following hunk. @@ -434,11 +434,7 @@ long do_domctl(XEN_GUEST_HANDLE(xen_domc ret = -EINVAL; if ( d != current->domain ) -{ -domain_kill(d); -ret

[Xen-ia64-devel] [PATCH 1/3] continuable destroy domain: common part

2007-08-31 Thread Isaku Yamahata
# HG changeset patch # User [EMAIL PROTECTED] # Date 1188566555 -32400 # Node ID 1ab773a3182bb785a3e0ec53fa4ab5bd6bfd5fa9 # Parent 96f64f4c42f043e3af2db369f4b9bdb9fcef017b XEN_DOMCTL_destroydomain hypercall frees domain resources, especially it frees all pages of the domain. When domain memory is

[Xen-ia64-devel] [PATCH 2/3] continuable destroy domain: x86 part

2007-08-31 Thread Isaku Yamahata
# HG changeset patch # User [EMAIL PROTECTED] # Date 1188557397 -32400 # Node ID 357ef76c2f1aa35523bad4c5825292c70bcc3381 # Parent 1ab773a3182bb785a3e0ec53fa4ab5bd6bfd5fa9 Implement x86 continuable domain destroy. This patch addresses the following bug report. http://bugzilla.xensource.com/bugzill

[Xen-ia64-devel] [PATCH 3/3] continuable destroy domain: ia64 part

2007-08-31 Thread Isaku Yamahata
# HG changeset patch # User [EMAIL PROTECTED] # Date 1188280280 -32400 # Node ID b4fe65fdc26d5b56057f3711e7d8bf4a3617cfa8 # Parent b8f3785f15bde5da96b4ffd1cde3e677d54abf90 Implement ia64 continuable domain detroy. PATCHNAME: implement_ia64_continuable_domain_destroy Signed-off-by: Isaku Yamahata

[Xen-ia64-devel] [PATCH 0/3] continuable destroy domain: Make XEN_DOMCTL_destroydomain hypercall continuable

2007-08-31 Thread Isaku Yamahata
Make XEN_DOMCTL_destroydomain hypercall continuable. XEN_DOMCTL_destroydomain hypercall frees domain resources, especially it frees all pages of the domain. When domain memory is very large, it takes too long resulting in soft lockup warning message or something worse. See http://bugzilla.xensourc

[Xen-ia64-devel] [IA64] Weekly benchmark results [ww35]

2007-08-31 Thread KUWAMURA Shin'ya
Hi, I report a benchmark result of this week on IPF using ia64/xen-unstable and ia64/linux-2.6.18-xen. - PV-on-HVM drivers cannot be compiled for RHEL4U2 RHEL4U2's kernel (2.6.9-22.EL) does not have the macro DEFINE_RWLOCK, so compiling machine_reboot.c failed. - LTP FAIL In LTP, test cases rela