Lines Matching full:interrupts

2141  * other cases which must be called after interrupts are enabled on the host.
8573 	 * an sti; sti; sequence only disable interrupts for the first  in toggle_interruptibility()
9212 		 * For STI, interrupts are shadowed; so KVM_REQ_EVENT will  in x86_emulate_instruction()
10187  * interrupts, KVM still honors instruction boundaries in most scenarios.
10232 	 * "Injected" interrupts can also collide with pending exceptions if  in kvm_check_and_inject_events()
10236 	 * exceptions, e.g. most #DBs, have higher priority than interrupts.  in kvm_check_and_inject_events()
10239 	 * execution, and interrupts are recognized at instruction boundaries.  in kvm_check_and_inject_events()
10319 	/* Don't inject interrupts if the user asked to avoid doing so */  in kvm_check_and_inject_events()
10491 	 * When APICv gets disabled, we may still have injected interrupts  in __kvm_vcpu_update_apicv()
10515 	 * this case so that KVM can use the AVIC doorbell to inject interrupts  in kvm_vcpu_update_apicv()
10882 	 * Process pending posted interrupts to handle the case where the  in vcpu_enter_guest()
10886 	 * i.e. they can post interrupts even if APICv is temporarily disabled.  in vcpu_enter_guest()
11023 	 * Consume any pending interrupts, including the possible source of  in vcpu_enter_guest()
11026 	 * interrupts on processors that implement an interrupt shadow, the  in vcpu_enter_guest()
13409 	 * If interrupts are off we cannot even use an artificial  in kvm_can_do_async_pf()