KVM: PPC: MMIO fixes
Subsystems (2)
v4 cover KVM: PPC: MMIO fixes
Changes from v3:
Removed all of the low level messages and altered the pr_emerg in the emulate_mmio to a more descriptive message.
Changed the Program interrupt to a Data Storage. There's an ifdef needed because this code is shared by HV, PR and booke.
v3:
https://lore.kernel.org/r/[email protected]
v2:
https://lore.kernel.org/r/[email protected]
v1:
https://lore.kernel.org/r/[email protected]
Fabiano Rosas (5):
KVM: PPC: Book3S HV: Stop returning internal values to userspace
KVM: PPC: Fix vmx/vsx mixup in mmio emulation
KVM: PPC: mmio: Reject instructions that access more than mmio.data
size
KVM: PPC: mmio: Return to guest after emulation failure
KVM: PPC: mmio: Deliver DSI after emulation failure
arch/powerpc/kvm/emulate_loadstore.c | 10 ++---- arch/powerpc/kvm/powerpc.c | 46 ++++++++++++++++++---------- 2 files changed, 33 insertions(+), 23 deletions(-)
Signature · 1 line
2.34.1
PATCH v4 1/5 KVM: PPC: Book3S HV: Stop returning internal values to userspace
Our kvm_arch_vcpu_ioctl_run currently returns the RESUME_HOST values to userspace, against the API of the KVM_RUN ioctl which returns 0 on success.
---
This was noticed while enabling the kvm selftests for powerpc. There's an assert at the _vcpu_run function when we return a value different from the expected.
--- arch/powerpc/kvm/powerpc.c | 8 ++++++++ 1 file changed, 8 insertions(+)
arch/powerpc/kvm/powerpc.c +8 -0
@@ -1841,6 +1841,14 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu)#ifdef CONFIG_ALTIVEC out:#endif + +/* +* We're already returning to userspace, don't pass the +* RESUME_HOST flags along. +*/ +if (r >0 ) + r =0 ; +vcpu_put (vcpu);return r; }
Signature · 1 line
2.34.1
PATCH v4 2/5 KVM: PPC: Fix vmx/vsx mixup in mmio emulation
In reply to Fabiano RosasThe MMIO emulation code for vector instructions is duplicated between VSX and VMX. When emulating VMX we should check the VMX copy size instead of the VSX one.
--- arch/powerpc/kvm/powerpc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/powerpc/kvm/powerpc.c +2 -2
@@ -1499,7 +1499,7 @@ int kvmppc_handle_vmx_load(struct kvm_vcpu *vcpu, {enum emulation_result emulated =EMULATE_DONE ; -if (vcpu->arch.mmio_vsx_copy_nums >2 ) +if (vcpu->arch.mmio_vmx_copy_nums >2 )return EMULATE_FAIL ;while (vcpu->arch.mmio_vmx_copy_nums) {
@@ -1596,7 +1596,7 @@ int kvmppc_handle_vmx_store(struct kvm_vcpu *vcpu,unsigned int index = rs &KVM_MMIO_REG_MASK ;enum emulation_result emulated =EMULATE_DONE ; -if (vcpu->arch.mmio_vsx_copy_nums >2 ) +if (vcpu->arch.mmio_vmx_copy_nums >2 )return EMULATE_FAIL ; vcpu->arch.io_gpr = rs;
Signature · 1 line
2.34.1
PATCH v4 3/5 KVM: PPC: mmio: Reject instructions that access more than mmio.data size
In reply to Fabiano RosasThe MMIO interface between the kernel and userspace uses a structure that supports a maximum of 8-bytes of data. Instructions that access more than that need to be emulated in parts.
We currently don't have generic support for splitting the emulation in parts and each set of instructions needs to be explicitly included.
There's already an error message being printed when a load or store exceeds the mmio.data buffer but we don't fail the emulation until later at kvmppc_complete_mmio_load and even then we allow userspace to make a partial copy of the data, which ends up overwriting some fields of the mmio structure.
This patch makes the emulation fail earlier at kvmppc_handle_load|store, which will send a Program interrupt to the guest. This is better than allowing the guest to proceed with partial data.
Note that this was caught in a somewhat artificial scenario using quadword instructions (lq/stq), there's no account of an actual guest in the wild running instructions that are not properly emulated.
(While here, remove the "bad MMIO" messages. The caller already has an error message.)
--- arch/powerpc/kvm/powerpc.c | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-)
arch/powerpc/kvm/powerpc.c +5 -11
@@ -1114,10 +1114,8 @@ static void kvmppc_complete_mmio_load(struct kvm_vcpu *vcpu)struct kvm_run *run = vcpu->run;u64 gpr; -if (run->mmio.len >sizeof (gpr)) { -printk (KERN_ERR "bad MMIO length: %d\n" , run->mmio.len); +if (run->mmio.len >sizeof (gpr))return ; - }if (!vcpu->arch.mmio_host_swabbed) {switch (run->mmio.len) {
@@ -1236,10 +1234,8 @@ static int __kvmppc_handle_load(struct kvm_vcpu *vcpu, host_swabbed = !is_default_endian; } -if (bytes >sizeof (run->mmio.data)) { -printk (KERN_ERR "%s: bad MMIO length: %d\n" , __func__, - run->mmio.len); - } +if (bytes >sizeof (run->mmio.data)) +return EMULATE_FAIL ; run->mmio.phys_addr = vcpu->arch.paddr_accessed; run->mmio.len = bytes;
@@ -1325,10 +1321,8 @@ int kvmppc_handle_store(struct kvm_vcpu *vcpu, host_swabbed = !is_default_endian; } -if (bytes >sizeof (run->mmio.data)) { -printk (KERN_ERR "%s: bad MMIO length: %d\n" , __func__, - run->mmio.len); - } +if (bytes >sizeof (run->mmio.data)) +return EMULATE_FAIL ; run->mmio.phys_addr = vcpu->arch.paddr_accessed; run->mmio.len = bytes;
Signature · 1 line
2.34.1
PATCH v4 4/5 KVM: PPC: mmio: Return to guest after emulation failure
In reply to Fabiano RosasIf MMIO emulation fails we don't want to crash the whole guest by returning to userspace.
The original commit bbf45ba57eae ("KVM: ppc: PowerPC 440 KVM implementation") added a todo:
/* XXX Deliver Program interrupt to guest. */
and later the commit d69614a295ae ("KVM: PPC: Separate loadstore emulation from priv emulation") added the Program interrupt injection but in another file, so I'm assuming it was missed that this block needed to be altered.
Also change the message to a ratelimited one since we're letting the guest run and it could flood the host logs.
--- arch/powerpc/kvm/powerpc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/powerpc/kvm/powerpc.c +3 -3
@@ -307,9 +307,9 @@ int kvmppc_emulate_mmio(struct kvm_vcpu *vcpu)u32 last_inst;kvmppc_get_last_inst (vcpu,INST_GENERIC , &last_inst); -/* XXX Deliver Program interrupt to guest. */ -pr_emerg ("%s: emulation failed (%08x)\n" , __func__, last_inst); - r =RESUME_HOST ; +pr_info_ratelimited ("KVM: guest access to device memory using unsupported instruction (PID: %d opcode: %#08x)\n" , + current->pid, last_inst); + r =RESUME_GUEST ;break ; }default :
Signature · 1 line
2.34.1
PATCH v4 5/5 KVM: PPC: mmio: Deliver DSI after emulation failure
In reply to Fabiano RosasMMIO emulation can fail if the guest uses an instruction that we are not prepared to emulate. Since these instructions can be and most likely are valid ones, this is (slightly) closer to an access fault than to an illegal instruction, so deliver a Data Storage interrupt instead of a Program interrupt.
--- arch/powerpc/kvm/emulate_loadstore.c | 10 +++------- arch/powerpc/kvm/powerpc.c | 12 ++++++++++++ 2 files changed, 15 insertions(+), 7 deletions(-)
arch/powerpc/kvm/emulate_loadstore.c +3 -7
@@ -73,7 +73,6 @@ int kvmppc_emulate_loadstore(struct kvm_vcpu *vcpu) {u32 inst;enum emulation_result emulated =EMULATE_FAIL ; -int advance =1 ;struct instruction_op op;/* this default type might be overwritten by subcategories */
@@ -98,6 +97,8 @@ int kvmppc_emulate_loadstore(struct kvm_vcpu *vcpu)int type = op.type &INSTR_TYPE_MASK ;int size =GETSIZE (op.type); + vcpu->mmio_is_write =OP_IS_STORE (type); +switch (type) {case LOAD : {int instr_byte_swap = op.type &BYTEREV ;
@@ -355,15 +356,10 @@ int kvmppc_emulate_loadstore(struct kvm_vcpu *vcpu) } } -if (emulated =EMULATE_FAIL ) { - advance =0 ; -kvmppc_core_queue_program (vcpu,0 ); - } -trace_kvm_ppc_instr (inst,kvmppc_get_pc (vcpu), emulated);/* Advance past emulated instruction. */ -if (advance) +if (emulated !=EMULATE_FAIL )kvmppc_set_pc (vcpu,kvmppc_get_pc (vcpu) +4 );return emulated;
arch/powerpc/kvm/powerpc.c +12 -0
@@ -305,10 +305,22 @@ int kvmppc_emulate_mmio(struct kvm_vcpu *vcpu)case EMULATE_FAIL : {u32 last_inst; +ulong store_bit =DSISR_ISSTORE ; +ulong cause =DSISR_BADACCESS ; +#ifdef CONFIG_BOOKE + store_bit =ESR_ST ; + cause =0 ; +#endif kvmppc_get_last_inst (vcpu,INST_GENERIC , &last_inst);pr_info_ratelimited ("KVM: guest access to device memory using unsupported instruction (PID: %d opcode: %#08x)\n" , current->pid, last_inst); + +if (vcpu->mmio_is_write) + cause |= store_bit; + +kvmppc_core_queue_data_storage (vcpu, vcpu->arch.vaddr_accessed, + cause); r =RESUME_GUEST ;break ; }
Signature · 1 line
2.34.1
Re: [PATCH v4 3/5] KVM: PPC: mmio: Reject instructions that access more than mmio.data size
In reply to Fabiano RosasExcerpts from Fabiano Rosas's message of January 22, 2022 8:26 am:
Quoted 21 lines
The MMIO interface between the kernel and userspace uses a structure that supports a maximum of 8-bytes of data. Instructions that access more than that need to be emulated in parts.
We currently don't have generic support for splitting the emulation in parts and each set of instructions needs to be explicitly included.
There's already an error message being printed when a load or store exceeds the mmio.data buffer but we don't fail the emulation until later at
kvmppc_complete_mmio_loadand even then we allow userspace to make a partial copy of the data, which ends up overwriting some fields of the mmio structure.This patch makes the emulation fail earlier at kvmppc_handle_load|store, which will send a Program interrupt to the guest. This is better than allowing the guest to proceed with partial data.
Note that this was caught in a somewhat artificial scenario using quadword instructions (lq/stq), there's no account of an actual guest in the wild running instructions that are not properly emulated.
Quoted 5 lines
(While here, remove the "bad MMIO" messages. The caller already has an error message.)
Signed-off-by Fabiano Rosas <[email protected]>Reviewed-by Alexey Kardashevskiy <[email protected]>
Quoted 50 lines
--- arch/powerpc/kvm/powerpc.c | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-)arch/powerpc/kvm/powerpc.c +5
-11@@ -1114,10 +1114,8 @@ static void kvmppc_complete_mmio_load(struct kvm_vcpu *vcpu)struct kvm_run *run = vcpu->run;u64 gpr; -if (run->mmio.len >sizeof (gpr)) { -printk (KERN_ERR "bad MMIO length: %d\n" , run->mmio.len); +if (run->mmio.len >sizeof (gpr))return ; - }if (!vcpu->arch.mmio_host_swabbed) {switch (run->mmio.len) {@@ -1236,10 +1234,8 @@ static int __kvmppc_handle_load(struct kvm_vcpu *vcpu, host_swabbed = !is_default_endian; } -if (bytes >sizeof (run->mmio.data)) { -printk (KERN_ERR "%s: bad MMIO length: %d\n" , __func__, - run->mmio.len); - } +if (bytes >sizeof (run->mmio.data)) +return EMULATE_FAIL ; run->mmio.phys_addr = vcpu->arch.paddr_accessed; run->mmio.len = bytes;@@ -1325,10 +1321,8 @@ int kvmppc_handle_store(struct kvm_vcpu *vcpu, host_swabbed = !is_default_endian; } -if (bytes >sizeof (run->mmio.data)) { -printk (KERN_ERR "%s: bad MMIO length: %d\n" , __func__, - run->mmio.len); - } +if (bytes >sizeof (run->mmio.data)) +return EMULATE_FAIL ; run->mmio.phys_addr = vcpu->arch.paddr_accessed; run->mmio.len = bytes;Signature · 1 line
2.34.1
Re: [PATCH v4 4/5] KVM: PPC: mmio: Return to guest after emulation failure
In reply to Fabiano RosasExcerpts from Fabiano Rosas's message of January 22, 2022 8:26 am:
Quoted 13 lines
If MMIO emulation fails we don't want to crash the whole guest by returning to userspace.
The original commit
bbf45ba57eae("KVM: ppc: PowerPC 440 KVM implementation") added a todo:/* XXX Deliver Program interrupt to guest. */
and later the commit
d69614a295ae("KVM: PPC: Separate loadstore emulation from priv emulation") added the Program interrupt injection but in another file, so I'm assuming it was missed that this block needed to be altered.
Quoted 4 lines
Also change the message to a ratelimited one since we're letting the guest run and it could flood the host logs.
Signed-off-by Fabiano Rosas <[email protected]>
One small thing...
Quoted 9 lines
--- arch/powerpc/kvm/powerpc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)arch/powerpc/kvm/powerpc.c +0
-0
arch/powerpc/kvm/powerpc.c int kvmppc_emulate_mmio(struct kvm_vcpu *vcpu) · line 311
Quoted 8 lines
arch/powerpc/kvm/powerpc.c +2
-3@@ -307,9 +307,9 @@ int kvmppc_emulate_mmio(struct kvm_vcpu *vcpu)u32 last_inst;kvmppc_get_last_inst (vcpu,INST_GENERIC , &last_inst); -/* XXX Deliver Program interrupt to guest. */ -pr_emerg ("%s: emulation failed (%08x)\n" , __func__, last_inst); - r =RESUME_HOST ; +pr_info_ratelimited ("KVM: guest access to device memory using unsupported instruction (PID: %d opcode: %#08x)\n" , + current->pid, last_inst);
Minor thing but KVM now has some particular printing helpers so I wonder if we should start moving to them in general with our messages.
vcpu_debug_ratelimited() maybe?
Thanks,
Nick
Nicholas Piggin
reviewerRe: [PATCH v4 5/5] KVM: PPC: mmio: Deliver DSI after emulation failure
In reply to Fabiano RosasExcerpts from Fabiano Rosas's message of January 22, 2022 8:26 am:
Quoted 56 lines
MMIO emulation can fail if the guest uses an instruction that we are not prepared to emulate. Since these instructions can be and most likely are valid ones, this is (slightly) closer to an access fault than to an illegal instruction, so deliver a Data Storage interrupt instead of a Program interrupt.
Suggested-by Nicholas Piggin <[email protected]>Signed-off-by Fabiano Rosas <[email protected]>--- arch/powerpc/kvm/emulate_loadstore.c | 10 +++------- arch/powerpc/kvm/powerpc.c | 12 ++++++++++++ 2 files changed, 15 insertions(+), 7 deletions(-)arch/powerpc/kvm/emulate_loadstore.c +3
-7@@ -73,7 +73,6 @@ int kvmppc_emulate_loadstore(struct kvm_vcpu *vcpu) {u32 inst;enum emulation_result emulated =EMULATE_FAIL ; -int advance =1 ;struct instruction_op op;/* this default type might be overwritten by subcategories */ @@ -98,6 +97,8 @@ int kvmppc_emulate_loadstore(struct kvm_vcpu *vcpu)int type = op.type &INSTR_TYPE_MASK ;int size =GETSIZE (op.type); + vcpu->mmio_is_write =OP_IS_STORE (type); +switch (type) {case LOAD : {int instr_byte_swap = op.type &BYTEREV ;@@ -355,15 +356,10 @@ int kvmppc_emulate_loadstore(struct kvm_vcpu *vcpu) } } -if (emulated ==EMULATE_FAIL ) { - advance =0 ; -kvmppc_core_queue_program (vcpu,0 ); - } -trace_kvm_ppc_instr (inst,kvmppc_get_pc (vcpu), emulated);/* Advance past emulated instruction. */ -if (advance) +if (emulated !=EMULATE_FAIL )kvmppc_set_pc (vcpu,kvmppc_get_pc (vcpu) +4 );return emulated;arch/powerpc/kvm/powerpc.c +0
-0
arch/powerpc/kvm/powerpc.c int kvmppc_emulate_mmio(struct kvm_vcpu *vcpu) · line 314
Quoted 10 lines
arch/powerpc/kvm/powerpc.c +6
-0@@ -305,10 +305,22 @@ int kvmppc_emulate_mmio(struct kvm_vcpu *vcpu)case EMULATE_FAIL : {u32 last_inst; +ulong store_bit =DSISR_ISSTORE ; +ulong cause =DSISR_BADACCESS ; +#ifdef CONFIG_BOOKE + store_bit =ESR_ST ; + cause =0 ; +#endif
BookE can not cause a bad page fault in the guest with ESR bits AFAIKS, so it would cause an infinite fault loop here. Maybe stick with the program interrupt for BookE with a comment about that here.
And if it could use if (IS_ENABLED()) would be good?
Otherwise looks good, it should do the right thing on BookS.
Thanks,
Nick
Quoted 16 lines
arch/powerpc/kvm/powerpc.c +6
-0kvmppc_get_last_inst (vcpu,INST_GENERIC , &last_inst);pr_info_ratelimited ("KVM: guest access to device memory using unsupported instruction (PID: %d opcode: %#08x)\n" , current->pid, last_inst); + +if (vcpu->mmio_is_write) + cause |= store_bit; + +kvmppc_core_queue_data_storage (vcpu, vcpu->arch.vaddr_accessed, + cause); r =RESUME_GUEST ;break ; }Signature · 1 line
2.34.1