diff options
| author | Paul Mackerras <paulus@ozlabs.org> | 2019-08-27 11:31:37 +1000 |
|---|---|---|
| committer | Paul Mackerras <paulus@ozlabs.org> | 2019-08-27 14:08:10 +1000 |
| commit | d28eafc5a64045c78136162af9d4ba42f8230080 (patch) | |
| tree | 89525b785f8ec2cf3bd9b2a882a187a4b89c8ba8 /arch/x86/kernel/kvm.c | |
| parent | 2ad7a27deaf6d78545d97ab80874584f6990360e (diff) | |
KVM: PPC: Book3S HV: Check for MMU ready on piggybacked virtual cores
When we are running multiple vcores on the same physical core, they
could be from different VMs and so it is possible that one of the
VMs could have its arch.mmu_ready flag cleared (for example by a
concurrent HPT resize) when we go to run it on a physical core.
We currently check the arch.mmu_ready flag for the primary vcore
but not the flags for the other vcores that will be run alongside
it. This adds that check, and also a check when we select the
secondary vcores from the preempted vcores list.
Cc: stable@vger.kernel.org # v4.14+
Fixes: 38c53af85306 ("KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT updates")
Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'arch/x86/kernel/kvm.c')
0 files changed, 0 insertions, 0 deletions