WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Change spec of callback IRQ for PV-on-HVMonIA64
From: Doi.Tsunehisa@xxxxxxxxxxxxxx
Date: Tue, 21 Nov 2006 17:41:46 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Doi.Tsunehisa@xxxxxxxxxxxxxx, Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Tue, 21 Nov 2006 00:42:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of Tue, 21 Nov 2006 16:17:18 +0800. <D470B4E54465E3469E2ABBC5AFAC390F0513FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <D470B4E54465E3469E2ABBC5AFAC390F0513FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Kevin,

You (kevin.tian) said:
>>> 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?

  I am talking about the situation of other OS guest on xen. In the
OS, we can't get the vector with its driver interface, because the
guest OS might set own value as vector to the interrupt controller.

  I believe that callback irq is the interface between hypervisor and
guest OS, thus it has to be indepent from kind of guest OS. Therefore
we should not use the value which we can't get in any OS.

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

  I think that the other OS register evtchn_interrupt at own vector
determined by itself for GSI(0x9).

Thanks,
- Tsunehisa Doi

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