[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism
Hi, I (Doi.Tsunehisa) said: > Hmm.. Current implement needs the GSI for platform-pci to follow > status of virtual IOSAPIC in hypervisor side. But, it's not certain > value from virtual IOSAPIC at calling set_callback_irq hypercall. > > I'll be thinking more... I've investigated it, but I couldn't find the method to get GSI of platform-pci for PV-on-HVM driver. There is convert functions like isa_irq_to_vector() in linux kernel source. [arch/ia64/kernel/apci.c] int acpi_gsi_to_irq(u32 gsi, unsigned int *irq) [arch/ia64/kernel/iosapic.c] inline int gsi_to_vector (unsigned int gsi) But, these functions are not EXPORT_SYMBOLE, thus we can't use them for kernel module. So, I think that.. * Hypervisor becomes to be able to use both GSI and Vector for callback irq. - For example, if it is normal value, HV accepts it as GSI. If it is value which is set MSB, HV accepts it as Vector. * If hypervisor gets Vector as callback irq, hypervisor finds the GSI for the pseudo device from virtual interrupt controller setting. What do you think about this method ? Thanks, - Tsunehisa Doi _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |