search for: domheap

And can we make p2m memory allocation from domain heap directly? -Xin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

We''ve run into an issue with an 8 node x3950 where xm info is showing only 6 nodes. I''ve traced the problem to the clip_to_limit function in arch/x86/e820.c. #ifdef __x86_64__ clip_to_limit((uint64_t)(MACH2PHYS_COMPAT_VIRT_END - __HYPERVISOR_COMPAT_VIRT_START) << 10, "Only the first %u GB of the physical memory map

Hello Han, I am pleased you approve of the design and implementation of the XI shadow mechanism. And I appreciate the time and care you''ve taken in reviewing this substantial body of new code. You asked about performance statistics. With the current XI patch, we are seeing the following: - page faults times for XI are about 4 times faster than non-XI: 10.56 (non-XI) vs 2.43

At last year''s Xen North America Summit in Boston, I gave a talk about memory overcommitment in Xen. I showed that the basic mechanisms for moving memory between domains were already present in Xen and that, with a few scripts, it was possible to roughly load-balance memory between domains. During this effort, I discovered that "ballooning" had a lot of weaknesses, even though

...om frame number instead of doing shift directly. - Remove some unnecessary initialization code and add "static" to vmentry_fields and gpdptr_fields. - Enable the VMREAD/VMWRITE bitmap only if nested hvm is enabled. - Use clear_page() to set all 0 to the page instead of memset(). - Use domheap to allocate the VMREAD/VMWRITE bitmap instead of xenheap. Changes from v1 to v2: - Use domain_page_map_to_mfn() instead of virt_to_mfn() to get the machine frame. - Address other comments from Jan, including some programming format, return value type, etc. Latest Intel SDM introduced a new feat...

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not

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

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