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 18:19:38 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 06 Dec 2006 01:20:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of Wed, 06 Dec 2006 14:56:54 +0800. <51CFAB8CB6883745AE7B93B3E084EBE207DD95@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: <51CFAB8CB6883745AE7B93B3E084EBE207DD95@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
You (anthony.xu) said:
>>   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.
> In this case,
> Can we call set_callback_irq with hardware irq inside Qemu rather than
> platform_pci, just after platform_pci is initiated in Qemu?
> It seems resolve this issue.
> What's your opinion about this?

  Sorry, I don't know this issue for detail. I think that the guest
OS sets interrupt mask register of VIOSAPIC until setting own vector.
I assume that the guest OS might change the vector for such hardware
in active state.

> BTW I found we use viosapic_set_irq to pend the platform_pci interrupt.
> It may be no correct, because platform_pic interrupt is like "edge"
> triggered interrupt, but VIOSAPIC for this irq is programmed to a "level"
> triggered due to it is PCI device.
> I'll fix this.

  Thank you.

- Tsunehisa Doi

Xen-ia64-devel mailing list

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