diff options
author | Ryan Grimm <grimm@linux.ibm.com> | 2019-10-01 13:17:53 -0400 |
---|---|---|
committer | Ram Pai <linuxram@us.ibm.com> | 2020-11-02 19:35:09 -0500 |
commit | 0a1317d27857e4cf87b66746d3592690906c2789 (patch) | |
tree | 83c1a53ee2e36968ac19036caa8172ec2bd0bc7b | |
parent | 39dc74ed319613c84fc4b0f2544b3aeec4346b28 (diff) | |
download | skiboot-0a1317d27857e4cf87b66746d3592690906c2789.zip skiboot-0a1317d27857e4cf87b66746d3592690906c2789.tar.gz skiboot-0a1317d27857e4cf87b66746d3592690906c2789.tar.bz2 |
ifdef out tm-suspend-hypervisor-assist cpu feature
We've tried
(1) disabling TM in the host via device tree
(2) disabling TM in qemu via "cap-tm=off"
(3) disabling TM in guest via kernel command line
but we're still getting this:
[ 81.914285] Facility 'TM' unavailable (5) exception in kernel mode at c000000000140324
[ 81.914298] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
[ 81.914305] LE PAGE_SIZE=64K MMU=Radix MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
[ 81.914312] Modules linked in:
[ 81.914318] CPU: 59 PID: 1487 Comm: qemu-system-ppc Not tainted 5.3.0-rc5-46613-gcafd1c60ac88 #1
[ 81.914325] NIP: c000000000140324 LR: c00000000012afa8 CTR: c00000000012c960
[ 81.914332] REGS: c000003d5032b490 TRAP: 0f60 Not tainted (5.3.0-rc5-46613-gcafd1c60ac88)
[ 81.914338] MSR: 9000000002803033 <SF,HV,VEC,VSX,FP,ME,IR,DR,RI,LE> CR: 22242242 XER: 00000000
[ 81.914349] CFAR: c00000000012afa4 IRQMASK: 3
[ 81.914349] GPR00: 0000000000000001 c000003d5032b720 c000000001791800 c000003d44900000
[ 81.914349] GPR04: 8000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 81.914349] GPR08: 0000000000000001 0000000000000001 0000000000000000 00000010068e5b9c
[ 81.914349] GPR12: 0000000000004000 c000003dbffcd380 0000000000000000 00007fffa92a0000
[ 81.914349] GPR16: 0000000000000000 00007fffaa5d4410 0000000000000000 0000000000000001
[ 81.914349] GPR20: c000000001966378 000000000000003b c000003d4478a558 0000000000000010
[ 81.914349] GPR24: 0000000000000000 4000000000000000 c000000000000000 0000000000000980
[ 81.914349] GPR28: c000003d50090000 004000000054f41f 0000001006a57e04 c000003d44900000
[ 81.914401] NIP [c000000000140324] kvmppc_restore_tm_hv+0x38/0x80
[ 81.914407] LR [c00000000012afa8] kvmhv_p9_guest_entry+0x108/0x910
[ 81.914412] Call Trace:
[ 81.914416] [c000003d5032b720] [c00000000012afa8] kvmhv_p9_guest_entry+0x108/0x910 (unreliable)
[ 81.914424] [c000003d5032b900] [c00000000012c09c] kvmhv_run_single_vcpu+0x2fc/0xbc0
[ 81.914431] [c000003d5032b9d0] [c00000000012cf80] kvmppc_vcpu_run_hv+0x620/0xb80
[ 81.914438] [c000003d5032bae0] [c000000000111664] kvmppc_vcpu_run+0x34/0x50
[ 81.914444] [c000003d5032bb00] [c00000000010db8c] kvm_arch_vcpu_ioctl_run+0x23c/0x410
[ 81.914451] [c000003d5032bb90] [c000000000100058] kvm_vcpu_ioctl+0x468/0x7c0
[ 81.914458] [c000003d5032bd00] [c000000000440de0] do_vfs_ioctl+0xe0/0xc60
[ 81.914465] [c000003d5032bdb0] [c0000000004419c4] ksys_ioctl+0x64/0xf0
[ 81.914472] [c000003d5032be00] [c000000000441a78] sys_ioctl+0x28/0x80
[ 81.914478] [c000003d5032be20] [c00000000000bae4] system_call+0x5c/0x70
[ 81.914483] Instruction dump:
[ 81.914487] 60000000 7c0802a6 f8010010 38000000 980d0b28 7ca000a6 38000001 780507ce
[ 81.914496] 7ca00164 e8a315e8 e8c315f8 e8e315f0 <7ca023a6> 7cc123a6 7ce223a6 7885ffa1
[ 81.914506] ---[ end trace 7ee98dd79ab5b3b0 ]---
[ 81.915662]
[ 81.915684] qemu-system-ppc (1487) used greatest stack depth: 11152 bytes left
Need to dig and figure out how to disable this cpu feature in the guest.
Signed-off-by: Ryan Grimm <grimm@linux.ibm.com>
-rw-r--r-- | core/cpufeatures.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/core/cpufeatures.c b/core/cpufeatures.c index ec30c97..5edfe56 100644 --- a/core/cpufeatures.c +++ b/core/cpufeatures.c @@ -713,6 +713,7 @@ static const struct cpu_feature cpu_features_table[] = { -1, -1, -1, NULL, }, +#if 0 /* * Due to hardware bugs in POWER9, the hypervisor needs to assist * guests. @@ -728,6 +729,7 @@ static const struct cpu_feature cpu_features_table[] = { HV_CUSTOM, OS_NONE, -1, -1, -1, NULL, }, +#endif /* * Due to hardware bugs in POWER9, the hypervisor can hit |