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

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


  • To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgA9OzcfY9Gb9pGR2mZngrddXcW4QAHXHZeACtw2sAABAkhcg==
  • Thread-topic: [Xen-devel] get_callback_via for Windows PV drivers

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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