[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism



Hi Anthony,

You (anthony.xu) said:
>>   We had implemented older PV-on-HVM with the method like this.
>> But, we found the issue that interrupt was injected during interrupt
>> masking of VIOSAPIC. So we changed to implement it.
>> 
>>   In this time, we have to implement it that interrupt injection
>> follows VIOSAPIC status. Thus, HV should look for VIOSAPIC, I think.
>> 
> 
> Hi Dio,
> 
> If platform_pci conforms to IOSAPIC, I has below suggestion.
> 
> 1. platform_pci calls set_callback_irq using vector,
> 
> 2. since HVMOP_set_param hypercall is arch-specific, HV can translate
>    vector to irq, ( VIOSAPIC can provide this interface),
> 
> 3. if there is event to besent, HV calls viosapic_set_irq to pend
>    interrupt.
> 
> What's your opinion about this?

  Basically, I agree your suggestion in Linux guest. But in Windows
guest, PV-driver can't get vector with own driver interface. So, I
think that HV has to have the interfaces about callback irq in both
cases, using GSI and Vector.

  BTW, in my experience, the vector doesn't set to VIOSAPIC at
HVMOP_set_param hypercall. Thus I'll implement to find the GSI at
interrupt injection phase.

Thanks,
- Tsunehisa Doi

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.