search for: construct_dom0

Hi All, I am not very familiar with xen details. Now I am thinking of building two privilged domain(domain 0 not driver domain) at boot time. The other question is that wether it is possible to create another domain 0 by domain-builder running in domain0? Does it make sense when domain 0 is shut down unexpectedly another domain 0 can run at once. Maybe it is absurd. I am looking forwards

...+ + if ( (rc = p2m_alloc_table(d)) != 0 ) + goto fail; } d->max_vcpus = 8; diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c index 15632f7..6687e50 100644 --- a/xen/arch/arm/domain_build.c +++ b/xen/arch/arm/domain_build.c @@ -93,9 +93,6 @@ int construct_dom0(struct domain *d) d->max_pages = ~0U; - if ( (rc = p2m_alloc_table(d)) != 0 ) - return rc; - printk("Populate P2M %#llx->%#llx\n", kinfo.ram_start, kinfo.ram_end); p2m_populate_ram(d, kinfo.ram_start, kinfo.ram_end); diff --git a/xen/arch/arm/p2m.c b/x...

...ve described BIOS/ACPI behavior, and is expected to also deal with a boot time crash of pv-ops Linux upon encountering the same kind of system. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/domain_build.c +++ b/xen/arch/x86/domain_build.c @@ -1114,7 +1114,7 @@ int __init construct_dom0( for ( i = 0; i < nr_ioapics; i++ ) { mfn = paddr_to_pfn(mp_ioapics[i].mpc_apicaddr); - if ( smp_found_config ) + if ( !rangeset_contains_singleton(mmio_ro_ranges, mfn) ) rc |= iomem_deny_access(dom0, mfn, mfn); } --- a/xen/arch/x86/io_apic.c...

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??

..._emulate_memop: 1264 0xffff8300001adbaa vmx_world_save: 1040 0xffff8300001aeac5 vmx_world_save: 1040 0xffff830000106800 do_dom0_op: 968 0xffff8300001080cf do_dom0_op: 968 0xffff830000137c64 construct_dom0: 968 0xffff83000013a81e construct_dom0: 968 0xffff8300001b1dbc vmx_vmexit_handler: 632 0xffff8300001b2f58 vmx_vmexit_handler: 632 0xffff8300001313ff arch_do_dom0_op: 552 0xffff8300001327f3 arch_do_dom0_o...

...| 6 ++++++ xen/arch/arm/vgic.c | 4 +++- 3 files changed, 10 insertions(+), 2 deletions(-) diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c index 1e9776d..aa0f191 100644 --- a/xen/arch/arm/domain_build.c +++ b/xen/arch/arm/domain_build.c @@ -331,7 +331,7 @@ int construct_dom0(struct domain *d) WRITE_CP32(SCTLR_BASE, SCTLR); - WRITE_CP32(HCR_PTW|HCR_BSU_OUTER|HCR_AMO|HCR_IMO|HCR_VM, HCR); + WRITE_CP32(HCR_PTW|HCR_BSU_OUTER|HCR_AMO|HCR_IMO|HCR_VM|HCR_TWI, HCR); isb(); local_abort_enable(); diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c...

...- 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 implement changes in and around construct_dom0. Patch 7 adds option to boot a dom0 in PVH mode. The rest support tool stack on a pvh dom0. These patches are based on c/s: 4b07b3cbf29f66da6090d52e75b5fdae592c6441 These can also be found in public git tree at: git://oss.oracle.com/git/mrathor/xen.git branch: dom0pvh-v6 Thanks for all th...

..._domain_same_page(d, mpaddr, size, flags | ASSIGN_nocache); return mpaddr; } diff -r b58bcd6551e2 xen/arch/powerpc/domain_build.c --- a/xen/arch/powerpc/domain_build.c Fri Dec 01 16:21:46 2006 +0000 +++ b/xen/arch/powerpc/domain_build.c Fri Dec 01 16:22:41 2006 +0000 @@ -306,7 +306,7 @@ int construct_dom0(struct domain *d, rc = 0; /* DOM0 is permitted full I/O capabilities. */ - rc |= iomem_permit_access(dom0, 0UL, ~0UL); + rc |= iomem_permit_access(dom0, 0UL, ~0UL, IOMEM_ACCESS_READWRITE); rc |= irqs_permit_access(dom0, 0, NR_IRQS-1); BUG_ON(rc != 0); diff -r b58bcd655...

...ing tasks. Signed-off-by: Joseph Cihula <joseph.cihula@intel.com> diff -r a53aaea4c698 -r a85c4081738a xen/arch/ia64/xen/domain.c --- a/xen/arch/ia64/xen/domain.c Fri Sep 07 19:54:29 2007 +0100 +++ b/xen/arch/ia64/xen/domain.c Fri Sep 07 17:37:01 2007 -0700 @@ -1486,7 +1486,7 @@ int __init construct_dom0(struct domain return 0; } -void machine_restart(char * __unused) +void machine_restart(int __unused) { console_start_sync(); if (running_on_sim) diff -r a53aaea4c698 -r a85c4081738a xen/arch/powerpc/domain.c --- a/xen/arch/powerpc/domain.c Fri Sep 07 19:54:29 2007 +0100 +++ b/xen/arch/po...

...ndex: 2006-10-04/xen/arch/x86/domain_build.c =================================================================== --- 2006-10-04.orig/xen/arch/x86/domain_build.c 2006-10-04 15:10:46.000000000 +0200 +++ 2006-10-04/xen/arch/x86/domain_build.c 2006-10-04 15:11:03.000000000 +0200 @@ -325,6 +325,7 @@ int construct_dom0(struct domain *d, l1_pgentry_t gdt_l1e; set_bit(_DOMF_compat, &d->domain_flags); + v->vcpu_info = (void *)&d->shared_info->compat.vcpu_info[0]; if ( nr_pages != (unsigned int)nr_pages ) nr_pages = UINT_MAX; @@ -735,7 +736,7 @@ i...

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

...00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) Xen call trace: (XEN) [<0024d78c>] exynos5_specific_mapping+0x30/0xf4 (XEN) [<0026850c>] ??? (XEN) [<00243404>] construct_dom0+0x8d4/0xae4 (XEN) [<002690c0>] ??? (XEN) [<00200518>] puts+0x8/0x1c

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

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

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.

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I

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

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.