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: <Doi.Tsunehisa@xxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Change spec of callback IRQ for PV-on-HVMonIA64
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 21 Nov 2006 16:46:41 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Tue, 21 Nov 2006 00:47:03 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccNSOuowe9CMXqrSA6+cyZXoa3qwQAADEcQ
Thread-topic: [Xen-devel] [PATCH] Change spec of callback IRQ for PV-on-HVMonIA64
>From: Doi.Tsunehisa@xxxxxxxxxxxxxx
>Sent: 2006年11月21日 16:42
>> 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).
>

OK, I see your point. One interesting question is, since you don't
know what the own vector used by other OS is, how do you do 
translation within xen to inject at own vector wanted by other OS? 
If there's a way to tell, why not tell at set_callback_irq time? :-)

Thanks,
Kevin

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