Re: [PATCH 9/13] KVM: define exit handlers

[Avi Kivity <avi@qumranet.com>]

Anthony Liguori wrote:
> Avi Kivity wrote:
>> +static int handle_external_interrupt(struct kvm_vcpu *vcpu,
>> +                     struct kvm_run *kvm_run)
>> +{
>> +    ++kvm_stat.irq_exits;
>> +    return 1;
>> +}
>>   
>
> Don't you need to propagate the interrupt here?  In Xen, we inject the 
> interrupt using the IDT.  As a module, you don't have access to that.  
> However, you could use a software interrupt to reraise it.

We don't set VM_EXIT_ACK_INTR_ON_EXIT on the VM exit controls, so when 
an external interrupt is received, it isn't acked and remains in the 
(real) apic.  We do set the guest to exit on external interrupt, so the 
guest exits and when it reaches the popf in kvm_dev_ioctl_run() the 
interrupt is dispatched naturally using the host IDT.

[Xen can't do that since it must handle some of the interrupts itself]

>
> I got your code running this afternoon (it's quite cool) but I noticed 
> a ton of "rtc: lost some interrupts at 1024Hz." messages which leads 
> me to believe.. you're dropping interrupts :-)  

That's in the guest, right?  I get those too.  Probably due to to our 
shadow mmu suckiness or a problem with the virtual apic.  We are 
addressing both.

> Things seem to hang trying to bring up eth0 in the guest.

Hmm.  What guest are you using?  Are you using dhcp? ipv6? qemu user net 
or tap?


>
> BTW, have you setup a mailing list yet?

I have a project queued on sourceforge, should be up in a day or two.

Thanks for testing!

-- 
error compiling committee.c: too many arguments to function