Allow setting NUMA distance for different NUMA nodes
PATCH v6 1/1 Allow setting NUMA distance for different NUMA nodes
This patch is going to add SLIT table support in QEMU, and provides additional option dist for command -numa to allow user set vNUMA distance by QEMU command.
With this patch, when a user wants to create a guest that contains several vNUMA nodes and also wants to set distance among those nodes, the QEMU command would like:
``` -numa node,nodeid=0,cpus=0 \ -numa node,nodeid=1,cpus=1 \ -numa node,nodeid=2,cpus=2 \ -numa node,nodeid=3,cpus=3 \ -numa dist,src=0,dst=1,val=21 \ -numa dist,src=0,dst=2,val=31 \ -numa dist,src=0,dst=3,val=41 \ -numa dist,src=1,dst=2,val=21 \ -numa dist,src=1,dst=3,val=31 \ -numa dist,src=2,dst=3,val=21 \ ```
--- hw/acpi/aml-build.c | 25 +++++++++++ hw/i386/acpi-build.c | 4 ++ include/hw/acpi/aml-build.h | 1 + include/sysemu/numa.h | 2 + include/sysemu/sysemu.h | 4 ++ numa.c | 100 ++++++++++++++++++++++++++++++++++++++++++++ qapi-schema.json | 30 ++++++++++++- qemu-options.hx | 16 ++++++- 8 files changed, 179 insertions(+), 3 deletions(-)
hw/acpi/aml-build.c +25 -0
@@ -24,6 +24,7 @@#include "hw/acpi/aml-build.h" #include "qemu/bswap.h" #include "qemu/bitops.h" +#include "sysemu/numa.h" static GArray *build_alloc_array (void ) {
@@ -1609,3 +1610,27 @@ void build_srat_memory(AcpiSratMemoryAffinity *numamem, uint64_t base, numamem->base_addr =cpu_to_le64 (base); numamem->range_length =cpu_to_le64 (len); } + +/* +* ACPI spec 5.2.17 System Locality Distance Information Table +* (Revision 2.0 or later) +*/ +void build_slit (GArray *table_data,BIOSLinker *linker) +{ +int slit_start, i, j; + slit_start = table_data->len; + +acpi_data_push (table_data,sizeof (AcpiTableHeader)); + +build_append_int_noprefix (table_data, nb_numa_nodes,8 ); +for (i =0 ; i < nb_numa_nodes; i++) { +for (j =0 ; j < nb_numa_nodes; j++) { +build_append_int_noprefix (table_data, numa_info[i].distance[j],1 ); + } + } + +build_header (linker, table_data, + (void *)(table_data->data + slit_start), +"SLIT" , + table_data->len - slit_start,1 ,NULL ,NULL ); +}
hw/i386/acpi-build.c +4 -0
@@ -2678,6 +2678,10 @@ void acpi_build(AcpiBuildTables *tables, MachineState *machine)if (pcms->numa_nodes) {acpi_add_table (table_offsets, tables_blob);build_srat (tables_blob, tables->linker, machine); +if (have_numa_distance) { +acpi_add_table (table_offsets, tables_blob); +build_slit (tables_blob, tables->linker); + } }if (acpi_get_mcfg (&mcfg)) {acpi_add_table (table_offsets, tables_blob);
include/hw/acpi/aml-build.h +1 -0
@@ -389,4 +389,5 @@ GCC_FMT_ATTR(2, 3);void build_srat_memory (AcpiSratMemoryAffinity *numamem,uint64_t base,uint64_t len,int node,MemoryAffinityFlags flags); +void build_slit (GArray *table_data,BIOSLinker *linker);#endif
include/sysemu/numa.h +2 -0
@@ -8,6 +8,7 @@#include "hw/boards.h" extern int nb_numa_nodes;/* Number of NUMA nodes */ +extern bool have_numa_distance;struct numa_addr_range {ram_addr_t mem_start;
@@ -21,6 +22,7 @@ typedef struct node_info {struct HostMemoryBackend *node_memdev;bool present; QLIST_HEAD(, numa_addr_range) addr; /* List to store address ranges */ +uint8_t distance[MAX_NODES ]; } NodeInfo;extern NodeInfo numa_info[MAX_NODES ];
include/sysemu/sysemu.h +4 -0
@@ -169,6 +169,10 @@ extern int mem_prealloc;#define MAX_NODES 128#define NUMA_NODE_UNASSIGNED MAX_NODES +#define NUMA_DISTANCE_MIN 10 +#define NUMA_DISTANCE_DEFAULT 20 +#define NUMA_DISTANCE_MAX 254 +#define NUMA_DISTANCE_UNREACHABLE 255#define MAX_OPTION_ROMS 16 typedef struct QEMUOptionRom {
numa.c +100 -0
130 lines not on this page · raw message
qapi-schema.json +28 -2
@@ -5673,10 +5673,14 @@ ## # @NumaOptionsType: # +# @node: NUMA nodes configuration +# +# @dist: NUMA distance configuration (since 2.10) +# # Since: 2.1 ## { 'enum': 'NumaOptionsType', - 'data': [ 'node' ] } + 'data': [ 'node', 'dist' ] } ## # @NumaOptions:
@@ -5689,7 +5693,8 @@ 'base': { 'type': 'NumaOptionsType' }, 'discriminator': 'type', 'data': { - 'node': 'NumaNodeOptions' }} + 'node': 'NumaNodeOptions', + 'dist': 'NumaDistOptions' }} ## # @NumaNodeOptions:
@@ -5718,6 +5723,27 @@ '*memdev': 'str' }} ## +# @NumaDistOptions: +# +# Set the distance between 2 NUMA nodes. +# +# @src: source NUMA node. +# +# @dst: destination NUMA node. +# +# @val: NUMA distance from source node to destination node. +# When a node is unreachable from another node, set the distance +# between them to 255. +# +# Since: 2.10 +## +{ 'struct': 'NumaDistOptions', + 'data': { + 'src': 'uint16', + 'dst': 'uint16', + 'val': 'uint8' }} + +## # @HostMemPolicy: # # Host memory policy types
qemu-options.hx +15 -1
@@ -139,12 +139,15 @@ ETEXI DEF("numa", HAS_ARG, QEMU_OPTION_numa, "-numa node[,mem=size][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n" - "-numa node[,memdev=id][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n", QEMU_ARCH_ALL) + "-numa node[,memdev=id][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n" + "-numa dist,src=source,dst=destination,val=distance\n", QEMU_ARCH_ALL) STEXI @item -numa node[,mem=@var{size}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}] @itemx -numa node[,memdev=@var{id}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}] +@itemx -numa dist,src=@var{source},dst=@var{destination},val=@var{distance} @findex -numa Define a NUMA node and assign RAM and VCPUs to it. +Set the NUMA distance from a source node to a destination node. @var{firstcpu} and @var{lastcpu} are CPU indexes. Each @samp{cpus} option represent a contiguous range of CPU indexes
@@ -167,6 +170,17 @@ split equally between them. @samp{mem} and @samp{memdev} are mutually exclusive. Furthermore, if one node uses @samp{memdev}, all of them have to use it. +@var{source} and @var{destination} are NUMA node IDs. +@var{distance} is the NUMA distance from @var{source} to @var{destination}. +The distance from a node to itself is always 10. If any pair of nodes is +given a distance, then all pairs must be given distances. Although, when +distances are only given in one direction for each pair of nodes, then +the distances in the opposite directions are assumed to be the same. If, +however, an asymmetrical pair of distances is given for even one node +pair, then all node pairs must be provided distance values for both +directions, even when they are symmetrical. When a node is unreachable +from another node, set the pair's distance to 255. + Note that the -@option{numa} option doesn't allocate any of the specified resources, it just assigns existing resources to NUMA nodes. This means that one still has to use the @option{-m},
Signature · 1 line
2.7.4
Quoted 154 lines · He Chen
This patch is going to add SLIT table support in QEMU, and provides additional option
distfor command-numato allow user set vNUMA distance by QEMU command.With this patch, when a user wants to create a guest that contains several vNUMA nodes and also wants to set distance among those nodes, the QEMU command would like:
```
(quoted diff) +0
-10-numa node,nodeid=0,cpus=0 \ -numa node,nodeid=1,cpus=1 \ -numa node,nodeid=2,cpus=2 \ -numa node,nodeid=3,cpus=3 \ -numa dist,src=0,dst=1,val=21 \ -numa dist,src=0,dst=2,val=31 \ -numa dist,src=0,dst=3,val=41 \ -numa dist,src=1,dst=2,val=21 \ -numa dist,src=1,dst=3,val=31 \ -numa dist,src=2,dst=3,val=21 \```
Signed-off-by He Chen <[email protected]>--- hw/acpi/aml-build.c | 25 +++++++++++ hw/i386/acpi-build.c | 4 ++ include/hw/acpi/aml-build.h | 1 + include/sysemu/numa.h | 2 + include/sysemu/sysemu.h | 4 ++ numa.c | 100 ++++++++++++++++++++++++++++++++++++++++++++ qapi-schema.json | 30 ++++++++++++- qemu-options.hx | 16 ++++++- 8 files changed, 179 insertions(+), 3 deletions(-)hw/acpi/aml-build.c +25
-0@@ -24,6 +24,7 @@#include "hw/acpi/aml-build.h" #include "qemu/bswap.h" #include "qemu/bitops.h" +#include "sysemu/numa.h" static GArray *build_alloc_array (void ) {@@ -1609,3 +1610,27 @@ void build_srat_memory(AcpiSratMemoryAffinity *numamem, uint64_t base, numamem->base_addr =cpu_to_le64 (base); numamem->range_length =cpu_to_le64 (len); } + +/* +* ACPI spec 5.2.17 System Locality Distance Information Table +* (Revision 2.0 or later) +*/ +void build_slit (GArray *table_data,BIOSLinker *linker) +{ +int slit_start, i, j; + slit_start = table_data->len; + +acpi_data_push (table_data,sizeof (AcpiTableHeader)); + +build_append_int_noprefix (table_data, nb_numa_nodes,8 ); +for (i =0 ; i < nb_numa_nodes; i++) { +for (j =0 ; j < nb_numa_nodes; j++) { +build_append_int_noprefix (table_data, numa_info[i].distance[j],1 ); + } + } + +build_header (linker, table_data, + (void *)(table_data->data + slit_start), +"SLIT" , + table_data->len - slit_start,1 ,NULL ,NULL ); +}hw/i386/acpi-build.c +4
-0@@ -2678,6 +2678,10 @@ void acpi_build(AcpiBuildTables *tables, MachineState *machine)if (pcms->numa_nodes) {acpi_add_table (table_offsets, tables_blob);build_srat (tables_blob, tables->linker, machine); +if (have_numa_distance) { +acpi_add_table (table_offsets, tables_blob); +build_slit (tables_blob, tables->linker); + } }if (acpi_get_mcfg (&mcfg)) {acpi_add_table (table_offsets, tables_blob);include/hw/acpi/aml-build.h +1
-0@@ -389,4 +389,5 @@ GCC_FMT_ATTR(2, 3);void build_srat_memory (AcpiSratMemoryAffinity *numamem,uint64_t base,uint64_t len,int node,MemoryAffinityFlags flags); +void build_slit (GArray *table_data,BIOSLinker *linker);#endif include/sysemu/numa.h +2
-0@@ -8,6 +8,7 @@#include "hw/boards.h" extern int nb_numa_nodes;/* Number of NUMA nodes */ +extern bool have_numa_distance;struct numa_addr_range {ram_addr_t mem_start;@@ -21,6 +22,7 @@ typedef struct node_info {struct HostMemoryBackend *node_memdev;bool present; QLIST_HEAD(, numa_addr_range) addr; /* List to store address ranges */ +uint8_t distance[MAX_NODES ]; } NodeInfo;extern NodeInfo numa_info[MAX_NODES ];include/sysemu/sysemu.h +4
-0@@ -169,6 +169,10 @@ extern int mem_prealloc;#define MAX_NODES 128#define NUMA_NODE_UNASSIGNED MAX_NODES +#define NUMA_DISTANCE_MIN 10 +#define NUMA_DISTANCE_DEFAULT 20 +#define NUMA_DISTANCE_MAX 254 +#define NUMA_DISTANCE_UNREACHABLE 255#define MAX_OPTION_ROMS 16 typedef struct QEMUOptionRom {numa.c +6
-0@@ -51,6 +51,7 @@ static int max_numa_nodeid; /* Highest specified NUMA node ID, plus one.* For all nodes, nodeid < max_numa_nodeid */ int nb_numa_nodes; +bool have_numa_distance;NodeInfo numa_info[MAX_NODES ];void numa_set_mem_node_id (ram_addr_t addr,uint64_t size,uint32_t node)@@ -212,6 +213,41 @@ static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) max_numa_nodeid =MAX (max_numa_nodeid, nodenr +1 ); } +static void numa_distance_parse (NumaDistOptions *dist,QemuOpts *opts,Error **errp) +{ +uint16_t src = dist->src; +uint16_t dst = dist->dst; +uint8_t val = dist->val;
numa.c static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) · line 230
Quoted 10 lines
numa.c +10
-0+ +if (!numa_info[src].present || !numa_info[dst].present) { +error_setg (errp,"Source/Destination NUMA node is missing. " +"Please use '-numa node' option to declare it first." ); +return ; + } + +if (src >=MAX_NODES || dst >=MAX_NODES ) { +error_setg (errp,"Max number of NUMA nodes reached: %" + PRIu16"" ,MAX_NODES );
^ shouldn't need that empty string
Quoted 209 lines
numa.c +84
-0+return ; + } + +if (val <NUMA_DISTANCE_MIN ) { +error_setg (errp,"NUMA distance (%" PRIu8") is invalid, " +"it should be larger than %d." , + val,NUMA_DISTANCE_MIN ); +return ; + } + +if (src == dst && val !=NUMA_DISTANCE_MIN ) { +error_setg (errp,"Local distance of node %d should be %d." , + src,NUMA_DISTANCE_MIN ); +return ; + } + + numa_info[src].distance[dst] = val; + have_numa_distance = true; +} +static int parse_numa (void *opaque,QemuOpts *opts,Error **errp) {NumaOptions *object =NULL ;@@ -235,6 +271,12 @@ static int parse_numa(void *opaque, QemuOpts *opts, Error **errp) } nb_numa_nodes++;break ; +case NUMA_OPTIONS_TYPE_DIST : +numa_distance_parse (&object->u.dist, opts, &err); +if (err) { + goto end; + } +break ;default :abort (); }@@ -294,6 +336,63 @@ static void validate_numa_cpus(void)g_free (seen_cpus); } +static void validate_numa_distance (void ) +{ +int src, dst, s, d; +bool is_asymmetrical = false; +bool opposite_missing = false; + +if (!have_numa_distance) { +return ; + } + +for (src =0 ; src < nb_numa_nodes; src++) { +for (dst = src; dst < nb_numa_nodes; dst++) { + s = src; + d = dst; + +if (numa_info[s].present && numa_info[d].present) { +if (numa_info[s].distance[d] ==0 && + numa_info[d].distance[s] ==0 ) { +if (s == d) { + numa_info[s].distance[d] =NUMA_DISTANCE_MIN ; + }else { +error_report ("The distance between node %d and %d is missing, " +"please provide all unique node pair distances." , + s, d); +exit (EXIT_FAILURE ); + } + } + +if (numa_info[s].distance[d] ==0 ) { + s = dst; + d = src; + } + +if (numa_info[d].distance[s] ==0 ) { + opposite_missing = true; + } + +if ((numa_info[d].distance[s] !=0 ) && + (numa_info[s].distance[d] != numa_info[d].distance[s])) { + is_asymmetrical = true; + } + +if (is_asymmetrical) { +if (opposite_missing) { +error_report ("At least one asymmetrical pair of distances " +"is given, please provide distances for both " +"directions of all node pairs." ); +exit (EXIT_FAILURE ); + } + }else { + numa_info[d].distance[s] = numa_info[s].distance[d]; + } + } + } + } +} +void parse_numa_opts (MachineClass *mc) {int i;@@ -390,6 +489,7 @@ void parse_numa_opts(MachineClass *mc) }validate_numa_cpus (); +validate_numa_distance (); }else {numa_set_mem_node_id (0 , ram_size,0 ); }qapi-schema.json +28
-2@@ -5673,10 +5673,14 @@ ## # @NumaOptionsType: # +# @node: NUMA nodes configuration +# +# @dist: NUMA distance configuration (since 2.10) +# # Since: 2.1 ## { 'enum': 'NumaOptionsType', - 'data': [ 'node' ] } + 'data': [ 'node', 'dist' ] } ## # @NumaOptions:@@ -5689,7 +5693,8 @@ 'base': { 'type': 'NumaOptionsType' }, 'discriminator': 'type', 'data': { - 'node': 'NumaNodeOptions' }} + 'node': 'NumaNodeOptions', + 'dist': 'NumaDistOptions' }} ## # @NumaNodeOptions:@@ -5718,6 +5723,27 @@ '*memdev': 'str' }} ## +# @NumaDistOptions: +# +# Set the distance between 2 NUMA nodes. +# +# @src: source NUMA node. +# +# @dst: destination NUMA node. +# +# @val: NUMA distance from source node to destination node. +# When a node is unreachable from another node, set the distance +# between them to 255. +# +# Since: 2.10 +## +{ 'struct': 'NumaDistOptions', + 'data': { + 'src': 'uint16', + 'dst': 'uint16', + 'val': 'uint8' }} + +## # @HostMemPolicy: # # Host memory policy typesqemu-options.hx +15
-1@@ -139,12 +139,15 @@ ETEXI DEF("numa", HAS_ARG, QEMU_OPTION_numa, "-numa node[,mem=size][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n" - "-numa node[,memdev=id][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n", QEMU_ARCH_ALL) + "-numa node[,memdev=id][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n" + "-numa dist,src=source,dst=destination,val=distance\n", QEMU_ARCH_ALL) STEXI @item -numa node[,mem=@var{size}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}] @itemx -numa node[,memdev=@var{id}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}] +@itemx -numa dist,src=@var{source},dst=@var{destination},val=@var{distance} @findex -numa Define a NUMA node and assign RAM and VCPUs to it. +Set the NUMA distance from a source node to a destination node. @var{firstcpu} and @var{lastcpu} are CPU indexes. Each @samp{cpus} option represent a contiguous range of CPU indexes@@ -167,6 +170,17 @@ split equally between them. @samp{mem} and @samp{memdev} are mutually exclusive. Furthermore, if one node uses @samp{memdev}, all of them have to use it. +@var{source} and @var{destination} are NUMA node IDs. +@var{distance} is the NUMA distance from @var{source} to @var{destination}. +The distance from a node to itself is always 10. If any pair of nodes is +given a distance, then all pairs must be given distances. Although, when +distances are only given in one direction for each pair of nodes, then +the distances in the opposite directions are assumed to be the same. If, +however, an asymmetrical pair of distances is given for even one node +pair, then all node pairs must be provided distance values for both +directions, even when they are symmetrical. When a node is unreachable +from another node, set the pair's distance to 255. + Note that the -@option{numa} option doesn't allocate any of the specified resources, it just assigns existing resources to NUMA nodes. This means that one still has to use the @option{-m},Signature · 1 line
2.7.4
Besides the "", looks good to me
Quoted 21 lines · He Chen
This patch is going to add SLIT table support in QEMU, and provides additional option
distfor command-numato allow user set vNUMA distance by QEMU command.With this patch, when a user wants to create a guest that contains several vNUMA nodes and also wants to set distance among those nodes, the QEMU command would like:
```
(quoted diff) +0
-10-numa node,nodeid=0,cpus=0 \ -numa node,nodeid=1,cpus=1 \ -numa node,nodeid=2,cpus=2 \ -numa node,nodeid=3,cpus=3 \ -numa dist,src=0,dst=1,val=21 \ -numa dist,src=0,dst=2,val=31 \ -numa dist,src=0,dst=3,val=41 \ -numa dist,src=1,dst=2,val=21 \ -numa dist,src=1,dst=3,val=31 \ -numa dist,src=2,dst=3,val=21 \```
Quoted 2 lines
Signed-off-by He Chen <[email protected]>---
Here is where you should mention what changed since v5, to help focus the attention of reviewers that have read earlier versions.
Quoted 4 lines
+++
b/qapi-schema.json##
qapi-schema.json +1
-0+# @NumaDistOptions:
qapi-schema.json line 5736
Quoted 10 lines
qapi-schema.json +10
-0+# +# Set the distance between 2 NUMA nodes. +# +# @src: source NUMA node. +# +# @dst: destination NUMA node. +# +# @val: NUMA distance from source node to destination node. +# When a node is unreachable from another node, set the distance +# between them to 255.
Still no mention that distances less than 10 are invalid, or that a node to itself defaults to 10 and can't be changed, or that other distances default to 20. But that starts to get complex enough, and you cover it elsewhere, so I'm okay with what you have here.
Interface looks sane, but I'll leave others to do the code review.
Signature · 3 lines
Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
Quoted 22 lines · Eric Blake
Quoted 21 lines · He Chen
This patch is going to add SLIT table support in QEMU, and provides additional option
distfor command-numato allow user set vNUMA distance by QEMU command.With this patch, when a user wants to create a guest that contains several vNUMA nodes and also wants to set distance among those nodes, the QEMU command would like:
```
(quoted diff) +0
-10-numa node,nodeid=0,cpus=0 \ -numa node,nodeid=1,cpus=1 \ -numa node,nodeid=2,cpus=2 \ -numa node,nodeid=3,cpus=3 \ -numa dist,src=0,dst=1,val=21 \ -numa dist,src=0,dst=2,val=31 \ -numa dist,src=0,dst=3,val=41 \ -numa dist,src=1,dst=2,val=21 \ -numa dist,src=1,dst=3,val=31 \ -numa dist,src=2,dst=3,val=21 \```
Quoted 6 lines
Quoted 2 lines
Signed-off-by He Chen <[email protected]>---
Here is where you should mention what changed since v5, to help focus the attention of reviewers that have read earlier versions.
Oh, sorry.
Changes since v5:
* Made the generation of the SLIT dependent on have_numa_distance.
* Doc refinement.
Quoted 20 lines
Quoted 4 lines
+++
b/qapi-schema.json##
qapi-schema.json +1
-0+# @NumaDistOptions:qapi-schema.json line 5736
Quoted 10 lines
qapi-schema.json +10
-0+# +# Set the distance between 2 NUMA nodes. +# +# @src: source NUMA node. +# +# @dst: destination NUMA node. +# +# @val: NUMA distance from source node to destination node. +# When a node is unreachable from another node, set the distance +# between them to 255.Still no mention that distances less than 10 are invalid, or that a node to itself defaults to 10 and can't be changed, or that other distances default to 20. But that starts to get complex enough, and you cover it elsewhere, so I'm okay with what you have here.
Quoted 2 lines
Interface looks sane, but I'll leave others to do the code review.
Is there anything I need to do to improve this patch? Still need another version patch or just wait for the code review?
Thanks,
-He
Quoted 146 lines · On Tue, 11 Apr 2017 16:49:26 +0800 He Chen <[email protected]> wrote:
This patch is going to add SLIT table support in QEMU, and provides additional option
distfor command-numato allow user set vNUMA distance by QEMU command.With this patch, when a user wants to create a guest that contains several vNUMA nodes and also wants to set distance among those nodes, the QEMU command would like:
```
(quoted diff) +0
-10-numa node,nodeid=0,cpus=0 \ -numa node,nodeid=1,cpus=1 \ -numa node,nodeid=2,cpus=2 \ -numa node,nodeid=3,cpus=3 \ -numa dist,src=0,dst=1,val=21 \ -numa dist,src=0,dst=2,val=31 \ -numa dist,src=0,dst=3,val=41 \ -numa dist,src=1,dst=2,val=21 \ -numa dist,src=1,dst=3,val=31 \ -numa dist,src=2,dst=3,val=21 \```
Signed-off-by He Chen <[email protected]>--- hw/acpi/aml-build.c | 25 +++++++++++ hw/i386/acpi-build.c | 4 ++ include/hw/acpi/aml-build.h | 1 + include/sysemu/numa.h | 2 + include/sysemu/sysemu.h | 4 ++ numa.c | 100 ++++++++++++++++++++++++++++++++++++++++++++ qapi-schema.json | 30 ++++++++++++- qemu-options.hx | 16 ++++++- 8 files changed, 179 insertions(+), 3 deletions(-)hw/acpi/aml-build.c +25
-0@@ -24,6 +24,7 @@#include "hw/acpi/aml-build.h" #include "qemu/bswap.h" #include "qemu/bitops.h" +#include "sysemu/numa.h" static GArray *build_alloc_array (void ) {@@ -1609,3 +1610,27 @@ void build_srat_memory(AcpiSratMemoryAffinity *numamem, uint64_t base, numamem->base_addr =cpu_to_le64 (base); numamem->range_length =cpu_to_le64 (len); } + +/* +* ACPI spec 5.2.17 System Locality Distance Information Table +* (Revision 2.0 or later) +*/ +void build_slit (GArray *table_data,BIOSLinker *linker) +{ +int slit_start, i, j; + slit_start = table_data->len; + +acpi_data_push (table_data,sizeof (AcpiTableHeader)); + +build_append_int_noprefix (table_data, nb_numa_nodes,8 ); +for (i =0 ; i < nb_numa_nodes; i++) { +for (j =0 ; j < nb_numa_nodes; j++) { +build_append_int_noprefix (table_data, numa_info[i].distance[j],1 ); + } + } + +build_header (linker, table_data, + (void *)(table_data->data + slit_start), +"SLIT" , + table_data->len - slit_start,1 ,NULL ,NULL ); +}hw/i386/acpi-build.c +4
-0@@ -2678,6 +2678,10 @@ void acpi_build(AcpiBuildTables *tables, MachineState *machine)if (pcms->numa_nodes) {acpi_add_table (table_offsets, tables_blob);build_srat (tables_blob, tables->linker, machine); +if (have_numa_distance) { +acpi_add_table (table_offsets, tables_blob); +build_slit (tables_blob, tables->linker); + } }if (acpi_get_mcfg (&mcfg)) {acpi_add_table (table_offsets, tables_blob);include/hw/acpi/aml-build.h +1
-0@@ -389,4 +389,5 @@ GCC_FMT_ATTR(2, 3);void build_srat_memory (AcpiSratMemoryAffinity *numamem,uint64_t base,uint64_t len,int node,MemoryAffinityFlags flags); +void build_slit (GArray *table_data,BIOSLinker *linker);#endif include/sysemu/numa.h +2
-0@@ -8,6 +8,7 @@#include "hw/boards.h" extern int nb_numa_nodes;/* Number of NUMA nodes */ +extern bool have_numa_distance;struct numa_addr_range {ram_addr_t mem_start;@@ -21,6 +22,7 @@ typedef struct node_info {struct HostMemoryBackend *node_memdev;bool present; QLIST_HEAD(, numa_addr_range) addr; /* List to store address ranges */ +uint8_t distance[MAX_NODES ]; } NodeInfo;extern NodeInfo numa_info[MAX_NODES ];include/sysemu/sysemu.h +4
-0@@ -169,6 +169,10 @@ extern int mem_prealloc;#define MAX_NODES 128#define NUMA_NODE_UNASSIGNED MAX_NODES +#define NUMA_DISTANCE_MIN 10 +#define NUMA_DISTANCE_DEFAULT 20 +#define NUMA_DISTANCE_MAX 254 +#define NUMA_DISTANCE_UNREACHABLE 255#define MAX_OPTION_ROMS 16 typedef struct QEMUOptionRom {numa.c +1
-0@@ -51,6 +51,7 @@ static int max_numa_nodeid; /* Highest specified NUMA node ID, plus one.* For all nodes, nodeid < max_numa_nodeid */ int nb_numa_nodes; +bool have_numa_distance;NodeInfo numa_info[MAX_NODES ];void numa_set_mem_node_id (ram_addr_t addr,uint64_t size,uint32_t node)
numa.c static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) · line 222
Quoted 10 lines
numa.c +7
-0@@ -212,6 +213,41 @@ static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) max_numa_nodeid =MAX (max_numa_nodeid, nodenr +1 ); } +static void numa_distance_parse (NumaDistOptions *dist,QemuOpts *opts,Error **errp) +{ +uint16_t src = dist->src; +uint16_t dst = dist->dst; +uint8_t val = dist->val; + +if (!numa_info[src].present || !numa_info[dst].present) {
possible out of bounds read since src/dst here could be > MAX_NODES here, move this block after "if (src >= MAX_NODES || dst >= MAX_NODES) {"
numa.c static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) · line 230
Quoted 8 lines
numa.c +8
-0+error_setg (errp,"Source/Destination NUMA node is missing. " +"Please use '-numa node' option to declare it first." ); +return ; + } + +if (src >=MAX_NODES || dst >=MAX_NODES ) { +error_setg (errp,"Max number of NUMA nodes reached: %" + PRIu16"" ,MAX_NODES );
message implies that max number of nodes has been allocated, which is not what check verifies.
how about:
"Invalid node %" PRIu16 ", max possible could be %d"
Quoted 24 lines
numa.c +20
-0+return ; + } + +if (val <NUMA_DISTANCE_MIN ) { +error_setg (errp,"NUMA distance (%" PRIu8") is invalid, " +"it should be larger than %d." , + val,NUMA_DISTANCE_MIN ); +return ; + } + +if (src == dst && val !=NUMA_DISTANCE_MIN ) { +error_setg (errp,"Local distance of node %d should be %d." , + src,NUMA_DISTANCE_MIN ); +return ; + } + + numa_info[src].distance[dst] = val; + have_numa_distance = true; +} +static int parse_numa (void *opaque,QemuOpts *opts,Error **errp) {NumaOptions *object =NULL ;
numa.c static int parse_numa(void *opaque, QemuOpts *opts, Error **errp) · line 275
Quoted 5 lines
numa.c +2
-0@@ -235,6 +271,12 @@ static int parse_numa(void *opaque, QemuOpts *opts, Error **errp) } nb_numa_nodes++;break ; +case NUMA_OPTIONS_TYPE_DIST : +numa_distance_parse (&object->u.dist, opts, &err);
looks like 'opts' argument isn't used inside numa_distance_parse(), why it's here?
numa.c static void validate_numa_cpus(void) · line 339
Quoted 12 lines
numa.c +5
-0+if (err) { + goto end; + } +break ;default :abort (); }@@ -294,6 +336,63 @@ static void validate_numa_cpus(void)g_free (seen_cpus); } +static void validate_numa_distance (void )
name of function doesn't match what it's doing,
it not only validates but also sets/fixups distance values,
it would be cleaner to split verification and
setting default/implied/mirrored values in to separate functions.
Quoted 20 lines
numa.c +20
-0+{ +int src, dst, s, d; +bool is_asymmetrical = false; +bool opposite_missing = false; + +if (!have_numa_distance) { +return ; + } + +for (src =0 ; src < nb_numa_nodes; src++) { +for (dst = src; dst < nb_numa_nodes; dst++) { + s = src; + d = dst; + +if (numa_info[s].present && numa_info[d].present) { +if (numa_info[s].distance[d] ==0 && + numa_info[d].distance[s] ==0 ) { +if (s == d) { + numa_info[s].distance[d] =NUMA_DISTANCE_MIN ; + }else {
numa.c static void validate_numa_cpus(void) · line 369
Quoted 10 lines
numa.c +10
-0+error_report ("The distance between node %d and %d is missing, " +"please provide all unique node pair distances." , + s, d); +exit (EXIT_FAILURE ); + } + } + +if (numa_info[s].distance[d] ==0 ) { + s = dst; + d = src;
this swapping makes the following up code rather confusing,
I'd prefer dst/src to be used as is in the capacity names imply and s, d dropped
PS:
adding small comments around blocks in this function would help reviewers and whoever comes here later to understand what's going on.
numa.c static void validate_numa_cpus(void) · line 372
Quoted 3 lines
numa.c +3
-0+ } + +if (numa_info[d].distance[s] ==0 ) {
if above swapping happened than this condition would be checking the same array entry as previous condition did, is that correct?
Quoted 6 lines
numa.c +6
-0+ opposite_missing = true; + } + +if ((numa_info[d].distance[s] !=0 ) && + (numa_info[s].distance[d] != numa_info[d].distance[s])) { + is_asymmetrical = true;
numa.c static void validate_numa_cpus(void) · line 388
Quoted 10 lines
numa.c +10
-0+ } + +if (is_asymmetrical) { +if (opposite_missing) { +error_report ("At least one asymmetrical pair of distances " +"is given, please provide distances for both " +"directions of all node pairs." ); +exit (EXIT_FAILURE ); + } + }else {
what if numa_info[d].distance[s] is 0 and numa_info[s].distance[d] is 0 as well? wouldn't we end up with invalid distance entry in SLIT
Quoted 115 lines
numa.c +8
-0+ numa_info[d].distance[s] = numa_info[s].distance[d]; + } + } + } + } +} +void parse_numa_opts (MachineClass *mc) {int i;@@ -390,6 +489,7 @@ void parse_numa_opts(MachineClass *mc) }validate_numa_cpus (); +validate_numa_distance (); }else {numa_set_mem_node_id (0 , ram_size,0 ); }qapi-schema.json +28
-2@@ -5673,10 +5673,14 @@ ## # @NumaOptionsType: # +# @node: NUMA nodes configuration +# +# @dist: NUMA distance configuration (since 2.10) +# # Since: 2.1 ## { 'enum': 'NumaOptionsType', - 'data': [ 'node' ] } + 'data': [ 'node', 'dist' ] } ## # @NumaOptions:@@ -5689,7 +5693,8 @@ 'base': { 'type': 'NumaOptionsType' }, 'discriminator': 'type', 'data': { - 'node': 'NumaNodeOptions' }} + 'node': 'NumaNodeOptions', + 'dist': 'NumaDistOptions' }} ## # @NumaNodeOptions:@@ -5718,6 +5723,27 @@ '*memdev': 'str' }} ## +# @NumaDistOptions: +# +# Set the distance between 2 NUMA nodes. +# +# @src: source NUMA node. +# +# @dst: destination NUMA node. +# +# @val: NUMA distance from source node to destination node. +# When a node is unreachable from another node, set the distance +# between them to 255. +# +# Since: 2.10 +## +{ 'struct': 'NumaDistOptions', + 'data': { + 'src': 'uint16', + 'dst': 'uint16', + 'val': 'uint8' }} + +## # @HostMemPolicy: # # Host memory policy typesqemu-options.hx +15
-1@@ -139,12 +139,15 @@ ETEXI DEF("numa", HAS_ARG, QEMU_OPTION_numa, "-numa node[,mem=size][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n" - "-numa node[,memdev=id][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n", QEMU_ARCH_ALL) + "-numa node[,memdev=id][,cpus=firstcpu[-lastcpu]][,nodeid=node]\n" + "-numa dist,src=source,dst=destination,val=distance\n", QEMU_ARCH_ALL) STEXI @item -numa node[,mem=@var{size}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}] @itemx -numa node[,memdev=@var{id}][,cpus=@var{firstcpu}[-@var{lastcpu}]][,nodeid=@var{node}] +@itemx -numa dist,src=@var{source},dst=@var{destination},val=@var{distance} @findex -numa Define a NUMA node and assign RAM and VCPUs to it. +Set the NUMA distance from a source node to a destination node. @var{firstcpu} and @var{lastcpu} are CPU indexes. Each @samp{cpus} option represent a contiguous range of CPU indexes@@ -167,6 +170,17 @@ split equally between them. @samp{mem} and @samp{memdev} are mutually exclusive. Furthermore, if one node uses @samp{memdev}, all of them have to use it. +@var{source} and @var{destination} are NUMA node IDs. +@var{distance} is the NUMA distance from @var{source} to @var{destination}. +The distance from a node to itself is always 10. If any pair of nodes is +given a distance, then all pairs must be given distances. Although, when +distances are only given in one direction for each pair of nodes, then +the distances in the opposite directions are assumed to be the same. If, +however, an asymmetrical pair of distances is given for even one node +pair, then all node pairs must be provided distance values for both +directions, even when they are symmetrical. When a node is unreachable +from another node, set the pair's distance to 255. + Note that the -@option{numa} option doesn't allocate any of the specified resources, it just assigns existing resources to NUMA nodes. This means that one still has to use the @option{-m},
Quoted 152 lines · Igor Mammedov
Quoted 149 lines · On Tue, 11 Apr 2017 16:49:26 +0800 He Chen <[email protected]> wrote:
This patch is going to add SLIT table support in QEMU, and provides additional option
distfor command-numato allow user set vNUMA distance by QEMU command.With this patch, when a user wants to create a guest that contains several vNUMA nodes and also wants to set distance among those nodes, the QEMU command would like:
```
(quoted diff) +0
-10-numa node,nodeid=0,cpus=0 \ -numa node,nodeid=1,cpus=1 \ -numa node,nodeid=2,cpus=2 \ -numa node,nodeid=3,cpus=3 \ -numa dist,src=0,dst=1,val=21 \ -numa dist,src=0,dst=2,val=31 \ -numa dist,src=0,dst=3,val=41 \ -numa dist,src=1,dst=2,val=21 \ -numa dist,src=1,dst=3,val=31 \ -numa dist,src=2,dst=3,val=21 \```
Signed-off-by He Chen <[email protected]>--- hw/acpi/aml-build.c | 25 +++++++++++ hw/i386/acpi-build.c | 4 ++ include/hw/acpi/aml-build.h | 1 + include/sysemu/numa.h | 2 + include/sysemu/sysemu.h | 4 ++ numa.c | 100 ++++++++++++++++++++++++++++++++++++++++++++ qapi-schema.json | 30 ++++++++++++- qemu-options.hx | 16 ++++++- 8 files changed, 179 insertions(+), 3 deletions(-)hw/acpi/aml-build.c +25
-0@@ -24,6 +24,7 @@#include "hw/acpi/aml-build.h" #include "qemu/bswap.h" #include "qemu/bitops.h" +#include "sysemu/numa.h" static GArray *build_alloc_array (void ) {@@ -1609,3 +1610,27 @@ void build_srat_memory(AcpiSratMemoryAffinity *numamem, uint64_t base, numamem->base_addr =cpu_to_le64 (base); numamem->range_length =cpu_to_le64 (len); } + +/* +* ACPI spec 5.2.17 System Locality Distance Information Table +* (Revision 2.0 or later) +*/ +void build_slit (GArray *table_data,BIOSLinker *linker) +{ +int slit_start, i, j; + slit_start = table_data->len; + +acpi_data_push (table_data,sizeof (AcpiTableHeader)); + +build_append_int_noprefix (table_data, nb_numa_nodes,8 ); +for (i =0 ; i < nb_numa_nodes; i++) { +for (j =0 ; j < nb_numa_nodes; j++) { +build_append_int_noprefix (table_data, numa_info[i].distance[j],1 ); + } + } + +build_header (linker, table_data, + (void *)(table_data->data + slit_start), +"SLIT" , + table_data->len - slit_start,1 ,NULL ,NULL ); +}hw/i386/acpi-build.c +4
-0@@ -2678,6 +2678,10 @@ void acpi_build(AcpiBuildTables *tables, MachineState *machine)if (pcms->numa_nodes) {acpi_add_table (table_offsets, tables_blob);build_srat (tables_blob, tables->linker, machine); +if (have_numa_distance) { +acpi_add_table (table_offsets, tables_blob); +build_slit (tables_blob, tables->linker); + } }if (acpi_get_mcfg (&mcfg)) {acpi_add_table (table_offsets, tables_blob);include/hw/acpi/aml-build.h +1
-0@@ -389,4 +389,5 @@ GCC_FMT_ATTR(2, 3);void build_srat_memory (AcpiSratMemoryAffinity *numamem,uint64_t base,uint64_t len,int node,MemoryAffinityFlags flags); +void build_slit (GArray *table_data,BIOSLinker *linker);#endif include/sysemu/numa.h +2
-0@@ -8,6 +8,7 @@#include "hw/boards.h" extern int nb_numa_nodes;/* Number of NUMA nodes */ +extern bool have_numa_distance;struct numa_addr_range {ram_addr_t mem_start;@@ -21,6 +22,7 @@ typedef struct node_info {struct HostMemoryBackend *node_memdev;bool present; QLIST_HEAD(, numa_addr_range) addr; /* List to store address ranges */ +uint8_t distance[MAX_NODES ]; } NodeInfo;extern NodeInfo numa_info[MAX_NODES ];include/sysemu/sysemu.h +4
-0@@ -169,6 +169,10 @@ extern int mem_prealloc;#define MAX_NODES 128#define NUMA_NODE_UNASSIGNED MAX_NODES +#define NUMA_DISTANCE_MIN 10 +#define NUMA_DISTANCE_DEFAULT 20 +#define NUMA_DISTANCE_MAX 254 +#define NUMA_DISTANCE_UNREACHABLE 255#define MAX_OPTION_ROMS 16 typedef struct QEMUOptionRom {numa.c +1
-0@@ -51,6 +51,7 @@ static int max_numa_nodeid; /* Highest specified NUMA node ID, plus one.* For all nodes, nodeid < max_numa_nodeid */ int nb_numa_nodes; +bool have_numa_distance;NodeInfo numa_info[MAX_NODES ];void numa_set_mem_node_id (ram_addr_t addr,uint64_t size,uint32_t node)@@ -212,6 +213,41 @@ static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) max_numa_nodeid =MAX (max_numa_nodeid, nodenr +1 ); }
Quoted 10 lines
numa.c static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) · line 222
Quoted 7 lines
numa.c +7
-0+static void numa_distance_parse (NumaDistOptions *dist,QemuOpts *opts,Error **errp) +{ +uint16_t src = dist->src; +uint16_t dst = dist->dst; +uint8_t val = dist->val; + +if (!numa_info[src].present || !numa_info[dst].present) {possible out of bounds read since src/dst here could be >
MAX_NODEShere, move this block after "if (src >=MAX_NODES|| dst >=MAX_NODES) {"
Yes, thanks for pointing it out.
Quoted 8 lines
numa.c static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) · line 230
Quoted 8 lines
numa.c +8
-0+error_setg (errp,"Source/Destination NUMA node is missing. " +"Please use '-numa node' option to declare it first." ); +return ; + } + +if (src >=MAX_NODES || dst >=MAX_NODES ) { +error_setg (errp,"Max number of NUMA nodes reached: %" + PRIu16"" ,MAX_NODES );
Quoted 5 lines
message implies that max number of nodes has been allocated, which is not what check verifies.
how about:
"Invalid node %" PRIu16 ", max possible could be %d"
As we should tell user which nodeid (src or dst) is invalid, what do you think of divide this if into 2 ifs like:
```
if (src >= MAX_NODES) {
error_setg(errp,
"Invalid node %" PRIu16
", max possible could be %" PRIu16,
src, MAX_NODES);
return;
}
if (dst >= MAX_NODES) {
error_setg(errp,
"Invalid node %" PRIu16
", max possible could be %" PRIu16,
dst, MAX_NODES);
return;
}
```Quoted 43 lines
Quoted 24 lines
numa.c +20
-0+return ; + } + +if (val <NUMA_DISTANCE_MIN ) { +error_setg (errp,"NUMA distance (%" PRIu8") is invalid, " +"it should be larger than %d." , + val,NUMA_DISTANCE_MIN ); +return ; + } + +if (src == dst && val !=NUMA_DISTANCE_MIN ) { +error_setg (errp,"Local distance of node %d should be %d." , + src,NUMA_DISTANCE_MIN ); +return ; + } + + numa_info[src].distance[dst] = val; + have_numa_distance = true; +} +static int parse_numa (void *opaque,QemuOpts *opts,Error **errp) {NumaOptions *object =NULL ;numa.c static int parse_numa(void *opaque, QemuOpts *opts, Error **errp) · line 275
Quoted 5 lines
numa.c +2
-0@@ -235,6 +271,12 @@ static int parse_numa(void *opaque, QemuOpts *opts, Error **errp) } nb_numa_nodes++;break ; +case NUMA_OPTIONS_TYPE_DIST : +numa_distance_parse (&object->u.dist, opts, &err);looks like 'opts' argument isn't used inside
numa_distance_parse(), why it's here?Quoted 11 lines
numa.c +4
-0+if (err) { + goto end; + } +break ;default :abort (); }@@ -294,6 +336,63 @@ static void validate_numa_cpus(void)g_free (seen_cpus); }
Quoted 7 lines
numa.c static void validate_numa_cpus(void) · line 339
Quoted 1 line
numa.c +1
-0+static void validate_numa_distance (void )name of function doesn't match what it's doing,
it not only validates but also sets/fixups distance values,it would be cleaner to split verification and
setting default/implied/mirrored values in to separate functions.
I agree that split these operations to sepaprate functions (e.g. validate_numa_distance and fixup_numa_distance) would be a good idea.
But if so, two functions would repeat some operations e.g. check whether the numa distance table is asymmetrical.
I prefer to keep validation and fixup in one function, of course, if we come up with a good function name and we can make the function code clear enough. Please correct me if I am wrong.
Quoted 33 lines
Quoted 20 lines
numa.c +20
-0+{ +int src, dst, s, d; +bool is_asymmetrical = false; +bool opposite_missing = false; + +if (!have_numa_distance) { +return ; + } + +for (src =0 ; src < nb_numa_nodes; src++) { +for (dst = src; dst < nb_numa_nodes; dst++) { + s = src; + d = dst; + +if (numa_info[s].present && numa_info[d].present) { +if (numa_info[s].distance[d] ==0 && + numa_info[d].distance[s] ==0 ) { +if (s == d) { + numa_info[s].distance[d] =NUMA_DISTANCE_MIN ; + }else {numa.c static void validate_numa_cpus(void) · line 369
Quoted 10 lines
numa.c +10
-0+error_report ("The distance between node %d and %d is missing, " +"please provide all unique node pair distances." , + s, d); +exit (EXIT_FAILURE ); + } + } + +if (numa_info[s].distance[d] ==0 ) { + s = dst; + d = src;this swapping makes the following up code rather confusing,
I'd prefer dst/src to be used as is in the capacity names imply and s, d dropped
Quoted 5 lines
PS:
adding small comments around blocks in this function would help reviewers and whoever comes here later to understand what's going on.
Oh, there should be comments here.
May I explain why I choose to use var s/d here and do this swapping.
Let's see some input cases first:
+-----------+ +-----------+ +-----------+
|XX 21 31 41| |XX 21 31 XX| |XX 21 31 41|
|XX XX 21 31| |XX XX 21 31| |XX XX 21 31|
|XX XX XX 21| |XX XX XX 21| |XX XX 10 21|
|XX XX XX XX| |41 XX XX XX| |51 XX XX 10|
+-----------+ +-----------+ +-----------+
(1) (2) (3)(XX means the value is not provided by users.)
According to previous discussion, we agreed that user at least should provide Table (1) as legal input because we can complete the whole with default mirror distance policy.
Regarding Table (2), I think we also agreed that it is legal because if we move left bottom 41 to the opposite position we still get a upper triangular matrix and it is the same as Table (1).
I have to admit that s/d is confusing, what I mean is that s represents the entry in upper triangular matrix and d represents the entry in the lower triangular matrix that is symmetric with respect to the main diagonal.
if (numa_info[s].distance[d] == 0) means that we miss the distance value in the upper triangular matrix, we would encounter this in table (2). In this case, we want to deal with Table (2) in the same way as Table (1). So we do the swapping.
Table (1) and Table (2) would be regarded as symmetric matrices, they are the same essentially.
Table (3) is illegal input since we find that one asymmetrical pair of distances is given, in this case, the whole table should be given.
Quoted 6 lines
numa.c static void validate_numa_cpus(void) · line 372
Quoted 3 lines
numa.c +3
-0+ } + +if (numa_info[d].distance[s] ==0 ) {if above swapping happened than this condition would be checking the same array entry as previous condition did, is that correct?
I think yes although it does the same thing as previous condition from the code view. Here, we want to check if the opposite entry is not set. Let's see Table (2), when we process entry(1,4) i.e. numa_info[0].distance[3], we find it is 0, then we swap s and d, now numa_info[s].distance[d] is 41, and we will see this condition makes sense in this case.
Quoted 10 lines
Quoted 10 lines
numa.c +10
-0+ opposite_missing = true; + } + +if ((numa_info[d].distance[s] !=0 ) && + (numa_info[s].distance[d] != numa_info[d].distance[s])) { + is_asymmetrical = true; + } + +if (is_asymmetrical) { +if (opposite_missing) {
Quoted 9 lines
numa.c static void validate_numa_cpus(void) · line 388
Quoted 6 lines
numa.c +6
-0+error_report ("At least one asymmetrical pair of distances " +"is given, please provide distances for both " +"directions of all node pairs." ); +exit (EXIT_FAILURE ); + } + }else {what if numa_info[d].distance[s] is 0 and numa_info[s].distance[d] is 0 as well? wouldn't we end up with invalid distance entry in SLIT
At the start of this function, we ensure that the symmetric value would not be both 0.
I know, the code in this function may be not clear enough. But when I treat the whole numa distance table as a matrix, it looks fine. Anyway, this is my point of view, if you have any sugguestion, I am very willing to know and cook a better patch in next version.
Thanks,
-He
Quoted 3 lines · On Thu, 20 Apr 2017 17:25:45 +0800 He Chen <[email protected]> wrote:
Quoted 2 lines · Igor Mammedov
On Tue, 11 Apr 2017 16:49:26 +0800
He Chen <[email protected]> wrote:
...
Quoted 13 lines
Quoted 8 lines
numa.c static void numa_node_parse(NumaNodeOptions *node, QemuOpts *opts, Error **errp) · line 230
Quoted 8 lines
numa.c +8
-0+error_setg (errp,"Source/Destination NUMA node is missing. " +"Please use '-numa node' option to declare it first." ); +return ; + } + +if (src >=MAX_NODES || dst >=MAX_NODES ) { +error_setg (errp,"Max number of NUMA nodes reached: %" + PRIu16"" ,MAX_NODES );Quoted 5 lines
message implies that max number of nodes has been allocated, which is not what check verifies.
how about:
"Invalid node %" PRIu16 ", max possible could be %d"
Quoted 5 lines
As we should tell user which nodeid (src or dst) is invalid, what do you think of divide this if into 2 ifs like:
```
if (src >= MAX_NODES) {
or shorter, keep original if and ...
Quoted 4 lines
error_setg(errp,
"Invalid node %" PRIu16
", max possible could be %" PRIu16, src,MAX_NODES);
s/src/MAX(src, dst)/
Quoted 67 lines
return; } if (dst >= MAX_NODES) { error_setg(errp, "Invalid node %" PRIu16 ", max possible could be %" PRIu16, dst, MAX_NODES); return; }```
Quoted 43 lines
Quoted 24 lines
numa.c +20
-0+return ; + } + +if (val <NUMA_DISTANCE_MIN ) { +error_setg (errp,"NUMA distance (%" PRIu8") is invalid, " +"it should be larger than %d." , + val,NUMA_DISTANCE_MIN ); +return ; + } + +if (src == dst && val !=NUMA_DISTANCE_MIN ) { +error_setg (errp,"Local distance of node %d should be %d." , + src,NUMA_DISTANCE_MIN ); +return ; + } + + numa_info[src].distance[dst] = val; + have_numa_distance = true; +} +static int parse_numa (void *opaque,QemuOpts *opts,Error **errp) {NumaOptions *object =NULL ;numa.c static int parse_numa(void *opaque, QemuOpts *opts, Error **errp) · line 275
Quoted 5 lines
numa.c +2
-0@@ -235,6 +271,12 @@ static int parse_numa(void *opaque, QemuOpts *opts, Error **errp) } nb_numa_nodes++;break ; +case NUMA_OPTIONS_TYPE_DIST : +numa_distance_parse (&object->u.dist, opts, &err);looks like 'opts' argument isn't used inside
numa_distance_parse(), why it's here?Quoted 11 lines
numa.c +4
-0+if (err) { + goto end; + } +break ;default :abort (); }@@ -294,6 +336,63 @@ static void validate_numa_cpus(void)g_free (seen_cpus); }Quoted 7 lines
numa.c static void validate_numa_cpus(void) · line 339
Quoted 1 line
numa.c +1
-0+static void validate_numa_distance (void )name of function doesn't match what it's doing,
it not only validates but also sets/fixups distance values,it would be cleaner to split verification and
setting default/implied/mirrored values in to separate functions.I agree that split these operations to sepaprate functions (e.g.
validate_numa_distanceandfixup_numa_distance) would be a good idea.
Quoted 6 lines
But if so, two functions would repeat some operations e.g. check whether the numa distance table is asymmetrical.
I prefer to keep validation and fixup in one function, of course, if we come up with a good function name and we can make the function code clear enough. Please correct me if I am wrong.
It's not a big deal to have a little extra lines if it helps to make code cleaner. So I suggest to go with 2 separate functions validate + complete_initialization.
Quoted 86 lines
Quoted 33 lines
Quoted 20 lines
numa.c +20
-0+{ +int src, dst, s, d; +bool is_asymmetrical = false; +bool opposite_missing = false; + +if (!have_numa_distance) { +return ; + } + +for (src =0 ; src < nb_numa_nodes; src++) { +for (dst = src; dst < nb_numa_nodes; dst++) { + s = src; + d = dst; + +if (numa_info[s].present && numa_info[d].present) { +if (numa_info[s].distance[d] ==0 && + numa_info[d].distance[s] ==0 ) { +if (s == d) { + numa_info[s].distance[d] =NUMA_DISTANCE_MIN ; + }else {numa.c static void validate_numa_cpus(void) · line 369
Quoted 10 lines
numa.c +10
-0+error_report ("The distance between node %d and %d is missing, " +"please provide all unique node pair distances." , + s, d); +exit (EXIT_FAILURE ); + } + } + +if (numa_info[s].distance[d] ==0 ) { + s = dst; + d = src;this swapping makes the following up code rather confusing,
I'd prefer dst/src to be used as is in the capacity names imply and s, d droppedQuoted 5 lines
PS:
adding small comments around blocks in this function would help reviewers and whoever comes here later to understand what's going on.Oh, there should be comments here.
May I explain why I choose to use var s/d here and do this swapping.
Let's see some input cases first:
+-----------+ +-----------+ +-----------+ |XX 21 31 41| |XX 21 31 XX| |XX 21 31 41| |XX XX 21 31| |XX XX 21 31| |XX XX 21 31| |XX XX XX 21| |XX XX XX 21| |XX XX 10 21| |XX XX XX XX| |41 XX XX XX| |51 XX XX 10| +-----------+ +-----------+ +-----------+ (1) (2) (3)(XX means the value is not provided by users.)
According to previous discussion, we agreed that user at least should provide Table (1) as legal input because we can complete the whole with default mirror distance policy.
Regarding Table (2), I think we also agreed that it is legal because if we move left bottom 41 to the opposite position we still get a upper triangular matrix and it is the same as Table (1).I have to admit that s/d is confusing, what I mean is that
srepresents the entry in upper triangular matrix anddrepresents the entry in the lower triangular matrix that is symmetric with respect to the main diagonal.
if (numa_info[s].distance[d] == 0)means that we miss the distance value in the upper triangular matrix, we would encounter this in table (2). In this case, we want to deal with Table (2) in the same way as Table (1). So we do the swapping.Table (1) and Table (2) would be regarded as symmetric matrices, they are the same essentially.
Table (3) is illegal input since we find that one asymmetrical pair of distances is given, in this case, the whole table should be given.Quoted 6 lines
numa.c static void validate_numa_cpus(void) · line 372
Quoted 3 lines
numa.c +3
-0+ } + +if (numa_info[d].distance[s] ==0 ) {if above swapping happened than this condition would be checking the same array entry as previous condition did, is that correct?
I think yes although it does the same thing as previous condition from the code view. Here, we want to check if the opposite entry is not set. Let's see Table (2), when we process
entry(1,4)i.e.numa_info[0].distance[3], we find it is 0, then we swapsandd, nownuma_info[s].distance[d]is41, and we will see this condition makes sense in this case.
Quoted 10 lines
Quoted 10 lines
numa.c static void validate_numa_cpus(void) · line 382
Quoted 10 lines
numa.c +10
-0+ opposite_missing = true; + } + +if ((numa_info[d].distance[s] !=0 ) && + (numa_info[s].distance[d] != numa_info[d].distance[s])) { + is_asymmetrical = true; + } + +if (is_asymmetrical) { +if (opposite_missing) {
this check will start working only after is_asymmetrical detected, but entries that were checked before are left unverified for missing opposite. So function won't work as described.
To guarantee that all entries have opposite, you have to do 2 passes over matrix.
Quoted 9 lines
Quoted 9 lines
numa.c static void validate_numa_cpus(void) · line 388
Quoted 6 lines
numa.c +6
-0+error_report ("At least one asymmetrical pair of distances " +"is given, please provide distances for both " +"directions of all node pairs." ); +exit (EXIT_FAILURE ); + } + }else {what if numa_info[d].distance[s] is 0 and numa_info[s].distance[d] is 0 as well? wouldn't we end up with invalid distance entry in SLIT
Quoted 7 lines
At the start of this function, we ensure that the symmetric value would not be both 0.
I know, the code in this function may be not clear enough. But when I treat the whole numa distance table as a matrix, it looks fine. Anyway, this is my point of view, if you have any sugguestion, I am very willing to know and cook a better patch in next version.
Suggestions stay the same:
1. split validate in init into separate functions, it should make code simpler to follow.
2. don't do swapping just use src/dst as is
3. add comments and maybe a larger one before validate function
to describe valid input so that reader won't have to check out qemu-options.hx
Quoted 4 lines
Thanks,
-He