target/arm: kvm: Support for KVM DABT with no valid ISS
v5 cover target/arm: kvm: Support for KVM DABT with no valid ISS
Some of the ARMv7 & ARMv8 load/store instructions might trigger a data abort exception with no valid ISS info to be decoded. The lack of decode info makes it at least tricky to emulate the instruction which is one of the (many) reasons why KVM will not even try to do so.
So far, if a guest made an attempt to access memory outside the memory slot, KVM reported vague ENOSYS. As a result QEMU exited with no useful information being provided or even a clue on what has just happened.
ARM KVM introduced support for notifying of an attempt to execute an instruction that resulted in dabt with no valid ISS decoding info. This still leaves QEMU to handle the case, but at least now it gives more control and a start point for more meaningful handling of such cases.
This patchset relies on KVM to insert the external data abort into the guest.
Thanks for all the input on the previous version!
----------------------
v5:
- Drop syncing vcpu regs in favour of calling kvm_put_vcpu_events directly
- Fix decoding DFSC for LPAE case
- Add/clarify comments
- Switch to reporting error case failure when enabling the cap
v4:
- Removing one of the patches as it is being picked-up separately target/arm: kvm: Inject events at the last stage of sync
- Moving handling KVM issue to a separate patch
- Minor changes wrt the review comments
v3:
- Fix setting KVM cap per vm not per vcpu
- Simplifying the handler to bare minimum with no default logging to address the potential risk of overflooding the host (adding support for rate limiting the logs turned out to be bit too invasive to justify the little add-on value from logs in this particular case)
- Adding handling KVM bug (for small range of affected kernels):
little bit of trade-off between what's reasonable and what's effective:
aborting qemu when running on buggy host kernel
v2:
- Improving/re-phrasing messaging
- Dropping messing around with forced sync (@see [PATCH v2 1/2]) and PC alignment
Beata Michalska (2):
target/arm: kvm: Handle DABT with no valid ISS target/arm: kvm: Handle misconfigured dabt injection
target/arm/cpu.h | 3 ++ target/arm/kvm.c | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++- target/arm/kvm32.c | 35 ++++++++++++++++++++ target/arm/kvm64.c | 49 ++++++++++++++++++++++++++++ target/arm/kvm_arm.h | 21 ++++++++++++ 5 files changed, 199 insertions(+), 1 deletion(-)
Signature · 6 lines
2.7.4 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 1/2 target/arm: kvm: Handle DABT with no valid ISS
On ARMv7 & ARMv8 some load/store instructions might trigger a data abort exception with no valid ISS info to be decoded. The lack of decode info makes it at least tricky to emulate those instruction which is one of the (many) reasons why KVM will not even try to do so.
Add support for handling those by requesting KVM to inject external dabt into the quest.
--- target/arm/cpu.h | 2 ++ target/arm/kvm.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++- target/arm/kvm_arm.h | 11 +++++++++ 3 files changed, 76 insertions(+), 1 deletion(-)
target/arm/cpu.h +2 -0
@@ -570,6 +570,8 @@ typedef struct CPUARMState {uint64_t esr; } serror; +uint8_t ext_dabt_pending;/* Request for injecting ext DABT */ +/* State of our input IRQ/FIQ/VIRQ/VFIQ lines */ uint32_t irq_line_state;
target/arm/kvm.c +63 -1
94 lines not on this page · raw message
target/arm/kvm_arm.h +11 -0
@@ -453,6 +453,17 @@ struct kvm_guest_debug_arch;void kvm_arm_copy_hw_debug_data (struct kvm_guest_debug_arch *ptr);/** +* kvm_arm_handle_dabt_nisv: +* @cs: CPUState +* @esr_iss: ISS encoding (limited) for the exception from Data Abort +* ISV bit set to '0b0' -> no valid instruction syndrome +* @fault_ipa: faulting address for the synch data abort +* +* Returns: 0 if the exception has been handled, < 0 otherwise +*/ +int kvm_arm_handle_dabt_nisv (CPUState *cs,uint64_t esr_iss, +uint64_t fault_ipa); +/** * its_class_name: * * Return the ITS class name to use depending on whether KVM acceleration
Signature · 6 lines
2.7.4 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Re: [PATCH v5 1/2] target/arm: kvm: Handle DABT with no valid ISS
Hi Beata,
I see Peter just picked this up, so I'm a bit late getting to it. I do have a couple comments below though.
Thanks,
drew
Quoted 89 lines · Beata Michalska
On ARMv7 & ARMv8 some load/store instructions might trigger a data abort exception with no valid ISS info to be decoded. The lack of decode info makes it at least tricky to emulate those instruction which is one of the (many) reasons why KVM will not even try to do so.
Add support for handling those by requesting KVM to inject external dabt into the quest.
Signed-off-by Beata Michalska <[email protected]>--- target/arm/cpu.h | 2 ++ target/arm/kvm.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++- target/arm/kvm_arm.h | 11 +++++++++ 3 files changed, 76 insertions(+), 1 deletion(-)target/arm/cpu.h +2
-0@@ -570,6 +570,8 @@ typedef struct CPUARMState {uint64_t esr; } serror; +uint8_t ext_dabt_pending;/* Request for injecting ext DABT */ +/* State of our input IRQ/FIQ/VIRQ/VFIQ lines */ uint32_t irq_line_state;target/arm/kvm.c +24
-1@@ -39,6 +39,7 @@ const KVMCapabilityInfo kvm_arch_required_capabilities[] = {static bool cap_has_mp_state;static bool cap_has_inject_serror_esr; +static bool cap_has_inject_ext_dabt;static ARMHostCPUFeatures arm_host_cpu_features;@@ -244,6 +245,16 @@ int kvm_arch_init(MachineState *ms, KVMState *s) ret = -EINVAL ; } +if (kvm_check_extension (s,KVM_CAP_ARM_NISV_TO_USER )) { +if (kvm_vm_enable_cap (s,KVM_CAP_ARM_NISV_TO_USER ,0 )) { +error_report ("Failed to enable KVM_CAP_ARM_NISV_TO_USER cap" ); + }else { +/* Set status for supporting the external dabt injection */ + cap_has_inject_ext_dabt =kvm_check_extension (s, +KVM_CAP_ARM_INJECT_EXT_DABT ); + } + } +return ret; }@@ -703,9 +714,16 @@ int kvm_put_vcpu_events(ARMCPU *cpu) events.exception.serror_esr = env->serror.esr; } +if (cap_has_inject_ext_dabt) { + events.exception.ext_dabt_pending = env->ext_dabt_pending; + } + ret =kvm_vcpu_ioctl (CPU (cpu),KVM_SET_VCPU_EVENTS , &events);if (ret) {error_report ("failed to put vcpu events" ); + }else { +/* Clear instantly if the call was successful */ + env->ext_dabt_pending =0 ; }return ret;@@ -819,7 +837,12 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run) ret =EXCP_DEBUG ; }/* otherwise return to guest */ break ; -default : +case KVM_EXIT_ARM_NISV : +/* External DABT with no valid iss to decode */ + ret =kvm_arm_handle_dabt_nisv (cs, run->arm_nisv.esr_iss, + run->arm_nisv.fault_ipa); +break ; +default :qemu_log_mask (LOG_UNIMP ,"%s: un-handled exit reason %d\n" , __func__, run->exit_reason);break ;
target/arm/kvm.c int kvm_arch_msi_data_to_gsi(uint32_t data) · line 983
Quoted 6 lines
target/arm/kvm.c +3
-0@@ -955,3 +978,42 @@ int kvm_arch_msi_data_to_gsi(uint32_t data) {return (data -32 ) &0xffff ; } + +int kvm_arm_handle_dabt_nisv (CPUState *cs,uint64_t esr_iss, +uint64_t fault_ipa)
This function could be static since it's in the same file as its one and only caller.
Quoted 18 lines
target/arm/kvm.c +18
-0+{ +ARMCPU *cpu =ARM_CPU (cs); +CPUARMState *env = &cpu->env; + +/* +* ISS [23:14] is invalid so there is a limited info +* on what has just happened so the only *useful* thing that can +* be retrieved from ISS is WnR & DFSC (though in some cases WnR +* might be less of a value as well) +*/ + +/* +* Request KVM to inject the external data abort into the guest +* by setting a pending exception on the affected vcpu. +*/ +if (cap_has_inject_ext_dabt) { +/* Set pending exception */ + env->ext_dabt_pending =1 ;
target/arm/kvm.c int kvm_arch_msi_data_to_gsi(uint32_t data) · line 1011
Quoted 10 lines
target/arm/kvm.c +10
-0+/* +* Even though at this point, the vcpu regs are out of sync, +* directly calling the KVM_SET_VCPU_EVENTS ioctl without +* explicitly synchronizing those, is enough and it also avoids +* overwriting changes done by KVM. +* The vcpu is not being marked as 'dirty' as all the changes +* needed to inject the abort are being handled by KVM only +* and there is no need for syncing either way +*/ +return kvm_put_vcpu_events (cpu);
This looks fragile. What if we change kvm_put_vcpu_events() in a way that requires CPU synchronization? Or, what if we change something else that results in the VCPU getting flagged as dirty before finishing this run loop, and then we end up calling kvm_put_vcpu_events() twice, possibly causing some other problem?
I think I'd prefer seeing the KVM_SET_VCPU_EVENTS ioctl get called directly from here with the events set to only inject the dabt, as we know that will be handled immediately and doesn't require any CPU synchronization.
Thanks,
drew
Quoted 34 lines
target/arm/kvm.c +8
-0+ }else { +error_report ("Data abort exception triggered by guest memory access " +"at physical address: 0x" TARGET_FMT_lx, + (target_ulong )fault_ipa); +error_printf ("KVM unable to emulate faulting instruction.\n" ); +return -1 ; + } +}target/arm/kvm_arm.h +11
-0@@ -453,6 +453,17 @@ struct kvm_guest_debug_arch;void kvm_arm_copy_hw_debug_data (struct kvm_guest_debug_arch *ptr);/** +* kvm_arm_handle_dabt_nisv: +* @cs: CPUState +* @esr_iss: ISS encoding (limited) for the exception from Data Abort +* ISV bit set to '0b0' -> no valid instruction syndrome +* @fault_ipa: faulting address for the synch data abort +* +* Returns: 0 if the exception has been handled, < 0 otherwise +*/ +int kvm_arm_handle_dabt_nisv (CPUState *cs,uint64_t esr_iss, +uint64_t fault_ipa); +/** * its_class_name: * * Return the ITS class name to use depending on whether KVM acceleration Signature · 1 line
2.7.4
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Re: [PATCH v5 1/2] target/arm: kvm: Handle DABT with no valid ISS
Quoted 5 lines · Andrew Jones
Hi Beata,
I see Peter just picked this up, so I'm a bit late getting to it. I do have a couple comments below though.
I'll drop it from my queue again for the moment, then.
thanks
-- PMM
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Re: [PATCH v5 1/2] target/arm: kvm: Handle DABT with no valid ISS
In reply to Andrew JonesHi Andrew,
Thanks for the feedback.
Quoted 100 lines · Andrew Jones
Hi Beata,
I see Peter just picked this up, so I'm a bit late getting to it. I do have a couple comments below though.
Thanks,
drewQuoted 90 lines · Beata Michalska
On ARMv7 & ARMv8 some load/store instructions might trigger a data abort exception with no valid ISS info to be decoded. The lack of decode info makes it at least tricky to emulate those instruction which is one of the (many) reasons why KVM will not even try to do so.
Add support for handling those by requesting KVM to inject external dabt into the quest.
Signed-off-by Beata Michalska <[email protected]>--- target/arm/cpu.h | 2 ++ target/arm/kvm.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++- target/arm/kvm_arm.h | 11 +++++++++ 3 files changed, 76 insertions(+), 1 deletion(-)target/arm/cpu.h +2
-0@@ -570,6 +570,8 @@ typedef struct CPUARMState {uint64_t esr; } serror; +uint8_t ext_dabt_pending;/* Request for injecting ext DABT */ +/* State of our input IRQ/FIQ/VIRQ/VFIQ lines */ uint32_t irq_line_state;target/arm/kvm.c +24
-1@@ -39,6 +39,7 @@ const KVMCapabilityInfo kvm_arch_required_capabilities[] = {static bool cap_has_mp_state;static bool cap_has_inject_serror_esr; +static bool cap_has_inject_ext_dabt;static ARMHostCPUFeatures arm_host_cpu_features;@@ -244,6 +245,16 @@ int kvm_arch_init(MachineState *ms, KVMState *s) ret = -EINVAL ; } +if (kvm_check_extension (s,KVM_CAP_ARM_NISV_TO_USER )) { +if (kvm_vm_enable_cap (s,KVM_CAP_ARM_NISV_TO_USER ,0 )) { +error_report ("Failed to enable KVM_CAP_ARM_NISV_TO_USER cap" ); + }else { +/* Set status for supporting the external dabt injection */ + cap_has_inject_ext_dabt =kvm_check_extension (s, +KVM_CAP_ARM_INJECT_EXT_DABT ); + } + } +return ret; }@@ -703,9 +714,16 @@ int kvm_put_vcpu_events(ARMCPU *cpu) events.exception.serror_esr = env->serror.esr; } +if (cap_has_inject_ext_dabt) { + events.exception.ext_dabt_pending = env->ext_dabt_pending; + } + ret =kvm_vcpu_ioctl (CPU (cpu),KVM_SET_VCPU_EVENTS , &events);if (ret) {error_report ("failed to put vcpu events" ); + }else { +/* Clear instantly if the call was successful */ + env->ext_dabt_pending =0 ; }return ret;@@ -819,7 +837,12 @@ int kvm_arch_handle_exit(CPUState *cs, struct kvm_run *run) ret =EXCP_DEBUG ; }/* otherwise return to guest */ break ; -default : +case KVM_EXIT_ARM_NISV : +/* External DABT with no valid iss to decode */ + ret =kvm_arm_handle_dabt_nisv (cs, run->arm_nisv.esr_iss, + run->arm_nisv.fault_ipa); +break ; +default :qemu_log_mask (LOG_UNIMP ,"%s: un-handled exit reason %d\n" , __func__, run->exit_reason);break ;@@ -955,3 +978,42 @@ int kvm_arch_msi_data_to_gsi(uint32_t data) {
Quoted 9 lines
target/arm/kvm.c int kvm_arch_msi_data_to_gsi(uint32_t data) · line 983
Quoted 5 lines
target/arm/kvm.c +3
-0return (data -32 ) &0xffff ; } + +int kvm_arm_handle_dabt_nisv (CPUState *cs,uint64_t esr_iss, +uint64_t fault_ipa)This function could be static since it's in the same file as its one and only caller.
Right. Will do.
Quoted 35 lines
Quoted 18 lines
target/arm/kvm.c +18
-0+{ +ARMCPU *cpu =ARM_CPU (cs); +CPUARMState *env = &cpu->env; + +/* +* ISS [23:14] is invalid so there is a limited info +* on what has just happened so the only *useful* thing that can +* be retrieved from ISS is WnR & DFSC (though in some cases WnR +* might be less of a value as well) +*/ + +/* +* Request KVM to inject the external data abort into the guest +* by setting a pending exception on the affected vcpu. +*/ +if (cap_has_inject_ext_dabt) { +/* Set pending exception */ + env->ext_dabt_pending =1 ;target/arm/kvm.c int kvm_arch_msi_data_to_gsi(uint32_t data) · line 1011
Quoted 10 lines
target/arm/kvm.c +10
-0+/* +* Even though at this point, the vcpu regs are out of sync, +* directly calling the KVM_SET_VCPU_EVENTS ioctl without +* explicitly synchronizing those, is enough and it also avoids +* overwriting changes done by KVM. +* The vcpu is not being marked as 'dirty' as all the changes +* needed to inject the abort are being handled by KVM only +* and there is no need for syncing either way +*/ +return kvm_put_vcpu_events (cpu);This looks fragile. What if we change
kvm_put_vcpu_events()in a way that requires CPU synchronization? Or, what if we change something else that results in the VCPU getting flagged as dirty before finishing this run loop, and then we end up callingkvm_put_vcpu_events()twice, possibly causing some other problem?
Quoted 5 lines
I think I'd prefer seeing the
KVM_SET_VCPU_EVENTSioctl get called directly from here with the events set to only inject the dabt, as we know that will be handled immediately and doesn't require any CPU synchronization.
It might be 'fragile' though I would expect any changes to kvm_put_vcpu_events revisit all users, but I have no objections to calling ioctl directly here if that's
the prefered way.
Will try to push the changes sometime later this week.
Thanks again for the review.
BR
Beata
Quoted 29 lines
Thanks,
drewQuoted 26 lines
target/arm/kvm.c +8
-0+ }else { +error_report ("Data abort exception triggered by guest memory access " +"at physical address: 0x" TARGET_FMT_lx, + (target_ulong )fault_ipa); +error_printf ("KVM unable to emulate faulting instruction.\n" ); +return -1 ; + } +}target/arm/kvm_arm.h +10
-0@@ -453,6 +453,17 @@ struct kvm_guest_debug_arch;void kvm_arm_copy_hw_debug_data (struct kvm_guest_debug_arch *ptr);/** +* kvm_arm_handle_dabt_nisv: +* @cs: CPUState +* @esr_iss: ISS encoding (limited) for the exception from Data Abort +* ISV bit set to '0b0' -> no valid instruction syndrome +* @fault_ipa: faulting address for the synch data abort +* +* Returns: 0 if the exception has been handled, < 0 otherwise +*/ +int kvm_arm_handle_dabt_nisv (CPUState *cs,uint64_t esr_iss, +uint64_t fault_ipa);
Quoted 9 lines
Quoted 8 lines
target/arm/kvm_arm.h +1
-1+/** * its_class_name: * * Return the ITS class name to use depending on whether KVM acceleration -- 2.7.4
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
PATCH v5 2/2 target/arm: kvm: Handle misconfigured dabt injection
In reply to Beata MichalskaInjecting external data abort through KVM might trigger an issue on kernels that do not get updated to include the KVM fix. For those and aarch32 guests, the injected abort gets misconfigured to be an implementation defined exception. This leads to the guest repeatedly re-running the faulting instruction.
Add support for handling that case.
[
Fixed-by: 018f22f95e8a
('KVM: arm: Fix DFSR setting for non-LPAE aarch32 guests')
Fixed-by: 21aecdbd7f3a
('KVM: arm: Make inject_abt32() inject an external abort instead')
]
--- target/arm/cpu.h | 1 + target/arm/kvm.c | 30 +++++++++++++++++++++++++++++- target/arm/kvm32.c | 34 ++++++++++++++++++++++++++++++++++ target/arm/kvm64.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ target/arm/kvm_arm.h | 10 ++++++++++ 5 files changed, 123 insertions(+), 1 deletion(-)
target/arm/cpu.h +1 -0
@@ -571,6 +571,7 @@ typedef struct CPUARMState { } serror;uint8_t ext_dabt_pending;/* Request for injecting ext DABT */ +uint8_t ext_dabt_raised;/* Tracking/verifying injection of ext DABT */ /* State of our input IRQ/FIQ/VIRQ/VFIQ lines */ uint32_t irq_line_state;
target/arm/kvm.c +29 -1
@@ -721,7 +721,12 @@ int kvm_put_vcpu_events(ARMCPU *cpu) ret =kvm_vcpu_ioctl (CPU (cpu),KVM_SET_VCPU_EVENTS , &events);if (ret) {error_report ("failed to put vcpu events" ); - }else { + }else if (env->ext_dabt_pending) { +/* +* Mark that the external DABT has been injected, +* if one has been requested +*/ + env->ext_dabt_raised = env->ext_dabt_pending;/* Clear instantly if the call was successful */ env->ext_dabt_pending =0 ; }
@@ -755,6 +760,29 @@ int kvm_get_vcpu_events(ARMCPU *cpu)void kvm_arch_pre_run (CPUState *cs,struct kvm_run *run) { +ARMCPU *cpu =ARM_CPU (cs); +CPUARMState *env = &cpu->env; + +if (unlikely (env->ext_dabt_raised)) { +/* +* Verifying that the ext DABT has been properly injected, +* otherwise risking indefinitely re-running the faulting instruction +* Covering a very narrow case for kernels 5.5..5.5.4 +* when injected abort was misconfigured to be +* an IMPLEMENTATION DEFINED exception (for 32-bit EL1) +*/ +if (!arm_feature (env,ARM_FEATURE_AARCH64 ) && +unlikely (!kvm_arm_verify_ext_dabt_pending (cs))) { + +error_report ("Data abort exception with no valid ISS generated by " +"guest memory access. KVM unable to emulate faulting " +"instruction. Failed to inject an external data abort " +"into the guest." ); +abort (); + } +/* Clear the status */ + env->ext_dabt_raised =0 ; + } }MemTxAttrs kvm_arch_post_run (CPUState *cs,struct kvm_run *run)
target/arm/kvm32.c +34 -0
@@ -559,3 +559,37 @@ void kvm_arm_pmu_init(CPUState *cs) {qemu_log_mask (LOG_UNIMP ,"%s: not implemented\n" , __func__); } + +#define ARM_REG_DFSR ARM_CP15_REG32(0, 5, 0, 0) +#define ARM_REG_TTBCR ARM_CP15_REG32(0, 2, 0, 2) +/* +*DFSR: +* TTBCR.EAE == 0 +* FS[4] - DFSR[10] +* FS[3:0] - DFSR[3:0] +* TTBCR.EAE == 1 +* FS, bits [5:0] +*/ +#define DFSR_FSC (lpae, v) \ + ((lpae) ? ((v) & 0x3F) : (((v) >> 6) | ((v) & 0x1F))) + +#define DFSC_EXTABT (lpae) ((lpae) ? 0x10 : 0x08) + +bool kvm_arm_verify_ext_dabt_pending (CPUState *cs) +{ +uint32_t dfsr_val; + +if (!kvm_get_one_reg (cs,ARM_REG_DFSR , &dfsr_val)) { +ARMCPU *cpu =ARM_CPU (cs); +CPUARMState *env = &cpu->env; +uint32_t ttbcr; +int lpae =0 ; + +if (!kvm_get_one_reg (cs,ARM_REG_TTBCR , &ttbcr)) { + lpae =arm_feature (env,ARM_FEATURE_LPAE ) && (ttbcr &TTBCR_EAE ); + } +/* The verification is based on FS filed of the DFSR reg only*/ +return (DFSR_FSC (lpae, dfsr_val) ==DFSC_EXTABT (lpae)); + } +return false; +}
target/arm/kvm64.c +49 -0
52 lines not on this page · raw message
target/arm/kvm_arm.h +10 -0
@@ -464,6 +464,16 @@ void kvm_arm_copy_hw_debug_data(struct kvm_guest_debug_arch *ptr);int kvm_arm_handle_dabt_nisv (CPUState *cs,uint64_t esr_iss,uint64_t fault_ipa);/** +* kvm_arm_verify_ext_dabt_pending: +* @cs: CPUState +* +* Verify the fault status code wrt the Ext DABT injection +* +* Returns: true if the fault status code is as expected, false otherwise +*/ +bool kvm_arm_verify_ext_dabt_pending (CPUState *cs); + +/** * its_class_name: * * Return the ITS class name to use depending on whether KVM acceleration
Signature · 6 lines
2.7.4 _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
Peter Maydell
AppliedQuoted 15 lines · Beata Michalska
Some of the ARMv7 & ARMv8 load/store instructions might trigger a data abort exception with no valid ISS info to be decoded. The lack of decode info makes it at least tricky to emulate the instruction which is one of the (many) reasons why KVM will not even try to do so.
So far, if a guest made an attempt to access memory outside the memory slot, KVM reported vague ENOSYS. As a result QEMU exited with no useful information being provided or even a clue on what has just happened.
ARM KVM introduced support for notifying of an attempt to execute an instruction that resulted in dabt with no valid ISS decoding info. This still leaves QEMU to handle the case, but at least now it gives more control and a start point for more meaningful handling of such cases.
Quoted 4 lines
This patchset relies on KVM to insert the external data abort into the guest.
Thanks for all the input on the previous version!
Applied to target-arm.next, thanks.
-- PMM
_______________________________________________
kvmarm mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm