On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote:
--- a/tools/libxc/xc_hvm_build_x86.c
+++ b/tools/libxc/xc_hvm_build_x86.c
@@ -407,7 +407,7 @@ static int setup_guest(xc_interface *xch,
new_memflags |= XENMEMF_exact_node_request;
}
-end_pages =
On Tue, Feb 17, 2015 at 02:26:23PM +, Dario Faggioli wrote:
On Thu, 2015-02-12 at 19:44 +, Wei Liu wrote:
--- a/tools/libxc/xc_hvm_build_x86.c
+++ b/tools/libxc/xc_hvm_build_x86.c
@@ -407,7 +407,7 @@ static int setup_guest(xc_interface *xch,
new_memflags |=
Wei Liu writes ([PATCH v5 17/24] libxl: build, check and pass vNUMA info to
Xen for HVM guest):
Transform user supplied vNUMA configuration into libxl internal
representations then libxc representations. Check validity along the
line.
This is going to be a totally stupid question: but why are
On Fri, Feb 13, 2015 at 02:21:27PM +, Ian Jackson wrote:
Wei Liu writes ([PATCH v5 17/24] libxl: build, check and pass vNUMA info to
Xen for HVM guest):
Transform user supplied vNUMA configuration into libxl internal
representations then libxc representations. Check validity along the
Transform user supplied vNUMA configuration into libxl internal
representations then libxc representations. Check validity along the
line.
Libxc has more involvement in building vmemranges in HVM case compared
to PV case. The building of vmemranges is placed after xc_hvm_build
returns, because it
