summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/kvm/Kconfig
diff options
context:
space:
mode:
authorMichael Neuling <mikey@neuling.org>2019-06-04 05:00:37 +0200
committerMichael Ellerman <mpe@ellerman.id.au>2019-07-03 07:19:35 +0200
commita278e7ea608bea5fe6df9b6ae91fa134655c5d2c (patch)
tree5eeb4faa4d6b050d034841d488b9e916429c6af5 /arch/powerpc/kvm/Kconfig
parentpowerpc: silence a -Wcast-function-type warning in dawr_write_file_bool (diff)
downloadlinux-a278e7ea608bea5fe6df9b6ae91fa134655c5d2c.tar.xz
linux-a278e7ea608bea5fe6df9b6ae91fa134655c5d2c.zip
powerpc: Fix compile issue with force DAWR
If you compile with KVM but without CONFIG_HAVE_HW_BREAKPOINT you fail at linking with: arch/powerpc/kvm/book3s_hv_rmhandlers.o:(.text+0x708): undefined reference to `dawr_force_enable' This was caused by commit c1fe190c0672 ("powerpc: Add force enable of DAWR on P9 option"). This moves a bunch of code around to fix this. It moves a lot of the DAWR code in a new file and creates a new CONFIG_PPC_DAWR to enable compiling it. Fixes: c1fe190c0672 ("powerpc: Add force enable of DAWR on P9 option") Signed-off-by: Michael Neuling <mikey@neuling.org> [mpe: Minor formatting in set_dawr()] Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to '')
-rw-r--r--arch/powerpc/kvm/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/powerpc/kvm/Kconfig b/arch/powerpc/kvm/Kconfig
index f53997a8ca62..b8e13d5a4a31 100644
--- a/arch/powerpc/kvm/Kconfig
+++ b/arch/powerpc/kvm/Kconfig
@@ -38,6 +38,7 @@ config KVM_BOOK3S_32_HANDLER
config KVM_BOOK3S_64_HANDLER
bool
select KVM_BOOK3S_HANDLER
+ select PPC_DAWR_FORCE_ENABLE
config KVM_BOOK3S_PR_POSSIBLE
bool