search for: hypercall_memory_op

...anged. Only the free memory will be affected. In normal linux, the value of MemTotal comes from "totalram_pages" defined in arch/i386/mm/init.c I tried to located the code in Xen, which changes the variable, but I didn''t find such code. I tried to locate the implementation of HYPERCALL_memory_op, but I can only traced to "call hypercall_page + STR(...)" Can someone tell me where I can find the actual implementation of those hypercalls? Thanks in advance! weiming _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists....

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

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of