]> xenbits.xensource.com Git - people/liuw/libxenctrl-split/xen.git/commitdiff
xl: fix vNUMA vdistance parsing
authorWei Liu <wei.liu2@citrix.com>
Mon, 17 Aug 2015 18:56:59 +0000 (19:56 +0100)
committerIan Campbell <ian.campbell@citrix.com>
Fri, 21 Aug 2015 07:45:55 +0000 (08:45 +0100)
We should parse the output from splitting function, not the original
string, otherwise the parsed result is wrong.

For example:

vnuma = [ [...,"vdistance=10,20",...],
          [...,"vdistance=20,10",...] ]

Before this change, vdistance from node 0 to all nodes (including
itself) was 10 and vdistance from node 1 to all nodes was 20.

After this change, vdistance from node 0 to itself is 10, to node 1 is
20 and vdistance from node 1 to node 0 is 20, to itself is 10. That's
the correct vdistance settings we expect.

Signed-off-by: Wei Liu <wei.liu2@citrix.com>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
tools/libxl/xl_cmdimpl.c

index c6b0b6827627bb16304595ebb573074de09e0381..44fff823096aabd98ab24b60cb156a7fd82f5fb9 100644 (file)
@@ -1188,7 +1188,7 @@ static void parse_vnuma_config(const XLU_Config *config,
                     len = libxl_string_list_length(&vdist);
 
                     for (j = 0; j < len; j++) {
-                        val = parse_ulong(value);
+                        val = parse_ulong(vdist[j]);
                         p->distances[j] = val;
                     }
                     libxl_string_list_dispose(&vdist);