summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorPaul Mackerras <paulus@ozlabs.org>2018-06-07 18:08:02 +1000
committerPaul Mackerras <paulus@ozlabs.org>2018-06-13 09:45:28 +1000
commitdb96a04a86c73817b4584aa4fa2a3f60a9aa3c52 (patch)
treeb79c30082d0e82ce5b53dc55ac4135686aed423d /arch
parent4f169d21181faad87a6cdb288742e08c808ec0ef (diff)
KVM: PPC: Book3S PR: Enable use on POWER9 bare-metal hosts in HPT mode
It turns out that PR KVM has no dependency on the format of HPTEs, because it uses functions pointed to by mmu_hash_ops which do all the formatting and interpretation of HPTEs. Thus we can allow PR KVM to load on POWER9 bare-metal hosts as long as they are running in HPT mode. Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/powerpc/kvm/book3s_pr.c8
1 files changed, 2 insertions, 6 deletions
diff --git a/arch/powerpc/kvm/book3s_pr.c b/arch/powerpc/kvm/book3s_pr.c
index 5c99b84e0856..c3b8006f0eac 100644
--- a/arch/powerpc/kvm/book3s_pr.c
+++ b/arch/powerpc/kvm/book3s_pr.c
@@ -2041,13 +2041,9 @@ static int kvmppc_core_check_processor_compat_pr(void)
* PR KVM can work on POWER9 inside a guest partition
* running in HPT mode. It can't work if we are using
* radix translation (because radix provides no way for
- * a process to have unique translations in quadrant 3)
- * or in a bare-metal HPT-mode host (because POWER9
- * uses a modified HPTE format which the PR KVM code
- * has not been adapted to use).
+ * a process to have unique translations in quadrant 3).
*/
- if (cpu_has_feature(CPU_FTR_ARCH_300) &&
- (radix_enabled() || cpu_has_feature(CPU_FTR_HVMODE)))
+ if (cpu_has_feature(CPU_FTR_ARCH_300) && radix_enabled())
return -EIO;
return 0;
}