RE: [Xen-devel] [PATCH] Change spec of callback IRQ for PV-on-HVMonIA64

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>From:Doi.Tsunehisa@xxxxxxxxxxxxxx
>Sent: 2006年11月21日 16:05
>Hi Kevin,
>
>You (kevin.tian) said:
>>>> Maybe I'm missing something and you can help me understand. :-)
>>>> Whatever the value is mangled in pdev->irq, you should always
>>>> keep following two instances same:
>>>>    if ((ret = request_irq(pdev->irq, evtchn_interrupt, SA_SHIRQ,...
>>>> and
>>>>    if ((ret = set_callback_irq(pdev->irq)))
>>>
>>>  In x86-linux, two instances are same. But in IA64-linux, previous
>one
>>>is a external interrupt vector for xen-platform interruption. Although
>>>latter one is a hardware IRQ id. Both values are not same in
>IA64-linux.
>>
>> The callback value is the one pending to vIRR, which should be same
>> as the one that platform-pci driver binds to. I'm still not sure the exact
>> difference here. It should be arch-independent. You have to draw
>> agreement between two sides.
>
>  In the Linux-world, I agree it. But... In the other OS (like Windows),
>we can get only hardware IRQ with its driver interface. Thus I propose
>to change the spec of callback IRQ.
> 

Callback IRQ is only meaningful for xen, and if in any case, your 
evtchn_interrupt still hooks at vector (0x21), what does matter to 
change callback irq?

En... seems you're talking about other OS which register evtchn_interrupt at 
0x9 instead of 0x21? If that's the case, how to differentiate?

Thanks,
Kevin

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