[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism
Doi.Tsunehisa@xxxxxxxxxxxxxx write on 2006年12月6日 17:20: > > Sorry, I don't know this issue for detail. I think that the guest > OS sets interrupt mask register of VIOSAPIC until setting own vector. > I assume that the guest OS might change the vector for such hardware > in active state. > Hi Doi, This issue is from you, guest linux uses vector, while there is no function like vector_to_irq. Because the hardware irq for platform_pci will not be changes. We can call set_callback_irq with hardware irq inside Qemu, Thus, platform_pci driver don't need to call set_callback_irq. Yes, guest OS can change the vector for platform_pci hardware irq, But the hardware irq is not changed, and HV know how to translate hardware irq to level through VIOSAPIC, And HV still use viosapic_set_irq to pend platform_pci interrupt. So I think it works. --Anthony > Thank you. > > - 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 |