aboutsummaryrefslogtreecommitdiff
path: root/bsd-user
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2018-01-15 16:40:23 +1100
committerDavid Gibson <david@gibson.dropbear.id.au>2018-01-17 09:35:24 +1100
commitabbc124753896f72e3715813ea20dd1924202ff0 (patch)
tree19068e4bd8f9f2ab9ab16368659681eec4cfc196 /bsd-user
parent03ee51d3548f5f553a3089f466483c1c6d5c666b (diff)
downloadqemu-abbc124753896f72e3715813ea20dd1924202ff0.zip
qemu-abbc124753896f72e3715813ea20dd1924202ff0.tar.gz
qemu-abbc124753896f72e3715813ea20dd1924202ff0.tar.bz2
target/ppc: Clarify compat mode max_threads value
We recently had some discussions that were sidetracked for a while, because nearly everyone misapprehended the purpose of the 'max_threads' field in the compatiblity modes table. It's all about guest expectations, not host expectations or support (that's handled elsewhere). In an attempt to avoid a repeat of that confusion, rename the field to 'max_vthreads' and add an explanatory comment. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Reviewed-by: Laurent Vivier <lvivier@redhat.com> Reviewed-by: Greg Kurz <groug@kaod.org> Reviewed-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Diffstat (limited to 'bsd-user')
0 files changed, 0 insertions, 0 deletions