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


Re: [Xen-devel] get_callback_via for Windows PV drivers

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] get_callback_via for Windows PV drivers
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 28 Sep 2007 14:05:43 +0100
Delivery-date: Fri, 28 Sep 2007 06:06:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01249936@trantor>
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: AcgA9OzcfY9Gb9pGR2mZngrddXcW4QAHXHZeACtw2sAABAkhcg==
Thread-topic: [Xen-devel] get_callback_via for Windows PV drivers
User-agent: Microsoft-Entourage/
On 28/9/07 12:15, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>> Neither of these values is determinable from the
>> interrupt vector. However, if you have probed the PCI device then you
>> probably know the (bus,dev,fn,pin) tuple, so you should probably aim
> to
>> specify that.
> I can get bus, dev, and fn, but can't seem to find 'pin' from the
> information that Windows gives me... if 28 isn't the GSI, then I'll have
> to look harder for this 'pin' number in the windows structures...

Read byte 0x3d in the PCI device config space. That returns the pin index.

> What is the simplest thing I could do to get the hypervisor to trigger
> an interrupt? That would tell me for sure that it's working. I have only
> implemented a tiny bit of the event channel logic, and no xen bus stuff
> yet...

Implement a simple console driver to talk to xenconsoled, perhaps?

 -- Keir

Xen-devel mailing list