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] get_callback_via for Windows PV drivers

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] get_callback_via for Windows PV drivers
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Thu, 27 Sep 2007 20:55:32 +1000
Delivery-date: Thu, 27 Sep 2007 03:56:24 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgA9OzcfY9Gb9pGR2mZngrddXcW4Q==
Thread-topic: get_callback_via for Windows PV drivers
Looking at the 'unmodified_drivers', it appears that I'm supposed to
tell the hypervisor the IRQ number to use to signal me. Under the
Windows DDK, I get an Interrupt Vector, which I don't think is the same
as an IRQ number... and I think I'm supposed to work backwards from the
vector to try and figure out what IRQ I'm supposed to pass the

If I right click on the PCI driver in 'Device Manager', it tells me that
the Xen PCI virtual device is using IRQ 28, is this the magic number
that I need to give to the hypervisor?



Xen-devel mailing list