search for: xen_

Don't use alloc_vm_area()/free_vm_area() directly, instead define xen_alloc_vm_area()/xen_free_vm_area() and use them. alloc_vm_area()/free_vm_area() are used to allocate/free area which are for grant table mapping. Xen/x86 grant table is based on virtual address so that alloc_vm_area()/free_vm_area() are suitable. On the other hand Xen/ia64 (and Xen/powerpc) grant t...

Don't use alloc_vm_area()/free_vm_area() directly, instead define xen_alloc_vm_area()/xen_free_vm_area() and use them. alloc_vm_area()/free_vm_area() are used to allocate/free area which are for grant table mapping. Xen/x86 grant table is based on virtual address so that alloc_vm_area()/free_vm_area() are suitable. On the other hand Xen/ia64 (and Xen/powerpc) grant t...

Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff --git a/xen/arch/x86/mm/paging.c b/xen/arch/x86/mm/paging.c --- a/xen/arch/x86/mm/paging.c +++ b/xen/arch/x86/mm/paging.c @@ -722,6 +722,10 @@ int paging_domctl(struct domain *d, xen_ /* Call when destroying a domain */ void paging_teardown(struct domain *d) { + /* Make sure log-dirty is turned off before trying to dismantle it. + * Needs to be done here becuse it''s covered by the hap/shadow lock */ + d->arch.paging.log_dirty.disable_log_dirty(d); +...

I last posted this back in April to critical acclaim (AKA near total silence). I''m not sure who looks after tools/include/xen-foreign. I had thought it was Jan but I think I was confused and was thinking of the semi-related xen/include/compat stuff. IOW I think nobody felt "responsible". Unless there''s any objection lets just treat this as coming under tools. The

When xen_emul_unplug=never is specified on kernel command line reading files from /sys/hypervisor is broken (returns -EBUSY). It is caused by xen_bus dependency on platform_pci and platform_pci isn''t initialized when xen_emul_unplug=never is specified. Fix it by allowing platform_pcii to ignore xen...

...ravirtentry.S | 99 ++++- arch/ia64/kernel/setup.c | 1 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/Makefile | 1 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 665 +++++++++++++++++++++++++++++++ 19 files changed, 2357 insertions(+), 25 deletions(-)

...ravirtentry.S | 99 ++++- arch/ia64/kernel/setup.c | 1 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/Makefile | 1 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 665 +++++++++++++++++++++++++++++++ 19 files changed, 2357 insertions(+), 25 deletions(-)

...514 ++++++++++++++++++++++++ arch/ia64/kernel/paravirtentry.S | 99 ++++- arch/ia64/kernel/setup.c | 2 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 665 +++++++++++++++++++++++++++++++ 17 files changed, 2353 insertions(+), 25 deletions(-)

...514 ++++++++++++++++++++++++ arch/ia64/kernel/paravirtentry.S | 99 ++++- arch/ia64/kernel/setup.c | 2 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 665 +++++++++++++++++++++++++++++++ 17 files changed, 2353 insertions(+), 25 deletions(-)

...514 ++++++++++++++++++++++++ arch/ia64/kernel/paravirtentry.S | 99 ++++- arch/ia64/kernel/setup.c | 2 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 665 +++++++++++++++++++++++++++++++ 17 files changed, 2353 insertions(+), 25 deletions(-)

...514 ++++++++++++++++++++++++ arch/ia64/kernel/paravirtentry.S | 99 ++++- arch/ia64/kernel/setup.c | 2 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 665 +++++++++++++++++++++++++++++++ 17 files changed, 2353 insertions(+), 25 deletions(-)

...509 +++++++++++++++++++++++ arch/ia64/kernel/paravirtentry.S | 101 ++++- arch/ia64/kernel/setup.c | 1 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 667 +++++++++++++++++++++++++++++++ 17 files changed, 2351 insertions(+), 25 deletions(-)

...509 +++++++++++++++++++++++ arch/ia64/kernel/paravirtentry.S | 101 ++++- arch/ia64/kernel/setup.c | 1 + arch/ia64/kernel/vmlinux.lds.S | 24 ++ arch/ia64/kvm/vtlb.c | 2 + arch/ia64/xen/hypercall.S | 2 + arch/ia64/xen/xen_pv_ops.c | 667 +++++++++++++++++++++++++++++++ 17 files changed, 2351 insertions(+), 25 deletions(-)

This patch uses the standard generic header for the definition of machine_emergency_restart() and reverses the call path for XenoLinux. Signed-off-by: Jimi Xenidis <jimix@watson.ibm.com> --- diff -r 7680b29c03a6 drivers/xen/core/reboot.c --- a/drivers/xen/core/reboot.c Sat Aug 05 11:33:24 2006 -0400 +++ b/drivers/xen/core/reboot.c Mon Aug 07 09:50:33 2006 -0400 @@ -9,6 +9,7 @@ #include

Hello, I find a strange behavior. When a machine is slow (or with many debug traces or a qemu vm), a interrupt can occur between the pv_irq_ops initialization and the xen_vcpu[0] initialization. This lead to a problem because some operations in xen_irq_ops use xen_vcpu. I send you a patch to fix that but I''m not quite sure that is the right solution. Regards, Anthoine From ac683ad8264f83fa0a5d743e18c0422e43e871d2 Mon Sep 17 00:00:00 2001 From: Anthoine Bou...

...sk_of(cpu)); /* capability check */ if (perf->state_count <= 1) { --- 2011-09-20.orig/xen/drivers/acpi/pmstat.c 2011-09-21 16:37:46.000000000 +0200 +++ 2011-09-20/xen/drivers/acpi/pmstat.c 2011-10-14 14:53:51.000000000 +0200 @@ -211,11 +211,11 @@ static int get_cpufreq_para(struct xen_s list_for_each(pos, &cpufreq_governor_list) gov_num++; - if ( (op->u.get_para.cpu_num != cpus_weight(policy->cpus)) || + if ( (op->u.get_para.cpu_num != cpumask_weight(policy->cpus)) || (op->u.get_para.freq_num != pmpt->perf.state_count) ||...

...physinfo.nr_nodes); + return physinfo.nr_cpus; } diff -r 51045f276c90 xen/arch/ia64/xen/dom0_ops.c --- a/xen/arch/ia64/xen/dom0_ops.c Mon Jul 31 10:48:48 2006 -0500 +++ b/xen/arch/ia64/xen/dom0_ops.c Mon Jul 31 10:49:10 2006 -0500 @@ -203,6 +203,7 @@ long arch_do_dom0_op(dom0_op_t *op, XEN_ cpus_weight(cpu_core_map[0]) / pi->threads_per_core; pi->sockets_per_node = num_online_cpus() / cpus_weight(cpu_core_map[0]); + pi->nr_cpus = (u32)num_online_cpus(); pi->nr_nodes = 1; pi->total_pages =...

Has anyone had any luck with this new release yet? I tried but simple got a restart upon the module being inserted in the install process. I''m still messing around with 8178 in an attempt to make something happen. I was getting some xen_* function symbols not found on an earlier one, but now Im working through compile problems.. Was just wondering if anyone thought this newer version would have better hope. I didn''t notice any xen specifics in the Changelog, so I''m not feeling to optimistic. -- View this message i...

>>>Has anyone had any luck with this new release yet? I tried but simple >>>got a restart upon the module being inserted in the install process. >>>I''m still messing around with 8178 in an attempt to make something >>>happen. I was getting some xen_* function symbols not found on an >>>earlier one, but now Im working through compile problems.. Any luck on resolving the compilation issues with 8178? I''ve tried both 8756 and 8762, both cause a lockup at boottime right after they''re installed. --Brian ____________...

...009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ Still, I cannot boot my dom0 properly. If I choose to boot xen with kernel 2.6.31 it first hangs, saying that my sata link is down, and all it can get is 1.5gigabit. And then I get a call trace with a lot of error in xen_.... elements. If, on the other hand I boot dom0 with kernel 2.6.18 it simply panics, being unable to mount my / on md0. My fs is ext3, but all the kernel tries is ext2 and iso9660. What am I doing wrong? Thanks for all help, mjb _______________________________________________ Xen-users mailing...