diff options
author | Paul Mackerras <paulus@samba.org> | 2012-02-03 00:54:17 (GMT) |
---|---|---|
committer | Avi Kivity <avi@redhat.com> | 2012-04-08 11:01:20 (GMT) |
commit | f0888f70151c7f53de2b45ee20ff1905837943e8 (patch) | |
tree | 80b7e133e681a2b4e4255a8fa747711da4c59211 /arch/powerpc/include/asm/hvcall.h | |
parent | f6127716c346c73ab1513edee53231800188c5ba (diff) | |
download | linux-fsl-qoriq-f0888f70151c7f53de2b45ee20ff1905837943e8.tar.xz |
KVM: PPC: Book3S HV: Make secondary threads more robust against stray IPIs
Currently on POWER7, if we are running the guest on a core and we don't
need all the hardware threads, we do nothing to ensure that the unused
threads aren't executing in the kernel (other than checking that they
are offline). We just assume they're napping and we don't do anything
to stop them trying to enter the kernel while the guest is running.
This means that a stray IPI can wake up the hardware thread and it will
then try to enter the kernel, but since the core is in guest context,
it will execute code from the guest in hypervisor mode once it turns the
MMU on, which tends to lead to crashes or hangs in the host.
This fixes the problem by adding two new one-byte flags in the
kvmppc_host_state structure in the PACA which are used to interlock
between the primary thread and the unused secondary threads when entering
the guest. With these flags, the primary thread can ensure that the
unused secondaries are not already in kernel mode (i.e. handling a stray
IPI) and then indicate that they should not try to enter the kernel
if they do get woken for any reason. Instead they will go into KVM code,
find that there is no vcpu to run, acknowledge and clear the IPI and go
back to nap mode.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'arch/powerpc/include/asm/hvcall.h')
0 files changed, 0 insertions, 0 deletions