search for: xenmem_set_memory_map

Displaying 6 results from an estimated 6 matches for "xenmem_set_memory_map".

2007 Jan 18
13
[PATCH 0/5] dump-core take 2:
The following dump-core patches changes its format into ELF, adds PFN-GMFN table, HVM support, and adds experimental IA64 support. - ELF format Program header and note section are adopted. - HVM domain support To know the memory area to dump, XENMEM_set_memory_map is added. XENMEM_memory_map hypercall is for current domain, so new one is created. and hvm domain builder tell xen its memory map. - IA64 support IA64 support is for only review. It doesn''t work because Xen/IA64 doesn''t support memory map hypercall. Subject: [PATCH 1/5]...
2006 Dec 12
1
[PATCH] Fix e820 mapping limit
The changeset ''12803:df5fa63490f4da7b65c56087a68783dbcb7944f8'' added a new hypercall XENMEM_set_memory_map for specifying the e820 mapping. There was a small bug in the userspace side of this change though - the e820 mapping was specified based on the ''memory_static_min'' domain info parameter which means the memory map size is clamped to the value ''memory'' config opti...
2012 Sep 04
2
[PATCH] valgrind: Support for ioctls used by Xen toolstack processes.
...lgrind.org/support/bug_reports.html &\n"); + VG_(dmsg)("http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen.\n"); + + SET_STATUS_Failure(VKI_ENOSYS); +} + +PRE(memory_op) +{ + PRINT("__HYPERVISOR_memory_op ( %ld, %lx )", ARG1, ARG2); + + switch (ARG1) { + case XENMEM_set_memory_map: { + xen_foreign_memory_map_t *arg = + (xen_foreign_memory_map_t *)(unsigned int)ARG2; + PRE_MEM_READ("XENMEM_set_memory_map", + (Addr)&arg->domid, sizeof(arg->domid)); + PRE_MEM_READ("XENMEM_set_memory_map", +...
2012 Oct 24
7
[PATCH 4/5] xen: arm: implement remap interfaces needed for privcmd mappings.
...T_HANDLE(xen_ulong_t) idxs; + + /* GPFN in domid where the source mapping page should appear. */ + GUEST_HANDLE(xen_pfn_t) gpfns; +}; +DEFINE_GUEST_HANDLE_STRUCT(xen_add_to_physmap_range); + /* * Returns the pseudo-physical memory map as it was when the domain * was started (specified by XENMEM_set_memory_map). -- 1.7.2.5
2013 Jul 23
73
Bug: Limitation of <=2GB RAM in domU persists with 4.3.0
I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB
2013 Dec 06
36
[V6 PATCH 0/7]: PVH dom0....
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