diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2018-01-04 14:33:21 +1100 |
|---|---|---|
| committer | David Gibson <david@gibson.dropbear.id.au> | 2018-01-10 12:53:00 +1100 |
| commit | 51f84465dd985fc21589b2eac1f18658fc9783e9 (patch) | |
| tree | e5b52cbf697fcd51effc429d346536d2389fb7fa /MAINTAINERS | |
| parent | a7167668898d1a7dbb717fe1e6d5615bd229827c (diff) | |
| download | qemu-51f84465dd985fc21589b2eac1f18658fc9783e9.zip qemu-51f84465dd985fc21589b2eac1f18658fc9783e9.tar.gz qemu-51f84465dd985fc21589b2eac1f18658fc9783e9.tar.bz2 | |
spapr: Correct compatibility mode setting for hotplugged CPUs
Currently the pseries machine sets the compatibility mode for the
guest's cpus in two places: 1) at machine reset and 2) after CAS
negotiation.
This means that if we set or negotiate a compatiblity mode, then
hotplug a cpu, the hotplugged cpu doesn't get the right mode set and
will incorrectly have the full native features.
To correct this, we set the compatibility mode on a cpu when it is
brought online with the 'start-cpu' RTAS call. Given that we no
longer need to set the compatibility mode on all CPUs at machine
reset, so we change that to only set the mode for the boot cpu.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reported-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Tested-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions