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/
Home Products Support Community News


Re: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism

To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel][PATCH]Change to new interrupt deliver mechanism
From: Doi.Tsunehisa@xxxxxxxxxxxxxx
Date: Wed, 06 Dec 2006 15:26:54 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 05 Dec 2006 22:27:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of Wed, 06 Dec 2006 13:17:31 +0800. <51CFAB8CB6883745AE7B93B3E084EBE207DD94@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <51CFAB8CB6883745AE7B93B3E084EBE207DD94@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Anthony,

You (anthony.xu) said:
>>   We had implemented older PV-on-HVM with the method like this.
>> But, we found the issue that interrupt was injected during interrupt
>> masking of VIOSAPIC. So we changed to implement it.
>>   In this time, we have to implement it that interrupt injection
>> follows VIOSAPIC status. Thus, HV should look for VIOSAPIC, I think.
> Hi Dio,
> If platform_pci conforms to IOSAPIC, I has below suggestion.
> 1. platform_pci calls set_callback_irq using vector,
> 2. since HVMOP_set_param hypercall is arch-specific, HV can translate
>    vector to irq, ( VIOSAPIC can provide this interface),
> 3. if there is event to besent, HV calls viosapic_set_irq to pend
>    interrupt.
> What's your opinion about this?

  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.

- Tsunehisa Doi

Xen-ia64-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>