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:44:30 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 06 Dec 2006 01:44:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of Wed, 06 Dec 2006 17:27:33 +0800. <51CFAB8CB6883745AE7B93B3E084EBE207DD97@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: <51CFAB8CB6883745AE7B93B3E084EBE207DD97@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Anthony,

You (anthony.xu) said:
>>   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.
> Hi Doi,
> This issue is from you,  guest linux uses vector, while there is no
> function like vector_to_irq.

  Sorry, I might misunderstand your comment.

  Yes, I think so.

> Because the hardware irq for platform_pci will not be changes.
> We can call set_callback_irq with hardware irq inside Qemu,
> Thus, platform_pci driver don't need to call set_callback_irq.
> Yes, guest OS can change the vector for platform_pci hardware irq,
> But the hardware irq is not changed, and HV know how to translate
> hardware irq to level through VIOSAPIC,
> And HV still use viosapic_set_irq to pend platform_pci interrupt.
> So I think it works.

  Do you meen that we have to modify qemu code to solve this isssue ?

- Tsunehisa Doi

Xen-ia64-devel mailing list