summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorIgor Mammedov2018-05-16 17:06:14 +0200
committerEduardo Habkost2018-05-30 18:08:11 +0200
commit74f38e96b321ef8df2bf7fa1bd4f673ef06aca5b (patch)
treed9acebdd53535a85ffddaffc1a771779461d6fd1 /include
parentMerge remote-tracking branch 'remotes/edgar/tags/edgar/xilinx-next-2018-05-29... (diff)
downloadqemu-74f38e96b321ef8df2bf7fa1bd4f673ef06aca5b.tar.gz
qemu-74f38e96b321ef8df2bf7fa1bd4f673ef06aca5b.tar.xz
qemu-74f38e96b321ef8df2bf7fa1bd4f673ef06aca5b.zip
numa: clarify error message when node index is out of range in -numa dist, ...
When using following CLI: -numa dist,src=128,dst=1,val=20 user gets a rather confusing error message: "Invalid node 128, max possible could be 128" Where 128 is number of nodes that QEMU supports (MAX_NODES), while src/dst is an index up to that limit, so it should be MAX_NODES - 1 in error message. Make error message to explicitly state valid range for node index to be more clear. Signed-off-by: Igor Mammedov <imammedo@redhat.com> Message-Id: <1526483174-169008-1-git-send-email-imammedo@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions