summaryrefslogtreecommitdiffstats
path: root/arch/mips/kvm/emulate.c
diff options
context:
space:
mode:
authorJames Hogan <james.hogan@imgtec.com>2016-11-16 23:48:56 +0000
committerJames Hogan <james.hogan@imgtec.com>2017-02-03 15:20:44 +0000
commit1581ff3dbf698abba00f39039cc5bd854400b664 (patch)
tree8fe03928b9d70e5349a3427024c2eb5caee1cc64 /arch/mips/kvm/emulate.c
parenta60b8438bdba4a4b77c90b6c1b22804150b4f244 (diff)
downloadtalos-op-linux-1581ff3dbf698abba00f39039cc5bd854400b664.tar.gz
talos-op-linux-1581ff3dbf698abba00f39039cc5bd854400b664.zip
KVM: MIPS/MMU: Move preempt/ASID handling to implementation
The MIPS KVM host and guest GVA ASIDs may need regenerating when scheduling a process in guest context, which is done from the kvm_arch_vcpu_load() / kvm_arch_vcpu_put() functions in mmu.c. However this is a fairly implementation specific detail. VZ for example may use GuestIDs instead of normal ASIDs to distinguish mappings belonging to different guests, and even on VZ without GuestID the root TLB will be used differently to trap & emulate. Trap & emulate GVA ASIDs only relate to the user part of the full address space, so can be left active during guest exit handling (guest context) to allow guest instructions to be easily read and translated. VZ root ASIDs however are for GPA mappings so can't be left active during normal kernel code. They also aren't useful for accessing guest virtual memory, and we should have CP0_BadInstr[P] registers available to provide encodings of trapping guest instructions anyway. Therefore move the ASID preemption handling into the implementation callback. Signed-off-by: James Hogan <james.hogan@imgtec.com> Cc: Paolo Bonzini <pbonzini@redhat.com> Cc: "Radim Krčmář" <rkrcmar@redhat.com> Cc: Ralf Baechle <ralf@linux-mips.org> Cc: linux-mips@linux-mips.org Cc: kvm@vger.kernel.org
Diffstat (limited to 'arch/mips/kvm/emulate.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud