mirror of
https://github.com/followmsi/android_kernel_google_msm.git
synced 2024-11-06 23:17:41 +00:00
b4433a7cce
To fetch the last instruction we were interrupted on, we enable DR in early exit code, where we are still in a very transitional phase between guest and host state. Most of the time this seemed to work, but another CPU can easily flush our TLB and HTAB which makes us go in the Linux page fault handler which totally breaks because we still use the guest's SLB entries. To work around that, let's introduce a second KVM guest mode that defines that whenever we get a trap, we don't call the Linux handler or go into the KVM exit code, but just jump over the faulting instruction. That way a potentially bad lwz doesn't trigger any faults and we can later on interpret the invalid instruction we fetched as "fetch didn't work". Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com> |
||
|---|---|---|
| .. | ||
| 44x.c | ||
| 44x_emulate.c | ||
| 44x_tlb.c | ||
| 44x_tlb.h | ||
| book3s.c | ||
| book3s_32_mmu.c | ||
| book3s_64_emulate.c | ||
| book3s_64_exports.c | ||
| book3s_64_interrupts.S | ||
| book3s_64_mmu.c | ||
| book3s_64_mmu_host.c | ||
| book3s_64_rmhandlers.S | ||
| book3s_64_slb.S | ||
| booke.c | ||
| booke.h | ||
| booke_emulate.c | ||
| booke_interrupts.S | ||
| e500.c | ||
| e500_emulate.c | ||
| e500_tlb.c | ||
| e500_tlb.h | ||
| emulate.c | ||
| Kconfig | ||
| Makefile | ||
| powerpc.c | ||
| timing.c | ||
| timing.h | ||
| trace.h | ||