cba313da5c
At present, on the powernv platform, if you off-line a CPU that was online, and then try to on-line it again, the kernel generates a warning message "OPAL Error -1 starting CPU n". Furthermore, if the CPU is a secondary thread that was used by KVM while it was off-line, the CPU fails to come online. The first problem is fixed by only calling OPAL to start the CPU the first time it is on-lined, as indicated by the cpu_start field of its PACA being zero. The second problem is fixed by restoring the cpu_start field to 1 instead of 0 when using the CPU within KVM. Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> |
||
---|---|---|
.. | ||
Kconfig | ||
Makefile | ||
opal-nvram.c | ||
opal-rtc.c | ||
opal-takeover.S | ||
opal-wrappers.S | ||
opal.c | ||
pci-ioda.c | ||
pci-p5ioc2.c | ||
pci.c | ||
pci.h | ||
powernv.h | ||
setup.c | ||
smp.c |