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]Question about qemu interrupt deliver.

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Keir Fraser" <keir@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel]Question about qemu interrupt deliver.
From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Date: Wed, 29 Nov 2006 16:21:13 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 29 Nov 2006 00:21:19 -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: AccTi/UCWhQFxKqBSYWUgXBidhb4LgAAe01hAAAWaeA=
Thread-topic: [Xen-devel]Question about qemu interrupt deliver.
Keir Fraser write on 2006年11月29日 16:11:
> On 29/11/06 7:57 am, "Xu, Anthony" <anthony.xu@xxxxxxxxx> wrote:
> 
>> 1. Why is the interrupt router table put inside hypervisor other
>> than Qemu? 
>> 
>> 2. Why is the relationship of PCI device interrupt pin to IOAPIC
>>    input pin put inside hypervisor other than Qemu?
> 
> Since the PICs live in Xen it seems cleaner to move interrupt
> steering there too and have a clean device-level interface to device
> models. It also means that this core piece of chipset infrastructure
> is available for use by PCI devices that we may implement in Xen or
> anywhere else outside the qemu-dm process in future, so in this
> respect it is more flexible rather than less. 

Thanks,
This answered the first question.

How about the second one?
#define hvm_pci_intx_gsi(dev, intx)  \
    (((((dev)<<2) + ((dev)>>3) + (intx)) & 31) + 16)

Why this logic is implemented inside hypervisor?

Thanks,
Anthony


> 
>  -- Keir

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