aboutsummaryrefslogtreecommitdiff
path: root/tcg/README
diff options
context:
space:
mode:
authorSam Bobroff <sam.bobroff@au1.ibm.com>2017-08-18 15:50:22 +1000
committerDavid Gibson <david@gibson.dropbear.id.au>2017-09-08 09:30:55 +1000
commitfa98fbfcdfcb980b4a690b8bc93ab597935087b1 (patch)
treedf06da704c52b1e04a645f9104dd03e00ad97b64 /tcg/README
parentcc7b35b169e96600c09947a31c610c84a3eda3ff (diff)
downloadqemu-fa98fbfcdfcb980b4a690b8bc93ab597935087b1.zip
qemu-fa98fbfcdfcb980b4a690b8bc93ab597935087b1.tar.gz
qemu-fa98fbfcdfcb980b4a690b8bc93ab597935087b1.tar.bz2
PPC: KVM: Support machine option to set VSMT mode
KVM now allows writing to KVM_CAP_PPC_SMT which has previously been read only. Doing so causes KVM to act, for that VM, as if the host's SMT mode was the given value. This is particularly important on Power 9 systems because their default value is 1, but they are able to support values up to 8. This patch introduces a way to control this capability via a new machine property called VSMT ("Virtual SMT"). If the value is not set on the command line a default is chosen that is, when possible, compatible with legacy systems. Note that the intialization of KVM_CAP_PPC_SMT has changed slightly because it has changed (in KVM) from a global capability to a VM-specific one. This won't cause a problem on older KVMs because VM capabilities fall back to global ones. Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'tcg/README')
0 files changed, 0 insertions, 0 deletions