kvm: Install specialized interrupt handler
KVM only requires to set the raised IRQ in CPUState and to kick the receiving vcpu if it is remote. Installing a specialized handler allows potential future changes to the TCG code path without risking KVM side effects. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
This commit is contained in:
		
							parent
							
								
									ec6959d046
								
							
						
					
					
						commit
						aa7f74d119
					
				
							
								
								
									
										11
									
								
								kvm-all.c
								
								
								
								
							
							
						
						
									
										11
									
								
								kvm-all.c
								
								
								
								
							| 
						 | 
				
			
			@ -651,6 +651,15 @@ static CPUPhysMemoryClient kvm_cpu_phys_memory_client = {
 | 
			
		|||
    .log_stop = kvm_log_stop,
 | 
			
		||||
};
 | 
			
		||||
 | 
			
		||||
static void kvm_handle_interrupt(CPUState *env, int mask)
 | 
			
		||||
{
 | 
			
		||||
    env->interrupt_request |= mask;
 | 
			
		||||
 | 
			
		||||
    if (!qemu_cpu_is_self(env)) {
 | 
			
		||||
        qemu_cpu_kick(env);
 | 
			
		||||
    }
 | 
			
		||||
}
 | 
			
		||||
 | 
			
		||||
int kvm_init(void)
 | 
			
		||||
{
 | 
			
		||||
    static const char upgrade_note[] =
 | 
			
		||||
| 
						 | 
				
			
			@ -759,6 +768,8 @@ int kvm_init(void)
 | 
			
		|||
 | 
			
		||||
    s->many_ioeventfds = kvm_check_many_ioeventfds();
 | 
			
		||||
 | 
			
		||||
    cpu_interrupt_handler = kvm_handle_interrupt;
 | 
			
		||||
 | 
			
		||||
    return 0;
 | 
			
		||||
 | 
			
		||||
err:
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue