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

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


  • To: <Doi.Tsunehisa@xxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Wed, 6 Dec 2006 13:17:31 +0800
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 05 Dec 2006 21:21:06 -0800
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AccY5EUDPKjvZoP4QMKYywRSN5CIxgAECxcw
  • Thread-topic: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism

Doi.Tsunehisa@xxxxxxxxxxxxxx write on 2006年12月6日 10:56:
> Hi Anthony,

>   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?


Thanks,
--Anthony.



> 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®.