search for: xen_create_contiguous_region

Hi Folks, I need some large chunk of physical memory, so I allocate it early using alloc_bootmem_low_pages and use it later (akin to bigphysarea patch). The trouble I am having is the following. Suppose the virtual address for the memory area is 0xc14d6000. After xen_create_contiguous_region call, I do a virt_to_bus and the bus address comes out to be 0x18000000. So far so good. However, later when I try to use this memory in a device driver, the call to virt_to_bus returns 0x14d6000. This result is baffling me, since that''s what it would look like in a normal 32-bit i386...

Hi all, I am using Xen 2.0.7. I have Broadcom NetXtreme BCM5704 Gigabit Ethernet (rev 02) cards which support frames greater than 1500. However when I boot into Xen and try to set the MTU to anything higher than 1500 (e.g., 4000, 8000 etc) I get a segmentation fault. After this fault, every command fails with a segmentation fault. I saw a similar bug report posted here:

...R_CODE; - move pfn_to_mfn and mfn_to_pfn to page.h as static inline functions; - no need to walk the two p2m trees if phys_to_mach.rb_node is NULL; - correctly handle multipage p2m entries; - substitute the p2m spin_lock with a rwlock; - assume dom0 is mapped 1:1, no need to call XENMEM_exchange in xen_create_contiguous_region; - add two simple performance improvements for swiotlb-xen. Changes in v7: - dma_mark_clean: switch to an empty implementation (we are going to use the platform map_page and unmap_page to ensure coherency); - dma_capable: use coherent_dma_mask if dma_mask hasn''t been allocated; - intr...

...being reserved when the system starts and only the populated ones getting the reserved status cleared in __free_pages_bootmem(), the condition to put pages into the balloon in balloon_init() is inverted. Also, dying in xen_destroy_contiguous_region() (and similarly in the failure recovery code in xen_create_contiguous_region()) if the space just unmapped can''t be re-populated seems overly harsh (we''re having a case where this actually happens); wouldn''t it make sense to make this fatal only when the page can''t be replaced by a free one (allocated inside the domain, with the page stol...

...: yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pni monitor ds_cpl cid xtpr bogomips : 5976.88 Problem: kernel BUG at arch/xen/i386/mm/hypervisor.c:354 (xen_create _contiguous_region)! Ä<c011847b>Ü xen_create_contiguous_region+0x2eb/0x360 Ä<c026761e>Ü net_rx_action+0x13e/0x220 Ä<c01072d9>Ü skbuff_ctor+0x69/0x70 Ä<c014d965>Ü cache_init_objs+0x55/0x90 Ä<c014db8c>Ü cache_grow+0x13c/0x240 Ä<c014deb6>Ü cache_alloc_refill+0x226/0x260 Ä<c014e14c>Ü kmem_cache_alloc+0x9c/0xb0 Ä<c02601...

..._DISABLED Paul Gortmaker (1): xen: delete new instances of added __cpuinit Stefano Stabellini (23): arm: make SWIOTLB available arm64: define DMA_ERROR_CODE arm/xen,arm64/xen: introduce p2m xen/x86: allow __set_phys_to_machine for autotranslate guests xen: make xen_create_contiguous_region return the dma address xen/arm,arm64: enable SWIOTLB_XEN swiotlb-xen: introduce xen_swiotlb_set_dma_mask arm/xen: get_dma_ops: return xen_dma_ops if we are running as xen_initial_domain arm64/xen: get_dma_ops: return xen_dma_ops if we are running as xen_initial_domain...

Hi all, this little series removes the last swiotlb API exposed to modules. Diffstat: arch/x86/include/asm/xen/swiotlb-xen.h | 6 ------ arch/x86/kernel/pci-dma.c | 28 ++++------------------------ drivers/gpu/drm/nouveau/nouveau_ttm.c | 10 +++------- drivers/pci/xen-pcifront.c | 6 ------ kernel/dma/swiotlb.c | 1 - 5 files changed, 7

Hello, I''ve hit known problem with dynamic memory management - memory fragmentation... This dynamic memory management basically does xl mem-set to balance memory. After some time of running system, xen memory is so fragmented that it is impossible to start new VM with PCI device. Sometimes it crashes during boot (no 64MB contiguous memory for SWIOTLB), or later - eg. iwlagn cannot

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine

This series implements ballooning for Xen on ARM and builds and Mukesh''s PVH privcmd stuff to implement foreign page mapping on ARM, replacing the old "HACK: initial (very hacky) XENMAPSPACE_gmfn_foreign" patch. The baseline is a bit complex, it is basically Stefano''s xenarm-forlinus branch (commit bbd6eb29214e) merged with Konrad''s linux-next-pvh branch

2011/7/19 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > CC''ing Tim and xen-devel > > On Mon, 18 Jul 2011, Jiageng Yu wrote: >> 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: >> > On Fri, 15 Jul 2011, Jiageng Yu wrote: >> >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: >> >> > 2011/7/15

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it