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


[Xen-devel] Does Dom0 always get interrupts first before they are delive

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Does Dom0 always get interrupts first before they are delivered to other guest domains?
From: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
Date: Fri, 16 Mar 2007 10:30:09 -0700
Delivery-date: Fri, 16 Mar 2007 10:29:17 -0700
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>
References: <C22009AB.4715%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

It seems if HVM domains access device using emulation mode w/ device model in domain0, Xen hypervisor will send the interrupt event to domain0 first and then the device model in domain0 will send event to HVM domains.

However, if I'm using split driver model and I only run BE driver on domain0. Does domain0 still get the interrupt first (assume this interupt is not owned by the Xen hypervisor ,e.g. local APIC timer) or Xen hypervisor will send event directly to HVM domain bypass domain0 for split driver model?

Another question is: for interrupt delivery, does Xen treat para-virtualized domain differently from HVM domain considering using device model and split driver model?

Thanks a lot,


Xen-devel mailing list

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