[Xen-devel]Question about qemu interrupt deliver.

To:	"Keir Fraser" <keir@xxxxxxxxxxxxx>
Subject:	[Xen-devel]Question about qemu interrupt deliver.
From:	"Xu, Anthony" <anthony.xu@xxxxxxxxx>
Date:	Wed, 29 Nov 2006 15:57:03 +0800
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Tue, 28 Nov 2006 23:57:51 -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/UCWhQFxKqBSYWUgXBidhb4Lg==
Thread-topic:	[Xen-devel]Question about qemu interrupt deliver.

Hi keir,

I have two questions about the new qemu interrupt deliver mechanism.

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?


Thanks,
Anthony

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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] [PATCH] [HVMLOADER] built-in memcmp function uses not-yet implemented opcode, Keir Fraser

Next by Date:

Re: [Xen-devel] pfn to mfn mapping for HVM domains?, Keir Fraser

Previous by Thread:

[Xen-devel] VMX status report 12591:7826e5482d42 with BLOCK issue, Yu, Ping Y

Next by Thread:

Re: [Xen-devel]Question about qemu interrupt deliver., Keir Fraser

Indexes:

[Date] [Thread] [Top] [All Lists]