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:58:59 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Doi.Tsunehisa@xxxxxxxxxxxxxx, Alex Williamson <alex.williamson@xxxxxx>
Delivery-date: Tue, 21 Nov 2006 00:59:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of Tue, 21 Nov 2006 16:46:41 +0800. <D470B4E54465E3469E2ABBC5AFAC390F051402@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: <D470B4E54465E3469E2ABBC5AFAC390F051402@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Kevin,

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

  In my experience, the other OS has device driver interface to notice
GSI for the device. It tells the vector to the interrupt controller
in kenrel code, not device driver. So, we can't know the vector, I think.

Thanks,
- Tsunehisa Doi

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