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:	Sun, 30 Sep 2007 09:14:58 +0100
Delivery-date:	Sun, 30 Sep 2007 01:11:21 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<AEC6C66638C05B468B556EA548C1A77D01249937@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:	AcgA9OzcfY9Gb9pGR2mZngrddXcW4QAHXHZeACtw2sAABAkhcgBS3J4gAAeRFSU=
Thread-topic:	[Xen-devel] get_callback_via for Windows PV drivers
User-agent:	Microsoft-Entourage/11.3.6.070618

On 30/9/07 05:40, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>>> 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.
> 
> Using 28 as the irq appears to work - the ISR definitely get called by
> xen (and locks up if I don't do the right thing with the upcall_pending
> flag).
> 
> Can you see a problem with doing it that way?

No, since it sounds like that value is the GSI.

 -- Keir



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