On Fri, Feb 13, 2015 at 03:49:44PM +, Andrew Cooper wrote:
[...]
+
+int libxl__vnuma_build_vmemrange_pv_generic(libxl__gc *gc,
+uint32_t domid,
+libxl_domain_build_info
*b_info,
+
On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote:
--- a/tools/libxl/libxl_x86.c
+++ b/tools/libxl/libxl_x86.c
@@ -339,6 +339,79 @@ int libxl__arch_domain_finalise_hw_description(libxl__gc
*gc,
return 0;
}
+/* Return 0 on success, ERROR_* on failure. */
+int
On 12/02/15 19:44, Wei Liu wrote:
Introduce a arch-independent routine to generate one vmemrange per
vnode. Also introduce arch-dependent routines for different
architectures because part of the process is arch-specific -- ARM has
yet have NUMA support and E820 is x86 only.
For those x86
Introduce a arch-independent routine to generate one vmemrange per
vnode. Also introduce arch-dependent routines for different
architectures because part of the process is arch-specific -- ARM has
yet have NUMA support and E820 is x86 only.
For those x86 guests who care about machine E820 map