x86/kvm/x86.c

510  * Handle a fault on a hardware virtualization (VMX or SVM) instruction.
512  * Hardware virtualization extension instructions may fault if a reboot turns
514  * fault we just panic; during reboot instead the instruction is ignored.
560 	 * #DBs can be trap-like or fault-like, the caller must check other CPU
561 	 * state, e.g. DR6, to determine whether a #DB is a trap or fault.
572 	/* Reserved exceptions will result in fault */
710 		/* triple fault -> shutdown */
782 void kvm_inject_page_fault(struct kvm_vcpu *vcpu, struct x86_exception *fault)
790 	if (is_guest_mode(vcpu) && fault->async_page_fault)
792 					   true, fault->error_code,
793 					   true, fault->address);
795 		kvm_queue_exception_e_p(vcpu, PF_VECTOR, fault->error_code,
796 					fault->address);
800 				    struct x86_exception *fault)
803 	WARN_ON_ONCE(fault->vector != PF_VECTOR);
805 	fault_mmu = fault->nested_page_fault ? vcpu->arch.mmu :
810 	 * else the access will fault indefinitely (and to emulate hardware).
812 	if ((fault->error_code & PFERR_PRESENT_MASK) &&
813 	    !(fault->error_code & PFERR_RSVD_MASK))
814 		kvm_mmu_invalidate_addr(vcpu, fault_mmu, fault->address,
817 	fault_mmu->inject_page_fault(vcpu, fault);
1840  * Write @data into the MSR specified by @index.  Select MSR specific fault
1920  * Read the MSR specified by @index into @data.  Select MSR specific fault
2042 	/* Check if the user wanted to know about this MSR fault */
3933 			/* R bits, i.e. writes are ignored, but don't fault. */
8859 		 * it to generate fault.
8895 	 * result in the instruction taking a !PRESENT page fault and thus put
8897 	 * a SPTE and write-protect the gfn to resolve the !PRESENT fault, and
8922 	 * last retried eip and the last fault address, if we meet the eip
9119  * (and wrong) when emulating on an intercepted fault-like exception[*], as
9166 		 * are fault-like and are higher priority than any faults on
9301 		 * Note, EXCPT_DB is assumed to be fault-like as the emulator
9303 		 * of which are fault-like.
10337  * instruction (in the guest).  E.g. if a page fault (#PF, #NPF, EPT violation)
10374 	 * determined the fault belongs to the guest and queues the exception
10382 	 * And while fault-like exceptions, e.g. #GP and #PF, are the lowest
10385 	 * Thus a pending fault-like exception means the fault occurred on the
10442 		 * fault-like.  They do _not_ set RF, a la code breakpoints.
10539 	 * vCPU into an infinite loop.  Triple fault can be queued when running
13408 	struct x86_exception fault;
13415 		fault.vector = PF_VECTOR;
13416 		fault.error_code_valid = true;
13417 		fault.error_code = 0;
13418 		fault.nested_page_fault = false;
13419 		fault.address = work->arch.token;
13420 		fault.async_page_fault = true;
13421 		kvm_inject_page_fault(vcpu, &fault);
13426 		 * page fault, but putting the guest in an artificial halt state
13430 		 * fault is retried, hopefully the page will be ready in the host.
13632 	struct x86_exception fault;
13637 	    mmu->gva_to_gpa(vcpu, mmu, gva, access, &fault) != INVALID_GPA) {
13643 		fault.vector = PF_VECTOR;
13644 		fault.error_code_valid = true;
13645 		fault.error_code = error_code;
13646 		fault.nested_page_fault = false;
13647 		fault.address = gva;
13648 		fault.async_page_fault = false;
13650 	vcpu->arch.walk_mmu->inject_page_fault(vcpu, &fault);