[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 14:56:54 +0800
  • Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 05 Dec 2006 22:56:50 -0800
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AccY/5NW05qqQwGGRweh/+RrSJtcKwAAED8A
  • Thread-topic: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism

Doi.Tsunehisa@xxxxxxxxxxxxxx write on 2006年12月6日 14:27:
> Hi Anthony,
> 
>   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.


In this case,

Can we call set_callback_irq with hardware irq inside Qemu rather than
platform_pci, just after platform_pci is initiated in Qemu?

It seems resolve this issue.

What's your opinion about this?

BTW I found we use viosapic_set_irq to pend the platform_pci interrupt.
It may be no correct, because platform_pic interrupt is like "edge" triggered 
interrupt, but VIOSAPIC for this irq is programmed to a "level" triggered due
to it is PCI device.
I'll fix this.


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