search for: alloc_vcpu

Hi all, I am having confusion regarding the way a newly created domain is allocated vcpu. Initially during dom0 creation alloc_vcpu is called to create vcpu structs for all the available cpu''s and assigned to dom0. But its not the case for domU creation. 1. So how will dom0 relinquish/share vcpu to/with a newly created domU. Does this happen as part of the shared_info page mapping?? 2. Till the end of DOMCTL_createdoma...

...ume) + restore_vcpu_affinity(d); domain_unpause(d); + } rcu_read_unlock(&domlist_read_lock); } diff --git a/xen/common/domain.c b/xen/common/domain.c index 64ee29d..590548e 100644 --- a/xen/common/domain.c +++ b/xen/common/domain.c @@ -126,6 +126,7 @@ struct vcpu *alloc_vcpu( if ( !zalloc_cpumask_var(&v->cpu_affinity) || !zalloc_cpumask_var(&v->cpu_affinity_tmp) || + !zalloc_cpumask_var(&v->cpu_affinity_saved) || !zalloc_cpumask_var(&v->vcpu_dirty_cpumask) ) goto fail_free; @@ -155,6 +156,7 @@ st...

...nilla Linux (2.6.16) comes up on this box in UP mode since it finds the local APIC disabled in bios. However, the xen based kernel tries to come up MP and fails in a non-intuitive way by hitting a BUG in the hypervisor code. Following is the stack trace of the xen based kernel: [<ff10f8d6>] alloc_vcpu+0x36/0x120 [<ff1518c0>] smp_prepare_cpus+0x460/0xd30 [<ff132fcd>] intel_p6_mcheck_init+0xbd/0xe0 [<ff1555b4>] get_mtrr_state+0xf4/0x110 [<ff1508f1>] __start_xen+0x5d1/0x9e0 [<ff123270>] new_tlbflush_clock_period+0x0/0x90 [<ff10015a>] start_paging+0x52...

...d) (xenheap_phys_end-__pa(heap_start)) >> 20, (xenheap_phys_end-__pa(heap_start)) >> 10); + late_setup_arch(&cmdline); + scheduler_init(); idle_vcpu[0] = (struct vcpu*) ia64_r13; idle_domain = domain_create(IDLE_DOMAIN_ID); if ( (idle_domain == NULL) || (alloc_vcpu(idle_domain, 0, 0) == NULL) ) BUG(); - late_setup_arch(&cmdline); alloc_dom_xen_and_dom_io(); setup_per_cpu_areas(); mem_init(); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-de...

...t_acpi_sleep); static u8 sleep_states[ACPI_S_STATE_COUNT]; --- 2009-08-18.orig/xen/arch/x86/domain_build.c 2009-08-21 17:38:51.000000000 +0200 +++ 2009-08-18/xen/arch/x86/domain_build.c 2009-08-24 17:40:18.000000000 +0200 @@ -101,10 +101,10 @@ struct vcpu *__init alloc_dom0_vcpu0(voi return alloc_vcpu(dom0, 0, 0); } -static unsigned int opt_dom0_shadow; +static unsigned int __initdata opt_dom0_shadow; boolean_param("dom0_shadow", opt_dom0_shadow); -static char opt_dom0_ioports_disable[200] = ""; +static char __initdata opt_dom0_ioports_disable[200] = ""; stri...

...0 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) Xen call trace: (XEN) [<ffff8300001180f4>] __bug+0x24/0x30 (XEN) [<ffff830000106f15>] alloc_vcpu+0x45/0x130 (XEN) [<ffff830000107369>] alloc_idle_vcpu+0x59/0x80 (XEN) [<ffff830000169f49>] smp_prepare_cpus+0x4a9/0xd10 (XEN) [<ffff830000168f0c>] __start_xen+0x75c/0xac0 (XEN) [<ffff8300001001c1>] __high_start+0x94/0x96 (XEN) (XEN) ******************************...

...es: * mode: C Index: 2006-10-04/xen/common/domain.c =================================================================== --- 2006-10-04.orig/xen/common/domain.c 2006-10-04 08:49:30.000000000 +0200 +++ 2006-10-04/xen/common/domain.c 2006-10-04 15:14:26.000000000 +0200 @@ -82,7 +82,7 @@ struct vcpu *alloc_vcpu( v->domain = d; v->vcpu_id = vcpu_id; - v->vcpu_info = &d->shared_info->vcpu_info[vcpu_id]; + v->vcpu_info = shared_info_addr(d, vcpu_info[vcpu_id]); spin_lock_init(&v->pause_lock); v->runstate.state = is_idle_vcpu(v) ? RUNSTATE_running...

Hi all, this small patch series implement guest SMP support for ARM, using the ARM PSCI interface for secondary cpu bringup. Stefano Stabellini (4): xen/arm: basic PSCI support, implement cpu_on xen/arm: support for guest SGI xen/arm: support vcpu_op hypercalls xen: move VCPUOP_register_vcpu_info to common code xen/arch/arm/domain.c | 66 ++++++++++++++++++++++++

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

This series of patches makes Xen pass a (somewhat) valid device tree to dom0. The device tree for dom0 is the same as the one supplied to Xen except the memory and chosen nodes are adjusted appropriately. We don''t yet make use of the device tree to map MMIO regions or setup interrupts for the guest and we still include the UART used for Xen''s console. Note that loading Linux

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the

Hi, V6: The only change from V5 is in patch #6: - changed comment to reflect autoxlate - removed a redundant ASSERT - reworked logic a bit so that get_page_from_gfn() is called with NULL for p2m type as before. arm has ASSERT wanting it to be NULL. Tim: patch 4 needs your approval. Daniel: patch 5 needs your approval. These patches implement PVH dom0. Patches 1 and 2

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See