[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel]Question about qemu interrupt deliver.

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>
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
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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

Follow-Ups:
- Re: [Xen-devel]Question about qemu interrupt deliver.
  - From: Keir Fraser

Prev by Date: Re: [Xen-devel] [PATCH] [HVMLOADER] built-in memcmp function uses not-yet implemented opcode
Next by Date: Re: [Xen-devel] pfn to mfn mapping for HVM domains?
Previous by thread: [Xen-devel] VMX status report 12591:7826e5482d42 with BLOCK issue
Next by thread: Re: [Xen-devel]Question about qemu interrupt deliver.
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.